Home » RDBMS Server » Server Administration » Not able to logins as ssysdba (oracle 9.2.0.6.0 ,linux )
Not able to logins as ssysdba [message #567587] Wed, 03 October 2012 07:41 Go to next message
sathish16787
Messages: 56
Registered: September 2011
Location: mumbai
Member
when we try connect to db it hangs

sqlplus '/ as sysdba'

SQL*Plus: Release 9.2.0.6.0 - Production on Thu Oct 4 08:20:57 2012

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.


Re: Not able to logins as ssysdba [message #567588 is a reply to message #567587] Wed, 03 October 2012 07:46 Go to previous messageGo to next message
Michel Cadot
Messages: 59427
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Truss your associated dedicated process.
Does the instance run or not?
Check if any FS is full.

Regards
Michel
Re: Not able to login as sysdba [message #567601 is a reply to message #567588] Wed, 03 October 2012 08:03 Go to previous messageGo to next message
sathish16787
Messages: 56
Registered: September 2011
Location: mumbai
Member
Instance is running

checked with ps -ef | grep pmon

Enough space is in FS.
Re: Not able to login as sysdba [message #567602 is a reply to message #567601] Wed, 03 October 2012 08:05 Go to previous messageGo to next message
Michel Cadot
Messages: 59427
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Are you able to connect as SYSTEM?
Rest "Truss your associated dedicated process" to see what it does.

Regards
Michel
Re: Not able to login as sysdba [message #567603 is a reply to message #567601] Wed, 03 October 2012 08:05 Go to previous messageGo to next message
BlackSwan
Messages: 22911
Registered: January 2009
Senior Member
what clues exist at tail end of alert_SID.log file? post excerpt from it
Re: Not able to login as sysdba [message #567607 is a reply to message #567603] Wed, 03 October 2012 08:16 Go to previous messageGo to next message
sathish16787
Messages: 56
Registered: September 2011
Location: mumbai
Member
Wed Oct 3 17:19:21 2012
Beginning log switch checkpoint up to RBA [0xb3f1.2.10], SCN: 0x0938.508d2c16
Thread 1 advanced to log sequence 46065
Current log# 2 seq# 46065 mem# 0: /u01/vis/visdemodata/log2.dbf
Wed Oct 3 17:28:26 2012
Completed checkpoint up to RBA [0xb3f1.2.10], SCN: 0x0938.508d2c16
Wed Oct 3 17:28:38 2012
Beginning log switch checkpoint up to RBA [0xb3f2.2.10], SCN: 0x0938.508d8769
Thread 1 advanced to log sequence 46066
Current log# 3 seq# 46066 mem# 0: /u01/vis/visdemodata/log1.dbf
Wed Oct 3 17:35:00 2012
Beginning log switch checkpoint up to RBA [0xb3f3.2.10], SCN: 0x0938.508e140c
Thread 1 advanced to log sequence 46067
Current log# 1 seq# 46067 mem# 0: /u01/vis/visdemodata/log3.dbf
Wed Oct 3 17:35:06 2012
Completed checkpoint up to RBA [0xb3f2.2.10], SCN: 0x0938.508d8769
Wed Oct 3 17:35:50 2012
Beginning log switch checkpoint up to RBA [0xb3f4.2.10], SCN: 0x0938.508e1d18
Thread 1 advanced to log sequence 46068
Current log# 2 seq# 46068 mem# 0: /u01/vis/visdemodata/log2.dbf
Wed Oct 3 17:35:50 2012
Completed checkpoint up to RBA [0xb3f3.2.10], SCN: 0x0938.508e140c
Wed Oct 3 17:50:53 2012
Completed checkpoint up to RBA [0xb3f4.2.10], SCN: 0x0938.508e1d18
Wed Oct 3 17:50:54 2012
Beginning log switch checkpoint up to RBA [0xb3f5.2.10], SCN: 0x0938.508fde9e
Thread 1 advanced to log sequence 46069
Current log# 3 seq# 46069 mem# 0: /u01/vis/visdemodata/log1.dbf
Wed Oct 3 17:52:09 2012
Beginning log switch checkpoint up to RBA [0xb3f6.2.10], SCN: 0x0938.508fffdb
Thread 1 advanced to log sequence 46070
Current log# 1 seq# 46070 mem# 0: /u01/vis/visdemodata/log3.dbf
Wed Oct 3 17:52:12 2012
Completed checkpoint up to RBA [0xb3f5.2.10], SCN: 0x0938.508fde9e
Wed Oct 3 17:52:53 2012
Completed checkpoint up to RBA [0xb3f6.2.10], SCN: 0x0938.508fffdb
Wed Oct 3 17:53:12 2012
Beginning log switch checkpoint up to RBA [0xb3f7.2.10], SCN: 0x0938.50900e32
Thread 1 advanced to log sequence 46071
Current log# 2 seq# 46071 mem# 0: /u01/vis/visdemodata/log2.dbf
Wed Oct 3 18:13:49 2012
Completed checkpoint up to RBA [0xb3f7.2.10], SCN: 0x0938.50900e32
Re: Not able to login as sysdba [message #567608 is a reply to message #567607] Wed, 03 October 2012 08:18 Go to previous messageGo to next message
sathish16787
Messages: 56
Registered: September 2011
Location: mumbai
Member
Not able to connect as system
Re: Not able to login as sysdba [message #567609 is a reply to message #567608] Wed, 03 October 2012 08:24 Go to previous messageGo to next message
BlackSwan
Messages: 22911
Registered: January 2009
Senior Member
>Wed Oct 3 18:13:49 2012

what happened between time above (last posted excerpt) & time below since MANY hours elapsed?

>SQL*Plus: Release 9.2.0.6.0 - Production on Thu Oct 4 08:20:57 2012
Re: Not able to login as sysdba [message #567612 is a reply to message #567609] Wed, 03 October 2012 08:32 Go to previous messageGo to next message
sathish16787
Messages: 56
Registered: September 2011
Location: mumbai
Member
Wed Oct 3 18:13:49 2012 after this time alert not generated
Re: Not able to login as sysdba [message #567613 is a reply to message #567612] Wed, 03 October 2012 08:38 Go to previous messageGo to next message
BlackSwan
Messages: 22911
Registered: January 2009
Senior Member
>Wed Oct 3 18:13:49 2012 after this time alert not generated
Then I would conclude that the instance is 100% stuck,frozen,hung solid.
I would restart the DB & hope that its becomes available again.
Re: Not able to login as sysdba [message #567615 is a reply to message #567612] Wed, 03 October 2012 08:38 Go to previous messageGo to next message
Michel Cadot
Messages: 59427
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Check if there is any trace file.
Anyway, I think the best you have to do is to kill smon/pmon and restart the instance.

Regards
Michel
Re: Not able to login as sysdba [message #567616 is a reply to message #567615] Wed, 03 October 2012 08:47 Go to previous messageGo to next message
sathish16787
Messages: 56
Registered: September 2011
Location: mumbai
Member
below is from trace file

Redo thread mounted by this instance: 1
Oracle process number: 77
Unix process pid: 29680, image: oracle@xxxx.xxxx.com (TNS V1-V3)

*** SESSION ID:(55.50823) 2012-08-18 20:38:47.733
kwqicaclcur: Error 604
Error(2) 1653
Cursor Session Number : 55
Cursor Session Serial : 50823
Cursor Pin Number : 10
kwqicaclcur: Error 604
Error(2) 1653
Cursor Session Number : 55
Cursor Session Serial : 50823
Cursor Pin Number : 10
kwqicaclcur: Error 604
Error(2) 1653
Cursor Session Number : 55
Cursor Session Serial : 50823
Cursor Pin Number : 10
kwqicaclcur: Error 604
Error(2) 1653
Cursor Session Number : 55
Cursor Session Serial : 50823
Cursor Pin Number : 10
Re: Not able to login as sysdba [message #567617 is a reply to message #567616] Wed, 03 October 2012 08:49 Go to previous messageGo to next message
BlackSwan
Messages: 22911
Registered: January 2009
Senior Member
>*** SESSION ID:(55.50823) 2012-08-18 20:38:47.733
from more than 1 month ago & not relevant for today.
Re: Not able to login as sysdba [message #567649 is a reply to message #567617] Thu, 04 October 2012 00:04 Go to previous message
sathish16787
Messages: 56
Registered: September 2011
Location: mumbai
Member
Issue fixed

ps -ef | grep ora

oracle 21438 1 0 Oct04 ? 00:00:00 oracleXXXX (LOCAL=NO)

since 2 months process is running. we killed all the process .Now we are able to login .


Thanks ..........
Previous Topic: Modified objects
Next Topic: Use of LM( Lock mode) in V$lock
Goto Forum:
  


Current Time: Sun Oct 26 01:07:11 CDT 2014

Total time taken to generate the page: 0.09428 seconds