Symptom
You are running Software Update Manager (SUM) on a J2EE instance and the following error is reported during shadow instance startup:
START-SHADOW-INSTANCE-DM.log
Mar 26, 2018 5:59:50 PM [Info ]: Standard out: F:\usr\sap\XXX\SUM\sdt\log\SUM\SAPCONTROL_WAITFORSTARTED_20_13.OUT
Mar 26, 2018 5:59:50 PM [Info ]: Process ID 12 has been started.
Mar 26, 2018 5:59:50 PM [Info ]: Waiting for process ID 12, name sapcontrol to finish.
Mar 26, 2018 6:00:10 PM [Info ]: Process ID 12, name sapcontrol has been finished, exit code 2.
Mar 26, 2018 6:00:10 PM [Error ]: Return code condition success evaluated to false for process sapcontrol for action wait for started.
Mar 26, 2018 6:00:10 PM [Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Could not start SAP instance with number 20.
Could not check if the instance number 20 on host XXX is started.
Sapcontrol client could not perform action wait for started on instance 20
Return code condition success evaluated to false for process sapcontrol for action wait for started.
SAPCONTROL_WAITFORSTARTED.log
WaitforStarted
FAIL: process jstart.EXE J2EE Server not running
dev_jstart
I [Thr 8548] MPI init, created: pipes=4000 buffers=2718 reserved=815 quota=10%, buffer size=65536, total size MB=170
I [Thr 8548] *** ERROR => FcaInit: already initialized [fcaxxcomm.c 956]
I [Thr 8548] *** ERROR => EvtRmMgt: Evt Mgt Table not init'd [evtnt.c 255]
I [Thr 8548] *** ERROR => ShmDelete: Invalid shared memory Key=62. [shmnt.c 753]
I [Thr 8548] *** ERROR => ShmCleanup: ShmDelete failed for Key:62. [shmnt.c 872]
I [Thr 8548] *** ERROR => ShmCleanup(62) failed 1 [mpixx.c 4615]
F
F ********************************************************************************
F *** ERROR => Node 'bootstrap' failed with exit code 558.
jvm_bootstrap.OUT
com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:497)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.<init>(DBConnectionPoolImpl.java:197)
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandlerImpl.<init>(PersistenceHandlerImpl.java:50)
.....
Caused by: com.sap.sql.log.OpenSQLException: Exception of type com.sap.sql.log.OpenSQLException caught: JDBC driver not supported for ORACLE database..
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:104)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:143)
at com.sap.sql.connect.datasource.DBDataSourceImpl.get(DBDataSourceImpl.java:286)
at com.sap.sql.connect.datasource.DBDataSourceImpl.getPooledConnection(DBDataSourceImpl.java:181)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:213)
at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPoolImpl.createConnection(DBConnectionPoolImpl.java:483)
... 13 more
Caused by: com.sap.sql.log.OpenSQLException: JDBC driver not supported for ORACLE database.
Read more...
Environment
Systems running on NetWeaver, System update to target release NetWeaver 730 or higher
Product
Keywords
ODBC driver, Oracle Instant client , KBA , BC-DB-ORA , Oracle , BC-UPG-TLS-TLJ , Upgrade tools for Java , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.