What is the cause of the error "java.lang.UnsatisfiedLinkError: no ocijdbc11 in java.library.path" in the EMS server log when using the Oracle OCI driver?
Article ID: KB0088733
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
When EMS is configured to usethe OCI driver, EMS server can not be started. The foolowing error is seen in the server log:
java.lang.UnsatisfiedLinkError: no ocijdbc11 in java.library.path
Causes:
======
The error indicates that the EMS server can not locate the OCI driver.
It is due to the change of dynamic loading by EMS server starting in EMS 5.1.2
Resolution:
= = = = = =
You can configure module_path = <OCI_driver_path> in tibemsd.conf to eliminate the above error.
Please refer to SOL1-AS36QO.
Environment:
=========
All
Keywords:
========
OCI driver ocijdbc11
Description:
============
When EMS is configured to usethe OCI driver, EMS server can not be started. The foolowing error is seen in the server log:
java.lang.UnsatisfiedLinkError: no ocijdbc11 in java.library.path
Causes:
======
The error indicates that the EMS server can not locate the OCI driver.
It is due to the change of dynamic loading by EMS server starting in EMS 5.1.2
Resolution:
= = = = = =
You can configure module_path = <OCI_driver_path> in tibemsd.conf to eliminate the above error.
Please refer to SOL1-AS36QO.
Environment:
=========
All
Keywords:
========
OCI driver ocijdbc11
Issue/Introduction
What is the cause of the error "java.lang.UnsatisfiedLinkError: no ocijdbc11 in java.library.path" in the EMS server log when using the Oracle OCI driver?
Feedback
Yes
No
Powered by
