Java CI Installation stopped - Error : Couldn't connect to remote DB

[Former Member]

We are installing NW7.0 SR3 SUSE/Oracle platform on a distributed environment for a Java stack appliation and the CI Install stopped on the step -- Start Java engine when the system is not abel to communicate with remote database running on DB server. We Installed Oracle SQLPlus clinet on the CI Server and the connection at sqlplus level work from CI to DB. But the Installer fail to make connection test to database and the sapinst.log has the following Information.

-

---

J2EE Database is not available via test

See logfile /usr/sap/fd1adm/JdbcCon.log

Database FD1 must be started on remote server

Log on to remote server and start database

-

---

-

---

fd1adm> more /usr/sap/fd1adm/JdbcCon.log

Start: Mon Jan 24 15:55:29 PST 2011

Error: Couldn't connect to DB

com.sap.sql.log.OpenSQLException: Could not load class

com.sap.dictionary.database.catalog.XmlCatalogReader.

-

---

The Environment of the system is given below :

OS : SUSE Linux (SLES 10 SP03)

NW : 7.0 SR3

Usage types : AS Java

Database : Oracle 10.2.0.4

Hardware : Dell X86_64

JDK : IBM JSE 1.4.2 SR13

Media : Downloaded from Market Place.

-

---

Steps for Reconstruction

1. Install Central Services Instance on CI Server. ( Installed correctly )

2. Install Database on DB Server ( Installed and Patched Correctly )

3. Invoke Central Instance Install on CI Server by selecting only AS Java.

4. During running Phase :Start java engine the system encounter the error and stop the Installation.

What would be the cause of DB connectivity Issue ? Are there any tools on Java stack to test DB conenctivity from CI ? SQLPLUS and Telnet on Oracle listener port works correctly from CI to DB Server but the sapinst couln't recognoze the database ....

What could be the reason for database connecivity failure during the CI Installer ? Any specific logs to look for other than the one listed above ?

Edited by: Rukmangada Peddamallu on Jan 25, 2011 3:43 AM

[nirmal_konchada]

Few checks :

1. Does the servers ping each other???

2. Is there any firewall between the servers???

3. Did u make arrangements fr all necessary shares between the servers??? (as per installation guide)

Regards,

Nirmal.K

[Former Member]

Nirmal,

Servers ping each other and I am able to test DB connection (using Oracle SQLclient) from CI to database server. There is no firewall between the servers. Profile shares /sapmnt/<SID> is made available between the servers. The Issue is what ever the tool/program used by sapinst to test connection to database on DB Server while starting Java engine is failing. The sapinst.log doesn't have much details on the cause of the Issue.

Regards,

Ruk

[Former Member]

SAP note 809477 contains a section (with header "05.11.2010") that describes the problem we encounter (i.e. "file stated but does not exist" for several jar archives).

This problem has been fixed in the newer versions of the startsap scriptthat you can download from the SAP Service Marketplace. Replacing older version of startsap/stopsap resolved the problem and completed the CI Installation in the distributed environment.

Thanks,

Ruk