Unable to start JNEP processes, Could not instantiate JDBC driver
(Doc ID 2686987.1)
Last updated on JANUARY 23, 2024
Applies to:
Oracle Communications ASAP - Version 7.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
ASAP 7.3 installed afresh. Later, cartridge installation was done. Post which, cannot see JNEP processes in status command output. Also, some permission error can be seen in JNEP*.diag.
JNEP diag
>> 154617.746:main:LOW :<
Initialising Sybase JDBC connection.
>> 154617.747:main:PROG:<
Could not instantiate JDBC driver: java.lang.ClassNotFoundException: com.sybase.jdbc4.jdbc.SybDriver
>> 154617.748:main:SANE:com.mslv.activation.server.ControlConnection:
Establishing connection with Open Server CTRLxxx
>> 154617.749:main:SANE:com.mslv.activation.server.ControlConnection:
Opened interfaces file <ASAP_BASE>/SYBASE/interfaces
>> 154617.750:main:LOW :com.mslv.activation.server.ControlConnection:
Found server definition for xxx
>> 154617.750:main:LOW :com.mslv.activation.server.ControlConnection:
Host: 'xxxxxx', port: [40051]
>> 154617.908:main:PROG:com.mslv.activation.server.ControlConnection:
Could not open connection to Open Server xxx: java.sql.SQLException: No suitable driver found for jdbc:sybase:Tds:xxxxxx:40051
>> 154617.908:main:PROG:com.mslv.activation.server.ControlConnection:
ASAP.console
CSF: Error encountered while retrieving 'sarmxxx' credentials from: <ASAP_BASE>/install/cwallet.sso
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |