AS JAVA not starting after changing hostname and configtool can't connect.

[Former Member]

Hello,

As as restore tes, we backed up our Sol Man 7.0 (Dual stack {AS ABAP + AS JAVA}) and restore it in other hostnames (We got 1 DB server and 1 CI server).

The AS ABAP is comming up OK, but the AS JAVA does not start.

We followed the notes:

1) Note 8307 - Changing host name on R/3 host: What do you do?

2) Note 757692 - Changing the hostname for J2EE Engine 6.40/7.0 installation

Now, when we try to execute the "3.Adapt Secure Store properties" of the 757692 note, the configtool cannot connect to DB.

The connection fails with the following error:

com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)

at com.sap.engine.configtool.visual.ConfigTool.loadClusterData(ConfigTool.java:99)

at com.sap.engine.configtool.visual.ConfigTool.initScan(ConfigTool.java:87)

at com.sap.engine.configtool.visual.ConfigTool.<init>(ConfigTool.java:82)

at com.sap.engine.configtool.visual.ConfigTool.main(ConfigTool.java:961)

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

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

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

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: java.sql.SQLException: Io exception: The Network Adapter could not establish the connection

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255)

at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:387)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:420)

at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)

at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)

at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)

at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)

at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:608)

at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)

at com.sap.engine.configtool.visual.ConfigTool.loadClusterData(ConfigTool.java:99)

at com.sap.engine.configtool.visual.ConfigTool.initScan(ConfigTool.java:87)

at com.sap.engine.configtool.visual.ConfigTool.<init>(ConfigTool.java:82)

at com.sap.engine.configtool.visual.ConfigTool.main(ConfigTool.java:961)

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

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

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

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)

-

---

We had check the user ID "admin/password/SMD" and "jdbc/pool/SMD/User" and reset password for the "admin/user/SMD" and "jdbc/pool/SMD/Password" to make sure is not a password issue.

License was applied sucessfully on SLICENSE, and like I said everything looks OK on AS ABAP and we did restore everything at OS & Filesystem level.

Any help is appreciated,

Hugo Mendoza

[Former Member]

The problem was solved by identifying the Oracle port and have adjusted accordingly.

[Former Member]

We get that Marcus and thanks for the observations. We did adjust the profiles on the SYS/profile file system, dbhost and dbadminurl profile parameters and at least we should be able to launch the configtool, however, is not happening.

The issue is simply that the config tool is nto able to get connected to the DB, I had adjusted the jdbc/pool/<SID>/Url and admin/host/<SID> without luck. Once I am able to get it working, then I can start the trail an error for the Java engine.

Hugo.

[Former Member]

Hello Markus,

The note 757692 is clear about the meaning that this approach does not replace the SAP official system copy procedure and MUST NOT be used for copying of an instance to another host and/or with different SID.

This is a test restore only, we'll wipe out the instance once we are done, but for the moment we would like to start up the Java engine.

Any help is appreciated.

Hugo Mendoza.

[markus_doehr2]

There are more than a dozen places where you have the wrong hostname, partly stored in the database partly on the filesystem in .properties files. Database entries may or may not be synced back to the filesystem (there was a not explaining this, I can´t find it, maybe it´s pulled back), it´s not documented what you need to change all so you have to try-and-error.

Markus

[markus_doehr2]

What you did is not supported.

System copies of instances containing Java must be done using sapinst.

Markus