start AS JAVA failed - bootstrap error

[Former Member]

Hello to all,

during the PI upgrade from 7.11 to 7.3 crahsed the software update manager.

We recovered PI from an Backup. Now the AS JAVA is not starting. The bootstrap fails with exit code 500.

Could someone provide some help.

Thanks and regards

Martin

[premsukh_bishnoi]

Hi,

Could you please check the folowings:

1. Check if the following files are located in
/usr/sap/<SID>/SYS/exe/jvm/hpia64/sapjvm_6.1.006/../jre/lib/security/,

local_policy.jar
US_export_policy.jar

If not, you can download from note 1240081.

Regards,

Premsukh

[Former Member]

Hi Premsukh,

thanks for fast response. I've checked your help. The files exists.

Could you tell me, why the system recreate files from 14.11. during the bootstrap, whenn the DB-Backup is from the 07.11.?

How can I force the system, that it have to use the DB-Data for starting java? And how to copy data from db to filesystem?

Thanks and regards

Martin

[hemanth2]

Hi Martin ,

Hope you are doing good.

For that you can use the force bootstrap option.

STEPS:

1)

Stop the j2ee server.

Under cluster directory (/usr/sap/<SID>/J<nr>/cluster) rename server0 and subsequent nodes to ".old" respectively. The intention here is to create a backup of the existing files.

Do not rename the bootstrap folder as this is needed for the sync proces.

2)

Change bootstrap.properties file to ensure it has element.resynch=force as per SAP note 710663.

3)

Restart the J2EE Engine. The new server folders should be created during the bootstrapping and this is a time consuming process as all the contents of the server nodes will be synched with the DB content.

4)

Remove the element.resynch=force property or change it to element.resynch=detect which is the default setting.

Thank you and have a nice day :).

_____________

Kind Regards,

Hemanth

[Former Member]

Hi Hemanth,

thanks for your answer. The steps which you provide are good. Our problem occure some steps before.

When the boostrap start, the system override the files in the folder /usr/sap/<SID>/J<nr>/cluster/bootstrape. After that the bootstrape failed. When we updated the folder during the restart phase with files from 12. Jan. the system starts. When we stop the system and restart it, then the files were override and the bootstrape failed.

Could someone provide some help?

Thanks and best regards

Martin

[hemanth2]

Hi Martin,

Have you checked the dev_bootstrap, jvm_bootstrap and the std_bootstrap files in the work directory for more details about the error?

The system.log in the folder /usr/sap/<SID>/J<nr>/cluster/boostrap/ should also provide valuable insights.

Kind Regards,

Hemanth

[Former Member]

Hi Hemanth,

information from the logs:

jvm_bootstrap:

Starting to initialize database connection

Exception occured for component [internal/unknown] of type [unknown]

...

[Bootstrap] > Error during synchronization.

Do you know what to do?

Thanks and best regards

Martin

[Former Member]

Hi Martin,

For exit code 500 please refer following note:

915825 AS Java Bootstrap Troubleshooting.

It seems that you have to create a OSS message for this exit code and attach the work dir with the OSS message.

Regards,

Vipin

[premsukh_bishnoi]

Hello Martin,

For your issue, please follow below instruction.

Short text          AS Java Bootstrap Troubleshooting 

SAP Note No. 915825

Exit code 500: Unknown exception. For more information, check the
bootstrap logs and see SAP Note 915825.

        The problem is not currently known. Please create a CSS message
        as described above. In the long text include description of what
        can be done to reproduce the problem or what was done before the
        error appeared (upgrade, deploy of AS Java system component,
        etc.). Collect all the logs from the folder
        /usr/sap/<SID>/JC<XX>/work/ and attach the archive to the newly
        created CSS message.

Regards, Premsukh