JDBC and other Jars Not Loading IDM 4.7.1

[jwilleke]

RHEL 7.6
eDirectory 9.1.2
IDM Standard" version="4.7.1.0"

Code(-9005) The driver returned a "fatal" status indicating that the driver should be shut down. Detail from driver: <description>Unable to load third-party JDBC driver: 'oracle.jdbc.driver.OracleDriver'.

Have: /opt/novell/eDirectory/lib/dirxml/classes/ojdbc14.jar

/opt/novell/eDirectory/lib64/nds-modules/jre/bin/java -version java version "1.8.0_172"


Driver currently running without issue on older versions:
RHEL 6.x
eDirectory 9.0.3
IDM Standard" version="4.5.5.0"

Any ideas?

Thanks
-jim

[aburgemeister]

On 05/16/2019 07:44 AM, jwilleke wrote:
>
> RHEL 7.6
> eDirectory 9.1.2
> IDM Standard" version="4.7.1.0"

Fairly current code, then, so that's a decent start.

> Code(-9005) The driver returned a "fatal" status indicating that the
> driver should be shut down. Detail from driver: <description>Unable to
> load third-party JDBC driver: 'oracle.jdbc.driver.OracleDriver'.

This looks correct to me, at least in terms of the name, without checking
the appropriate JAR to verify it is in there.

> Have: /opt/novell/eDirectory/lib/dirxml/classes/ojdbc14.jar

The path looks correct, but this is an ancient JAR file; the '14' means it
was meant to work with Java 1.4; you should probably be using ojdbc8.jar
for this version of Java).

> /opt/novell/eDirectory/lib64/nds-modules/jre/bin/java -version java
> version "1.8.0_172"
>
> Driver currently running without issue on older versions:
> RHEL 6.x
> eDirectory 9.0.3
> IDM Standard" version="4.5.5.0"

IDM 4.5 SP5 might have Java 1.8, but I do not remember . Either way, I'd
probably at least swap out your broken ojdbc14.jar with a newer one.
Maybe it's corrupt (check with a checksum) or something else odd has
happened, but it's just a zip-compressed file (as I am sure you know) so
perhaps extract it, or test its extraction, and be sure the class is within:

unzip -t /opt/novell/eDirectory/lib/dirxml/classes/ojdbc14.jar | grep
OracleDriver

One of the results should be OracleDriver.class with a path that looks a
lot like your package/class specified above, having slashes instead of
dots though.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.

[jwilleke]

Well all that seems to check out but no joy.

Tried a newer Oracle jar also with no luck.

We also had some "jar" files and none of them appear to load.

Has anything on the path changed or do we need to modify the env_idm file?

Do there load when eDirectory loads or when vridm loads?

Thanks
-jim

[aburgemeister]

On 05/16/2019 08:44 AM, jwilleke wrote:
>
> Well all that seems to check out but no joy.
>
> Tried a newer Oracle jar also with no luck.
>
> We also had some "jar" files and none of them appear to load.
>
> Has anything on the path changed or do we need to modify the env_idm
> file?
>
> Do there load when eDirectory loads or when vridm loads?

JARs are read when they are needed, which is why if you have NEVER used a
JAR before, you can add it and use it without even restarting eDirectory,
but if you are using version n today you cannot upgrade to n+1 without a
full eDirectory restart.

Just to check a few subtle things, are you SURE you are trying to run the
driver config object on the same box as where you are dropping the JARs?
I've seen clients before try to load a driver object on server-x when
Designer or iManager was actually trying to start the driver object on
server-y. It's not common, but it would explain everything you are seeing.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.

[geoffc]

On 5/16/2019 9:44 AM, jwilleke wrote:
>
> RHEL 7.6
> eDirectory 9.1.2
> IDM Standard" version="4.7.1.0"
>
> Code(-9005) The driver returned a "fatal" status indicating that the
> driver should be shut down. Detail from driver: <description>Unable to
> load third-party JDBC driver: 'oracle.jdbc.driver.OracleDriver'.
>
> Have: /opt/novell/eDirectory/lib/dirxml/classes/ojdbc14.jar
>
Open up ojdbc14.jar and check that the proper main() class is the
OracleDriver. I recall it changed in different ojdbc.jar versions.

[jwilleke]

unzip -t /opt/novell/eDirectory/lib/dirxml/classes/ojdbc7.jar | grep OracleDriver
testing: oracle/jdbc/OracleDriver.class OK
testing: oracle/jdbc/driver/OracleDriver$1.class OK
testing: oracle/jdbc/driver/OracleDriver.class OK
testing: oracle/jdbc/driver/OracleDriverExtension.class OK
-jim