lusiana
asked on
LGWR failure and is causing instance shutdown.
Hi All,
I experienced a problem where oracle instance shuts down,
and the last entry on alert_sid.log file:
:
Thread 1 advanced to log sequence 22412
Current log# 2 seq# 22412 mem# 0: /opt/dbfiles1/dev1/oradata /dev1/redo 02.log
LGWR: terminating instance due to error 27152
Instance terminated by LGWR, pid = 13562
Wed Jul 25 14:16:28 2001
Errors in file /oracle/admin/dev1/bdump/d ev1_lgwr_1 3562.trc:
ORA-27300: OS system dependent operation:semctl failed with status: 22
ORA-27301: OS failure message: Invalid argument
ORA-27302: failure occurred at: sskgpwrm1
ORA-27152: attempt to post process failed
Additional information: 1
Additional information: -2090048448
ORA-27300: OS system dependent operation:semctl failed with status: 22
ORA-27301: OS failure message: Invalid argument
ORA-27302: failure occurred at: sskgpwpost1
ORA-27303: additional information: semid = 12648451
Some additional information:
From init.ora: processes = 50
Oracle version is 8.1.6
I'm quite at lost at how to start investigating this problem.
The problem has occurred three times in the span of the last 10 days.
Any help, hints would be appreciated.
Thanks heaps.
Lucy
I experienced a problem where oracle instance shuts down,
and the last entry on alert_sid.log file:
:
Thread 1 advanced to log sequence 22412
Current log# 2 seq# 22412 mem# 0: /opt/dbfiles1/dev1/oradata
LGWR: terminating instance due to error 27152
Instance terminated by LGWR, pid = 13562
Wed Jul 25 14:16:28 2001
Errors in file /oracle/admin/dev1/bdump/d
ORA-27300: OS system dependent operation:semctl failed with status: 22
ORA-27301: OS failure message: Invalid argument
ORA-27302: failure occurred at: sskgpwrm1
ORA-27152: attempt to post process failed
Additional information: 1
Additional information: -2090048448
ORA-27300: OS system dependent operation:semctl failed with status: 22
ORA-27301: OS failure message: Invalid argument
ORA-27302: failure occurred at: sskgpwpost1
ORA-27303: additional information: semid = 12648451
Some additional information:
From init.ora: processes = 50
Oracle version is 8.1.6
I'm quite at lost at how to start investigating this problem.
The problem has occurred three times in the span of the last 10 days.
Any help, hints would be appreciated.
Thanks heaps.
Lucy
Here is some more info. Good luck!
Bug 1262942 is an issue where the hash function used to generate the key for semaphore set allocation can generate duplicates for similar ORACLE_SID/ORACLE_HOME combinations. This can cause problems when there are several databases on the same server using similar ORACLE_SIDs as if the keys are the same only one of the instances can be running at a time.
The bug is fixed in 8.1.7 and included in the 8.1.6.3 patchset release (for Solaris only). The workaround is to rename the ORACLE_SID of one of the clashing instances.
You can check for duplicate keys using 'ipcs -s':
o startup instance 1
o ipcs -s
o shutdown instance 1
o startup instance 2
o ipcs -s
Bug 1262942 is an issue where the hash function used to generate the key for semaphore set allocation can generate duplicates for similar ORACLE_SID/ORACLE_HOME combinations. This can cause problems when there are several databases on the same server using similar ORACLE_SIDs as if the keys are the same only one of the instances can be running at a time.
The bug is fixed in 8.1.7 and included in the 8.1.6.3 patchset release (for Solaris only). The workaround is to rename the ORACLE_SID of one of the clashing instances.
You can check for duplicate keys using 'ipcs -s':
o startup instance 1
o ipcs -s
o shutdown instance 1
o startup instance 2
o ipcs -s
ASKER
Thanks for your response.
At the moment, our database has only one instance.
The ORACLE_SID is defined to be the same as db_name.
Thanks again.
At the moment, our database has only one instance.
The ORACLE_SID is defined to be the same as db_name.
Thanks again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks heaps for the responses, everyone.
It occurs when two of your ORACLE_SIDs are similarly named. Rename one of your ORACLE_SIDs - this is relatively easy since your instance ID (ORACLE_SID) can be different from db_name.