STOPSAP Problems on DoubleStack Systems

[Former Member]

Hello together,

for a long time we have problems during the shutdown of double stack systems.

We stop our DoubleStack systems with the following command as <SID>OFR or <SID>ADM:

STOPSAP SID('<sid>') INSTANCE(*ALL)

Now the main instance DVEBMGS<nn> is stopped. But the SCS is still running.

Only a STOPSAP command especially for the SCS helps to shutdown the SCS:

STOPSAP SID('<sid>') INSTANCE(<numer of SCS>)

We are running sap on IBM i V7R1 with a Kernel version 7.20.

The problem ocurrs on different systems with different versions of Kernel 7.20.

Maybe someone knows the problem and can help us.

Thanks in advance.

Tobias

[joachim_kern · Accepted solution]

Hi Tobias,

Could you please check the joblog of your session, where you call STOPSAP.

Does it contain lines like:

     'StopAllInstances: Failed to stop instance .....'

or

     'StopAllInstances: Failed to stop central instance .....'

Such an error message will break the loop to shutdown all instances.

Maybe immediately before such a line you will get more information what happened.

If you find something, could you please add a joblog extraction to this thread.

Best regards

Joachim

[Former Member · Accepted solution]

Hello Joachim,

thanks for the hint. Yes I found some problems. And there seems to be a problem during the shutdown of main instance (sysnr 91) and not of the scs (sysnr92).

Nevertheless the main instance was stopped the scs not.

Here the extraction of the joblog:

Stopping instance 91 of system <sid>...

Waiting 120 seconds for instance 91 of system <sid> to shutdown

WaitForInstanceShutdown: Instance 91 of system <sid> not down after 120 seconds.            

StopInstance: Instance 91 of system <sid> still running.                                      

StopAllInstances: Failed to stop central instance 91 of system <sid> on host <hostname>    

O4STRSTP: Stopping all instances of system <sid> failed.        

Best regards

Tobias

[joachim_kern · Accepted solution]

Hello Tobias,

This is the reason:

WaitForInstanceShutdown: Instance 91 of system <sid> not down after 120 seconds.           

Your central Instance needs to long to shutdown, so the whole procedure stopps.

It is a known 'problem', because JAVA needs a long time to start and to shut down.

Please increase the waittime accordingly

     Wait for instance to end . . . . WAIT         > *YES        

     Maximum wait time (seconds)  . . WAITTIME     > 600     

and try again.

Best regards

Joachim

[Former Member · Accepted solution]

Hello Joachim,

ok. I understand. That makes sense.

At the moment I can't try a shutdown of these Systems but I think to increase the waittime could help.

Best regards

Tobias

[Former Member]

Dear Tobias:

There is probably a file with no extension in the /sapmnt/<SID>/profile; please check the files.

Regards.

Henry

[Former Member]

Hello Henry,

I think you mean the profiles. Start profile, instance profile, default profile... what shoul I check in the profiles?

[Former Member]

Dear Tobias:

I mean they probably made a copy of a profile, and that new file has a name without extension eg: <profile>_backup and should be corrected as follows: <profile>_backup.BAK

Regards

Henry

[Former Member]

Thanks for your reply. But there aren't such files....

[Former Member]

have you tried to stop using -t as option?

stopsap -t all

Syntax:

stopsap -t  r3|j2ee -i <instance>

[Former Member]

Hello Sunil,

the parameter "-t" it's not available on the IBMi Plattform....