cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Startup Failure - SHMDETACH

0 Kudos

Hi all,

I am fully aware this issue has been covered, but I will outline exactly which steps I have followed and if anyone has any other suggestions, they'd be appreciated.

We have 3 systems (R/3, BI and Portal) running on a server. We rebooted the server recently, and now the R/3 system won't start up again. I can start up the BI and Portal without a problem, but when I start the R/3, it fails with the following error.

vrdadm> startsap

Checking VRD Database

-


Database is running

Starting Startup Agent sapstartsrv

-


Instance Service on host zamdc20163 started

Starting SAP Instance DVEBMGS00

-


Startup-Log is written to /home/vrdadm/startsap_DVEBMGS00.log

Startup of Instance failed

See /home/vrdadm/startsap_DVEBMGS00.log for details

vrdadm> cat /home/vrdadm/startsap_DVEBMGS00.log

Trace of system startup/check of SAP System VRD on Sat Dec 10 13:20:26 SAST 2011

Called command: /usr/sap/VRD/SYS/exe/run/startsap start

Starting Startup Agent sapstartsrv

-


Instance Service on host zamdc20163 started

Starting SAP Instance DVEBMGS00

-


SAP-R/3-Startup Program Rel 701 V1.8 (2003/04/24)

-


Starting at 2011/12/10 13:20:36

Startup Profile: "/usr/sap/VRD/SYS/profile/VRD_DVEBMGS00_zamdc20163"

Starting Programs

-


(2098) Waiting for Child Processes to terminate.

(2098) **** No more Child Processes to wait for.

(2098) Parent Shutdown at 2011/12/10 13:20:36

Execute Post-Shutdown Commands

-


10.12.2011 13:20:36

ShmDetach

OK

(2098) Exiting with Return-Code 3. (No more child processes)

Startup of Instance failed

vrdadm>

****************************

vrdadm> cat dev_sapstart

-


trc file: "dev_sapstart", trc level: 1, release: "701"

-


Sat Dec 10 13:16:11 2011

SigISetDefaultAction : default handling for signal 17

vrdadm>

****************************

I have made sure the kernel is at the latest patch level, and I have restarted the server, so using cleanipc is unnecessary.

The WORK directory is not being updated with useful files, as I don't think the startup gets that far (dev_w0 etc).

Does anyone have any other suggestions?

thanks.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Bradley,

dev_disp is also not updated under work directory? Please check.

Please perform the following steps.

1. Run SAPPFPAR pf=<instance profile path. CHECK command with SIDADM.

2. Take necessary actions against errors.

3. Stop SAP

4. Kill any active process and clean IPC

5. Start SAP.

Good Luck.

Thanks,

Siva Kumar

0 Kudos

Hi there sir,

I have already done this, and there were no errors, unfortunately.

As to the WORK directory, here are the only files that get written after the startsap command is run...

-rw-rw-r-- 1 vrdadm sapsys 626 Dec 10 11:09 sapstartsrv.old

-rw-rw-r-- 1 vrdadm sapsys 626 Dec 10 12:58 sapstartsrv.log

-rw-rr 1 vrdadm sapsys 240 Dec 10 13:20 dev_sapstart

-rw-rw-r-- 1 vrdadm sapsys 0 Dec 10 14:16 dev_tp.old

-rw-rw-r-- 1 vrdadm sapsys 0 Dec 10 14:32 dev_tp

-rw-rr 1 vrdadm sapsys 513 Dec 10 14:33 sapstart.log

-rw-rw-r-- 1 vrdadm sapsys 332 Dec 10 14:33 INSTSTAT

-rw-rr 1 vrdadm sapsys 41928806 Dec 10 14:46 available.log

Answers (2)

Answers (2)

Former Member
0 Kudos

The issue has resolved which has occured on Linux 3.0.101-0.46-default. The work directory was not giving any info except the INSTSTAT.log was giving info saying "Exit with 3 No more child processes."

The root cause was, the sapstart process, was hanging.

Resolutioin was, the kill -9 command worked to kill the process and the SAP instance has started.

Clean the processes, that might help in this situation.

Regards,

Durga PK Saitana

Former Member
0 Kudos
0 Kudos

Hi Srini,

Thanks, but, as stated, the /work directory isn't being updated, and the system was rebooted, so cleanipc is not required.

Former Member
0 Kudos

Hello Bradley,

Please check how much of physical memory is being used by other 2 instances on the server. I doubt, physical memory is not enough to share memory for this 3rd instance.

Please look at log sapstart.log under work directory.

Thanks,

Siva Kumar

Edited by: Siva Kumar Arivinti on Dec 11, 2011 6:46 PM

0 Kudos

Hi there,

The system has more than enough memory, but even with the other two systems off, it has the same error.

Can you make sense of this log?

vrdadm> cat sapstart.log

SAP-R/3-Startup Program Rel 701 V1.8 (2003/04/24)

-


Starting at 2011/12/11 14:58:40

Startup Profile: "/usr/sap/VRD/SYS/profile/VRD_DVEBMGS00_zamdc20163"

Starting Programs

-


(25820) Waiting for Child Processes to terminate.

(25820) **** No more Child Processes to wait for.

(25820) Parent Shutdown at 2011/12/11 14:58:40

Execute Post-Shutdown Commands

-


(25820) Exiting with Return-Code 3. (No more child processes)

Former Member
0 Kudos

It looks strange. I don't see any clue from the log.

Can you check all SAP file systems exist on this server with proper ownership and permissions?

Thanks,

Siva Kumar

0 Kudos

Hi there,

I know, that log is useless. I can't think of any decent places to check logs besides the /work and /usr/sap/tmp directory.

The filesystem seems intact. I am able to perform other commands from the command line, so the path is correct.

I am able to execute BRTOOLS.

Any other suggestions?

0 Kudos

Good day,

After a long weekend of searching...

Someone had deleted the START profile from the /profile directory, so I had to rebuild one from another system.

Thanks for all the suggestions.

Former Member
0 Kudos

Hello Bradley,

Glad to hear that issue is resolved. So start profile screwed up your week end.

Thanks,

Siva Kumar

Former Member
0 Kudos

> Someone had deleted the START profile from the /profile directory, so I had to rebuild one from another system.

This is something you should work on, for the safety and security of your sap landscape and ultimately the customer's business.

You should have something in place to find out how did this 'deletion' happen at OS level.

Thanks