Database startup issue after power failure

Question

Hello, I am hoping someone might have some ideas for me on this issue. We had a power failure over the weekend and I was not alerted in time to shut down my DB server gracefully. I am running a 10g (10.2.0.4.0) standard database on RHEL 5. When power was restored I booted the server and noticed the database did not start (I have a startup script in init.d), I tried running dbstart manually and that did not work either. Below is the entries in my startup.log file and sqlnet.log file, I cannot figure out what is causing the 12514 error, as everything was working fine before the power failure. Interestingly though I am able to start the DB by running dbca and making a minor config change that requires a restart, dbca is somehow able to start the DB. Any ideas would be greatly apprieciated. Thanks!
STARTUP.LOG
/u01/app/oracle/product/10.2.0/db_1/bin/dbstart: Starting up database "DBS"
Sat Dec 4 15:33:12 PST 2010
SQL*Plus: Release 10.2.0.4.0 - Production on Sat Dec 4 15:33:12 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
SQL> ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
SQL> ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
SQL>
/u01/app/oracle/product/10.2.0/db_1/bin/dbstart: Database instance "DBS" warm started.
SQLNET.LOG
Fatal NI connect error 12514, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oraserver.domain.com)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=DBS.domain.com)(CID=(PROGRAM=sqlplus)(HOST=oraserver)(USER=oracle))))
VERSION INFORMATION:
TNS for Linux: Version 10.2.0.4.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.4.0 - Production
Time: 01-OCT-2009 17:19:10
Tracing not turned on.
Tns error struct:
ns main err code: 12564
TNS-12564: TNS:connection refused
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0

Answer 1

Mohammed Taj wrote:
Why do you suggest starting the db before the listener?
I always start db first then after listener.
Well, there's a good strong justification ....
because if you start listener then that time there is no db services to register, and lsnrctl services will show (no services ....) msg. Ok, so I have this startup script. One line starts the listener, the very next line starts the database. So in the few seconds between the listener starting and the database starting and fully opening, I am exposed to the possibility that someone might try to connect and get "ORA-12514: TNS:listener does not currently know of service requested in connect descriptor". That's opposed to the error they would have gotten a couple of seconds earlier, that would have said .... "ORA-12541: TNS:no listener"
Or I use your startup script. One line starts the database, the next line starts the listener. A full minute later the instance gets itself registered with the listener. So in the time between starting the listener and the database making as second - this time successful - attempt to register with the listener, I am exposed to the risk of someone making a connection attempt and getting "ORA-12514: TNS:listener does not currently know of service requested in connect descriptor". And again, this is as opposed to if they had been just a few seconds earlier and gotten ""ORA-12541: TNS:no listener"
or else if you want to start listener first then edit the listener.ora file and add the sid (few lines) then user will not receive the above mention error.In which case I start the listener first, it now knows about the instance without the instance self registering ... but it still has to wait for the instance to come up before it can service a connection request. How is that any different from NOT listing the SID_LIST, starting the listener, then starting the database and allowing the database to self-register? You are not eliminating anything from the user's end .. simply changing the error message they would get.