J2EE error starting on MSSQL

[Former Member]

Hi

We are trying to start a standalone J2EE engine for EP5.0. During the bootstrap process it tries to query the MSSQL 2000 SP2 database. The bootstrap fails because it can't connect to the db due the error : Could not continue scan due to NOLOCK with data movement. This is written into the jvm_bootstrap for the dispatcher node.

However we can connect to the db with isql/Query Analyzer and the j2ee configtool. There is nothing else running on this db as it only hosts the portal and this is currently down.

There are no errors in the SQL logs, we have done a dbcc checkdb and it shows no errors.

Can anyone expand of the bootstrap process. Is the jvm_boostrap the first and only boostrap process to connect to the db? If this process can't connect will any others try? Is it the jvm_bootstrap that does the first synchronization of binaries? Is this all binaries or just those related to the JVM?

Thanks and regards

Leigh

[Former Member]

Hi

Thanks so much for the feedback. We eventually followed note 142731 and found consistency errors in a couple of the j2ee tables. The decision was taken to restore the database, after which bootstrap completes successfully and j2ee starts up. Unfortunately when it tries to start the portal applications - we get lots of failures but that's a problem for another post!

Thanks for your assistance

Cheers

Leigh

[Former Member]

Please let me know how to connect sql 2000 from sap was J2EE engine ?

Regards

N P Bhat

[Former Member]

Hello,

Please refer to note 915825 for list of the most command problems associated with bootstrap and instructions how to fix them.

Please post the full error message from the jvm bootstrap log. What is the error number?

If it’s 601 please refer to note 607689.

Note 142731 describes how to do consistency check of the DB. Please check if you followed the same procedure.

There are several bootstrap processes. The first is initial bootstrap and its output is recorded in dev_bootstrap, jvm_bootsrap.out, std_bootstrap.out and log_bootstrap_ID0035151.0.log. After the initial bootstrap, there is bootstrap process for each node (server and dispatcher) and the logs are written to files like dev_bootstrap_ID3515100, jvm_bootstrap_ID3515100.out, log_bootstrap_ID003515100.0.log, etc.. The bootstrap synchronizes most binaries of the J2EE Engine and it runs before the J2EE Engine is started.

You could see the synchronized files in the log files with names like: log_bootstrap_ID003515100.0.log

Regards,

Ventsi Tsachev

Technology Development Support (J2EE Engine)

SAP Labs, Palo Alto, Ca (USA)

[Former Member]

Hi,

As per the startup process for java instance, bootstrap first tries to establish a connection with the database.

Refer http://help.sap.com/saphelp_nw70/helpdata/en/a2/852aca5cd96f4796e51ba0f7a28926/frameset.htm for details.

Hope it explains why you are able to connect to database through queryanalyser and not through bootstrap.

Please check the bootstrap properties file.

Also, some information about the error that you have received:

This is a databse problem. The bootstrap program seems to be trying to access the database using the NOLOCK option. This means that the exclusive lock is not being honoured. If another process is performing an INSERT/UPDATE/DELETE statement on the table, which leads to data being shuffled around, the process which is not honouring locks may suddenly find itself in the middle of nowhere.

So, please check the bootstrap properties and also, please post the logs for detailed error analysis.

Best Regards,

Srividya.R