cancel
Showing results for 
Search instead for 
Did you mean: 

Oracle problem at startup

Former Member
0 Kudos

Hi

Oracle at boot after shutdown get the following error in the alert:

ORA-27157: OS post/wait facility removed

ORA-27300: OS system dependent operation:semop failed with status: 36

ORA-27301: OS failure message: Identifier removed

ORA-27302: failure occurred at: sskgpwwait1

Mon Dec 17 08:06:50 2007

RECO: terminating instance due to error 27157

Instance terminated by RECO, pid = 27760

Mon Dec 17 08:06:50 2007

Errors in file /oracle/BB2/saptrace/background/bb2_reco_27760.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-27157: OS post/wait facility removed

ORA-27300: OS system dependent operation:semop failed with status: 36

ORA-27301: OS failure message: Identifier removed

ORA-27302: failure occurred at: sskgpwwait1

It's necesary to kill the oracle's process, clean memory semafhore before startup.

We have oracle 9.2.0.5 and Solarios 5.8. I'm not sure if it's a oracle problem memory. RAM is 8 Gb and the sga_max_size 1.8 Gb.

Any ideas?

Thanks and advance

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Thanks again

I have read the metalink notes but now I'm not sure to find the solution. My Knowledge of operating system-level memory are small.

Sorry but this is my first post and I didn't know rating your help. I hope to have done correctly.

Best regards

Former Member
0 Kudos

Thanks for your help Stefan.

We startup the database with a script from the crontab.

The trace file bb2_reco_27760.trc is similar than the alert, A part of it is:

Argument/Register addr=0x00000001032CCC28.

Dump of memory from 0x00000001032CCBE8 to 0x00000001032CCD28

1032CCBE0 64623033 64623137 [db03db17]

1032CCBF0 31000000 00000000 32633164 35366236 [1.......2c1d56b6]

1032CCC00 34386336 63643131 30000000 00000000 [48c6cd110.......]

ORA-27120: unable to removed shared memory segment

SVR4 Error: 22: Invalid argument

Additional information: -2147361064

Additional information: 53485568

Additional information: 2147475601

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-27157: OS post/wait facility removed

ORA-27300: OS system dependent operation:semop failed with status: 36

ORA-27301: OS failure message: Identifier removed

ORA-27302: failure occurred at: sskgpwwait1

I increased de SGA up 3.273.628.280 because it was only 1.855.539.118 and the RAM is 8 Gb. I always increased dba_cache_size from 927.769.559 to 2.198.478.592

Thanks again

stefan_koehler
Active Contributor
0 Kudos

Hello Maximino,

i am not pretty deep into SUN Solaris (i am an AIX guy ), but there are 2 metalink notes which refer to those errors.

Thanks for the part of the trace file... the interesting part is the error "SVR4 Error: 22: Invalid argument" in combination with the other ORA-errors.

Metalinknotes #61896.1 and #115753.1 are pointing to such problems.

Regards

Stefan

P.S.: I would appreciate some ratings.

Former Member
0 Kudos

It is rather strange that somebody has erased the semaphores. I have increased the sga parameter and the las startup finished OK, bun I don't sure if the problem is resolved.

Do you think that my initial question and the sga are related?

Thanks

stefan_koehler
Active Contributor
0 Kudos

Hello,

>> Do you think that my initial question and the sga are related?

No, i don't think so. The SGA is build up in shared memory, but increasing the SGA should not solve the problem.

If you decrease the SGA again - does the problem still persist?

- How did you start the database .. with a script or manually?

- Does the trace file bb2_reco_27760.trc include something interesting?

- Are you using RAC or some other cluster techniques?

Regards

Stefan

stefan_koehler
Active Contributor
0 Kudos

Hello Maximino,

ORA-27302 points to removed shared memory segments. (manually or by OS)

Metalinknote #438205.1 describes that problem.

>> Cause

>> The semaphores used by Oracle have been inadvertendly removed.

>>The errors are signalling that something happened at the OS level with shared memory and/or semaphores. The semaphore sets could be removed manually, or they could be dying for some reason due to a hardware >>error. You may want to check for any possibility of a user dba using the "ipcrm" command to kill the

>>semaphores (accidentally) since the error ora-27301 (OS failure message: Identifier removed) suggests that. Also, it could have been a bad memory stick or something else at the OS level. Someone could also have removed the shared memory segments at the OS level for some specific reason, or by accident.Most likely something had removed the shared memory and semaphore sets in use by 'oracle'. This can only be done by a root-level user or 'oracle' itself who owns the resources. If someone logged in as root and removed all IPC resources, Oracle would crash when it lost the allocated shared memory/semaphores.

Please check your operating system for some errors or if you have a script which removes shared memory segments.

Regards

Stefan