SAP not starting up

[AL_3001]

Hi Friends,
We have a wekly offline backup, where the sap is brought down by the script and than the backup start.After the backup, the script starts sap. However, recently there has been problems with starting up sap after the offline backup. The scripts in itself is fine. The error that is received is as follows:
------------------------------
The system failed to restart due to the error below:
**************************************************
PXA_NO_SHARED_MEMORY -- 08.03.2008 at 22:33:23
205748 kilo bytes of shared memory for PXA not available.
**************************************************

The system starts up but in a Zombie state and is not usable.
------------------------------

It seems, it cannot find enough memory to start up. Application team is blaming the unix team, saying there is problem with memory allocation. Kindly advise how shud we try to diagonse this unusual error at unis end.

Inputs would be really appreciated.

Thanks.

[Dennis Handly]

>it cannot find enough memory to start up

Is this a 32 or a 64 bit application?
What does "ipcs -ma" show?

>The system starts up but in a Zombie state

Do you mean a Unix zombie?

[AL_3001]

Attached is the output of ipcs.

[YAQUB_1]

Hi Ashish,

>>Application team is blaming the unix team, saying there is problem with memory allocation.

I strongly protest Ur SAP team, because with any evidence why they are blame U.

Please cross check with Ur SAP team, login a SAP administrator & run the command st22 and analysis the output & U find out what is the actual problem. After the analyses if they (SAP team) want change the abap/buffersize parameter using the st02.

[Note:- If possible pls send me st22 O/P]

Thanksâ Yaqub
HP Support!!!

[Eric Antunes]

Hi Ashish,

The solution here is to restart the server because your Oracle instance wasn't shutdown correctly (you should check why).

Best Regards,

Eric Antunes

[Dennis Handly]

You have a bunch of large segments:
519 0x91246e28 --rw-rw---- orarsp dba orarsp dba 54 1064181760
525 0x00002713 --rw-r----- rspadm sapsys rspadm sapsys 20 55059200
20503 0x00002716 --rw-r----- rspadm sapsys rspadm sapsys 18 210686772

[Hein van den Heuvel]

Ashish,

Check out:

http://forums12.itrc.hp.com/service/forums/questionanswer.do?threadId=1197626

Try /usr/sap/RSP/SYS/exe/run/memlimits | more

Have your sap team explain to you how much memory that are requesting (things like
em/max_size_MB em/initial_size_MB ...)

Eric>> The solution here is to restart the server because your Oracle instance wasn't

How can you tell? Judging by 'ctime' the Oracle sintance was brough up seconds before SAP was started, which is normal no?

Dennis>> You have a bunch of large segments:

Well, yeah, which seems normal for an (partial) start no?

Hein.

[Bart Paulusse · Accepted solution]

Ashis,

log on as sidadm user:
issue "stopsap r3" command
verify that both sap and oracle have stopped.
If there are any sap processes still lingering, "kill" them (and if that doesn't help "kill -HUP or kill -9"

logon as orasid user:
"shutdown immediate" oracle from sqlplus, and check oracle alert log.

log on as sidadm user again:
then "cleanipc " command
if you have any entries returned, remove them with "cleanipc remove"

Now you've removed any sap processes hogging memory.
Have you (or the application team) changed the sap buffersettings recently? You can verify that by looking at the timestamp (or contents) of profile files in directory /sapmnt//profile
If so look for large buffersettings. The message you get means sap tries to reserve more memory for the abap buffer than there is available.

Or have there been changes in the oracle memory settings? Verify that by checking the init.ora or spfile.ora in the /oracle//_64/dbs directory.
If oracle hogs all memory, then sap will never be able to start...

I don't like blame games, but it wouldn't be the first time the "offender" is the first one to start pointing fingers...

regards and good luck,

Bart

[Bart Paulusse]

Ashish,

another question, why don't you use brbackup with the offline_force option? This does an oracle offline backup without stopping sap.
This keeps your sap buffers intact.

regards,

Bart

[AL_3001]

I will put forward your inputs to the SAP team and update you all...