cancel
Showing results for 
Search instead for 
Did you mean: 

Java does not start after installation using system copy method.

Former Member
0 Kudos

Hi All,

We are unable to start the java instance after following the sap suggested approach using export/import method for a new system installation.

The following are few observations.

1)Configtool shows the serverid of the source with the dispatcher process but target does not have any dispatcher uder it.

2) there are no dispatcher directory structure under cluster and cfg under server0.

We did not see any errors during installation. We have changed some of the properties under cluster in the configtool which were pointing to the old host but still the same.

the error from log_bootstrap_ID0513880.0.log is as follows

Jan 5, 2011 3:50:35 PM ] [Bootstrap module]> Problem occurred while performing synchronization.

[Jan 5, 2011 3:51:14 PM ] -


[Jan 5, 2011 3:51:14 PM ] Bootstrap MODE:

[Jan 5, 2011 3:51:14 PM ] <INSTANCE GLOBALS>

[Jan 5, 2011 3:51:14 PM ] determined by parameter [ID0513880].

[Jan 5, 2011 3:51:14 PM ] -


[Jan 5, 2011 3:51:15 PM ] Exception occurred:

com.sap.engine.frame.core.configuration.NameNotFoundException: A configuration with the path "cluster_data/dispatcher/ID51388

000" does not exist.

at com.sap.engine.core.configuration.impl.ConfigurationDataCacheAllImpl.getSubConfiguration(ConfigurationDataCacheAll

Impl.java:107)

at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getSubConfiguration(ReadAccessConfiguration.java:71

5)

at com.sap.engine.bootstrap.Synchronizer.getConfiguration(Synchronizer.java:573)

at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:93)

at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:475)

at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:147)

at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:946)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

[Jan 5, 2011 3:51:15 PM ] Exception occurred:

com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!

at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:477)

at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:147)

at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:946)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

-


==[ Caused by: ]==----


com.sap.engine.bootstrap.SynchronizationException: No such Dialog Instance (ID51388000) in the database! Check database consi

stency or local Bootstrap properties!

at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:96)

at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:475)

at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:147)

at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:946)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)

at java.lang.reflect.Method.invoke(Method.java:391)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

[Jan 5, 2011 3:51:15 PM ] [Bootstrap module]> Problem occurred while performing synchronization.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Have you used the recommended version of JDK before doing the import? ensure the JDK is in place and the environment variable Java_Home is set.

In case the java system is not coming up, then please paste the std_server0.out log.

Rgds,

Soujanya

Former Member
0 Kudos

we have used the right Java version.

Tom. Thanks for this. We did go though this note but need some help if the cfg directory structure gets created during installation or first startup of the server .

TomCenens
Active Contributor
0 Kudos

The directory structures server0 and dispatcher and so on normally get created upon first proper startup

Former Member
0 Kudos

Hi Tom,

The issue is now resolved. Based on your assurance, we tried a different approach. changing the configtool and instance profile with the target SID ,hostnames and other details and it worked like a charm.

Cheers.

TomCenens
Active Contributor
0 Kudos

Hello

The following SAP note has information concerning the Node ID after a SAP system copy:

[Note 831812 - Config Tool shows incorrect parameters after System Copy|https://service.sap.com/sap/support/notes/831812]

Can you check if the note is a match for your issue and provide feedback please ?

Kind regards

Tom