BI production down

[Former Member]

Hi,

While starting BI production server we are getting the following error

in sapstart.log

(770176) Starting: local se.sapFBP_DVEBMGS23

pf=/usr/sap/FBP/SYS/profile/FBP_DVEBMGS23_fbpci-db -F

(811034) Starting: local ig.sapFBP_DVEBMGS23 -mode=profile

pf=/usr/sap/FBP/SYS/profile/FBP_DVEBMGS23_fbpci-db

(483480) Waiting for Child Processes to terminate.

(811034) New Child Process created.

(811034) Starting local Command:

Command: ig.sapFBP_DVEBMGS23

-mode=profile

pf=/usr/sap/FBP/SYS/profile/FBP_DVEBMGS23_fbpci-db

(483480) **** 2007/05/19 11:06:57 Caught Signal to Stop all Programs.

****

(483480) Parent Shutdown at 2007/05/19 11:06:59

(483480) Stop Child Process: 811034

(483480) Wait 300 sec for Process 811034 terminating...

(483480) Stop Child Process: 770176

(483480) Wait 300 sec for Process 770176 terminating...

(483480) Stop Child Process: 368744

(483480) Wait 300 sec for Process 368744 terminating...

(483480) Stop Child Process: 950304

(483480) Wait 300 sec for Process 950304 terminating...

Execute Post-Shutdown Commands

-

---

(483480) Exiting with Return-Code 0. (Ok)

Cannot create Lock File. ("sapstart.sem" Invalid file system control

data detected)

(901218) Exiting with Return-Code -103. (Access permission denied)

Cannot create Lock File. ("sapstart.sem" Invalid file system control

data detected)

(745538) Exiting with Return-Code -103. (Access permission denied)

Cannot create Lock File. ("sapstart.sem" Invalid file system control

data detected)

(778438) Exiting with Return-Code -103. (Access permission denied)

We cleaned ipc and shared memory before starting the instance.

Please reply as it is our production system.

Regards,

Manish S.

[Former Member · Accepted solution]

Hi Manish,

Please delete sapstart.sem and then try to restart the system.

Regards.

Ruchit

[Former Member · Accepted solution]

Hi,

I tried this grep command but I dint found anu IPC process and I also check sapstart.sem in work directory but that file was already deleted by stop command.

Regards,

Manish S.

[Former Member · Accepted solution]

Hi,

Could you please let me know dtabase details?

check database status ..

Regards

Ben

[Former Member · Accepted solution]

Hi,

Database is DB2 8.2

and it was up and running we have distributed systems.

Now the system is up but for that we have to reboot the LPAR which we could not do in future if same problem arises.

We checked at the OS level and told to unix team for any errors for the same from AIX point of view but they told now errors at OS level.

Regards,

Manish

[Former Member · Accepted solution]

Hi All,

I dont whether it is right method or not but I just ask the OS Unix guys to restart the LPAR and than i tried starting with the application and it worked.

Thanks for your support

[Former Member · Accepted solution]

This can also be caused by the simple fact that the sidadm user doesnt own the usr/sap/dir or the sapmnt dir, always check that first.

[Former Member]

Hi,

Could you please let me know the OS.

If the OS is AIX ..

Please use following commands

ICPS | grep -i <SID>

using the command ipcrm ... you have to clean memory sigments ..

ipcrm <-q or -s or -m options > process ID..

-

---

or

Restart server

Regards

Ben