Re: /etc/init.d/dbora stop hangs

"ton de w" <ton_de_winter_at_yahoo.co.uk> schreef in bericht news:6edab45a-a831-43b8-a01d-d7f580f87612_at_s27g2000prg.googlegroups.com... On 10 Jan, 15:36, "fitzjarr..._at_cox.net" <fitzjarr..._at_cox.net> wrote:
> On Jan 10, 9:24 am, ton de w <ton_de_win..._at_yahoo.co.uk> wrote:
>
>
>
>
>
> > On 10 Jan, 13:29, vitalis..._at_gmail.com wrote:
>
> > > On Jan 10, 12:39 pm, ton de w <ton_de_win..._at_yahoo.co.uk> wrote:
>
> > > > Hello,
> > > > Have 9i on RedHat 3.8 and if I carry out a dbors stop it hangs.
>
> > > > [root_at_carbon init.d]# ./dbora stop
>
> > > > SQL*Plus: Release 9.2.0.4.0 - Production on Thu Jan 10 11:29:34 2008
>
> > > > Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
>
> > > > SQL> Connected.
> > > > SQL>
> > > > //hangs here
> > > > SQL> quit
>
> > > > ORA-01013: user requested cancel of current operation
> > > > // hangs here
> > > > SQL> Disconnected from Oracle9i Release 9.2.0.4.0 - Production
> > > > // but responds to a ctrl-c
> > > > JServer Release 9.2.0.4.0 - Production
> > > > Database "HIST2" shut down.
>
> > > > LSNRCTL for Linux: Version 9.2.0.4.0 - Production on 10-JAN-2008
> > > > 11:35:04
>
> > > > Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
>
> > > > Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)
> > > > (PORT=1521)))
> > > > The command completed successfully
>
> > > > SQL>
> > > > // so the db has shut down, but I am concerned that I dont get the
> > > > root prompt back.
>
> > > > What can I do to investigate this?
>
> > > > dbora script below:
>
> > > > ORA_HOME=/u01/app/oracle/product/9.2.0
> > > > ORA_OWNER=oracle
>
> > > > if [ ! -f $ORA_HOME/bin/dbstart ]
> > > > then
> > > > echo "Oracle startup: cannot start"
> > > > exit
> > > > fi
>
> > > > case "$1" in
> > > > 'start')
> > > > # Start the Oracle databases:
> > > > # The following command assumes that the oracle login
> > > > # will not prompt the user for any values
> > > > su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl start"
> > > > su - $ORA_OWNER -c $ORA_HOME/bin/dbstart
> > > > ;;
> > > > 'stop')
> > > > # Stop the Oracle databases:
> > > > # The following command assumes that the oracle login
> > > > # will not prompt the user for any values
> > > > su - $ORA_OWNER -c $ORA_HOME/bin/dbshut
> > > > su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl stop"
> > > > ;;
> > > > esac
>
> > > > TIA
>
> > > > Ton
>
> > > dbshut reads /etc/oratab
> > > Check in /etc/oratab whether your database is set up correctly.- Hide
> > > quoted text -
>
> > > - Show quoted text -
>
> > OK good point!
>
> > [root_at_carbon]$ cat /etc/oratab
> > ...
> > #
> > *:/u01/app/oracle/product/9.2.0:N
> > HIST2:/u01/app/oracle/product/9.2.0:Y
>
> > Looks good to me!
> > Maybe if it was baad /etc/init.d/dbora start would not work?- Hide
> > quoted text -
>
> > - Show quoted text -
>
> That is correct.
>
> How long do you let this script run before killing the shutdown? What
> do you find in your alert log? You've provided very little, if
> anything, to base a determination upon.
>
> David Fitzjarrell- Hide quoted text -
>
> - Show quoted text -

True - Sorry - I was not quite sure what info would help troubleshoot. There could be a problem with port 8080 - there was/is a webserver running on the oracle and after a reboot i could not start the webserver - port in use.
[root_at_carbon root]# netstat -anp | grep 8080

tcp        0      0 0.0.0.0:8080
0.0.0.0:*                   LISTEN      4366/tnslsnr
[root_at_carbon root]# nmap -sT -O localhost | grep 8080
8080/tcp   open        http-proxy

the alerts file no errors and the dabase appears to have shut down correctly.
...
Completed: ALTER DATABASE OPEN
Shutting down instance: further logons disabled Shutting down instance (normal)
License high water mark = 3

I think I can live with not getting the root prompt back after a dbora stop for the moment.
But Oracle starting up and grabbing port 8080 is more urgent! And ideas?

• Reply starts here

If you are using (with or wihout knowing it) XDB (Oracle XML DB) in your database, it will get hold of port 8080 by default. You can change the port with

call dbms_xdb.cfg_update(updateXML(dbms_xdb.cfg_get(), '/xdbconfig/sysconfig/protocolconfig/httpconfig/http-port/text()', 8083));

exec dbms_xdb.cfg_refresh;

or more simple:

call xdb_utility.set_http_port(8083)

or use the em screens to do so.

For xdb_utility see metalink note 209564.1

Verify this with
lsnrctl status

Shakespeare Received on Fri Jan 11 2008 - 07:29:17 CST