| Database startup issue after power failure [message #485338] |
Tue, 07 December 2010 12:00  |
 |
taylorjp75
Messages: 14
Registered: December 2010
Location: California
|
Junior Member |
|
|
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.c om)(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
[EDITED by LF: fixed topic title typo; was "Oraclce"]
[Updated on: Wed, 08 December 2010 14:14] by Moderator Report message to a moderator |
|
|
|
| Re: Database startup issue after power failure [message #485341 is a reply to message #485338] |
Tue, 07 December 2010 12:13  |
 |
Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille
|
Senior Member
Account Moderator |
|
|
First check if instance is up
check if you can login to database (logged in as OS user oracle)
export ORACLE_SID=yourSID
sqlplus / as sysdba
issue some query and exit;
Then check the status of listener (name of listener is available in listener.ora file). and start the listener
lsnrctl status your_listenerName
lsnrctl start your_listenerName [Updated on: Tue, 07 December 2010 12:14] Report message to a moderator |
|
|
|
|
|
| Re: Database startup issue after power failure [message #485345 is a reply to message #485344] |
Tue, 07 December 2010 12:24 |
|
Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille
|
Senior Member
Account Moderator |
|
|
Please post what you did, instead of explaining. Helps us better.
Even if you provide a wrong ORACLE_SID or the instance is down,
your sysdba session will not give 12514, if you connect the way I said.
oracle@123#export ORACLE_SID=thisNeverExists
oracle@123#sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Dec 7 13:22:19 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
all you need to do is,
connect and start the instance (hopefully). login as sysdba
and issue
[Updated on: Tue, 07 December 2010 12:24] Report message to a moderator |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Database startup issue after power failure [message #485555 is a reply to message #485545] |
Wed, 08 December 2010 15:27 |
joy_division
Messages: 4963
Registered: February 2005
Location: East Coast USA
|
Senior Member |
|
|
Maybe TWO_TASK wasn't set previously. Maybe someone changed the .bash_profile since the last time the oracle user was logged in.
Maybe before the reboot a listener was started against a different listener.ora file than the one currently in place.
|
|
|
|
|
|
| Re: Database startup issue after power failure [message #485582 is a reply to message #485556] |
Wed, 08 December 2010 23:18 |
|
taylorjp75
Messages: 14
Registered: December 2010
Location: California
|
Junior Member |
|
|
Well I am still having the problem with dbstart, here is what I have done
1. Rebooted the server
2. Checked if oracle instance was running
[oracle@oraserver ~]$ ps -ef|grep smon
oracle 4301 4064 0 20:53 pts/2 00:00:00 grep smon
it was not
3. Tried connecting with sqlplus anyway (just to see what error I got)
[oracle@oraserver ~]$ sqlplus system/controll
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Dec 8 20:41:47 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
Enter user-name:
4. Checked the startup.log to see what might have gone wrong during dbstart execution
/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.
Shows the 12514 error but says the database was warm started, it is not though.
5. Checked the listener status
LSNRCTL> status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oraserver.jdnet.deere.com)(PORT=1521)))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Linux Error: 111: Connection refused
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC0)))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Linux Error: 111: Connection refused
It was not running
6. Connected as sysdba (thanks to BlackSwan I am to do that again) and ran startup
[oracle@oraserver ~]$ sqlplus "/as sysdba"
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Dec 8 20:44:13 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup open
ORACLE instance started.
Total System Global Area 8589934592 bytes
Fixed Size 2097696 bytes
Variable Size 1107299808 bytes
Database Buffers 7465861120 bytes
Redo Buffers 14675968 bytes
Database mounted.
Database opened.
After this the database is started and running fine.
So I can get my database started but my boot time start script, or just running dbstart from the command line, is not working, I cannot figure out what the problem is.
|
|
|
|
|
|
|
|
|
|
| Re: Database startup issue after power failure [message #485725 is a reply to message #485724] |
Thu, 09 December 2010 11:32 |
|
taylorjp75
Messages: 14
Registered: December 2010
Location: California
|
Junior Member |
|
|
[oracle@oraserver ~]$ cat $ORACLE_HOME/network/admin/sqlnet.ora
# sqlnet.ora Network Configuration File: /u01/app/oracle/product/10.2.0/db_1/network/admin/sqlnet.ora
# Generated by Oracle configuration tools.
NAMES.DIRECTORY_PATH= (TNSNAMES)
SQLNET.EXPIRE_TIME=120
[oracle@oraserver ~]$ cat $ORACLE_HOME/network/admin/listener.ora
# listener.ora Network Configuration File: /u01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1)
(PROGRAM = extproc)
)
)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oraserver.domain.com)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
)
)
SUBSCRIBE_FOR_NODE_DOWN_EVENT_Listener=OFF
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
