EP Upgrade from 7.0 to 7.3EHP1

[Former Member]

Hi All,

We are doing enterprise java portal upgrade from 7.0 to 7.3EHP1.We are reached start shadow instance step of pre-processing phase.

In this phase,we have received below mentioned error.

"could not start SAP instance with number 2.The instance with number 2 on host <host name> could not be started within the specified timeout".

We are not able to see the start profile for shadow instance in /usr/sap/<SID>/SUM/sdt/<SID>/SYS/profile/ path.At the same time shadow

instances(JC02) are not getting started and could not check the status for shadow instance through command jcmon pf=<instance profile name> its showing.

command => 20

Can't open shared memory administration (rc = 3)

But shadow instance process are can able to see with ps -ef|grep sapstartsrv command. We observed that shadow instance server0 log directory returning this error in default trace file(/usr/sap/<SID>/SUM/sdt/<SID>/JC02/j2ee/cluster/server0/log/defaultTrace_00.0.trc) .

"""Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start] """

As per note 1937296 we have upgraded the kernel in shadow instance with latest level.After we started it again with the same step.Still we are unable to proceed further and again getting same error.

"could not start SAP instance with number 2.The instance with number 2 on host <host name> could not be started within the specified timeout".

Kindly share your inputs to fix this issue.

Regards,

Kubendran A

[Former Member · Accepted solution]

Hi

Can you please check the note 1836705 whether it helps you.  Have you updated to the currect kernel and I assume your kernel upgrade is done correctly.

Usually Kernel upgrade should resolve the issue.

Regards,
Deepanshu Sharma

[Former Member · Accepted solution]

Hi Deepanshu,

Thanks for the Info.Already done kernel upgrade with latest version.But no luck,Due to this issue upgrade got stuck.

During this shadow instance creation step logs are generating with below details /<SUM>/sdt/log/SWITCH/START-SHADOW-INSTANCE-DM_07   path.

Apr 11, 2014 4:09:24 PM [Info  ]: Starting instance number 2 on host epqas with timeout of 7200 seconds.

Apr 11, 2014 4:09:24 PM [Info  ]: Sent the start command to instance number 2 on host epqas with timeout of 7200 seconds.

Apr 11, 2014 4:09:24 PM [Info  ]: All retrieved instances : 1

Apr 11, 2014 4:09:24 PM [Info  ]: Correctly detected instance: 2 on host epqas

Apr 11, 2014 4:09:24 PM [Info  ]: Instance has status STOPPED.

Apr 11, 2014 4:09:29 PM [Info  ]: All retrieved instances : 1

Apr 11, 2014 4:09:29 PM [Info  ]: Correctly detected instance: 2 on host epqas

Apr 11, 2014 4:09:29 PM [Info  ]: Instance has status STOPPED.

Apr 11, 2014 4:09:34 PM [Info  ]: All retrieved instances : 1

Apr 11, 2014 4:09:34 PM [Info  ]: Correctly detected instance: 2 on host epqas

Apr 11, 2014 4:09:34 PM [Info  ]: Instance has status STOPPED.

Apr 11, 2014 4:09:40 PM [Info  ]: All retrieved instances : 1

Apr 11, 2014 4:09:40 PM [Info  ]: Correctly detected instance: 2 on host epqas

Regards,

Kubendran

[Sriram2009 · Accepted solution]

Hi

Could you refer the SAP Notes

1853913 - J2EE engine startup fails due to user with unique name already exists error

1794176 - J2EE System fails with "exitcode 2150"

1562141 - Application Server Java cannot start during upgrade to 7.30

Regards

Sriram

[Former Member · Accepted solution]

Hi All,

Issue is resolved now... Thanks for info provided..

updated latest kernel version in actual system and shadow instance also.Issue got fixed.

Regards,

Kubendran

[Former Member · Accepted solution]

HI KUbendran,

Good to hear that your issue got resolved. I have asked you in first reply itself stating "I assume your kernel upgrade is done correctly"

Good that it resolved.

Regards,

Deepanshu Sharma