Home

Results 1 to 3 of 3

Thread: Driver JDBC 3.6.0 shut down unexpectedly -

  1. #1
    shinojosa NNTP User

    Driver JDBC 3.6.0 shut down unexpectedly -


    I have two servers IDM 4.0.2 Patch 1a (IDM1 and IDM2) whit JDBC driver
    3.6.0, connected to Oracle 11g. The driver up and run correctly on IDM1
    but when i shutdown the driver and try to up it on IDM2, the driver
    start to process and a few seconds after it turn off.

    I dont know if the next error produce this action:

    > 734587:[04/12/13 12:11:54.464]:IDM_ExportIRM PT:Metadata has been
    > retrieved.
    > 734588:[04/12/13 12:11:54.464]:IDM_ExportIRM PT:BEGIN Set transaction
    > isolation level.
    > 734589:[04/12/13 12:11:54.464]:IDM_ExportIRM PT: CALLING
    > Connection.getTransactionIsolation()
    > 734590:[04/12/13 12:11:54.464]:IDM_ExportIRM PT: CALLED
    > 734591:[04/12/13 12:11:54.465]:IDM_ExportIRM PT: Transaction isolation
    > level: read committed
    > 734592:[04/12/13 12:11:54.465]:IDM_ExportIRM PT:END Set transaction
    > isolation level.
    > 734593:[04/12/13 12:11:54.465]:IDM_ExportIRM PT:Interpreting filter.
    > 734594:[04/12/13 12:11:54.465]:IDM_ExportIRM PT:Unhandled Exception:
    > java.lang.NoSuchMethodError:
    > com.novell.nds.dirxml.driver.jdbc.util.table.JDBCP arentTable.getReferential()Z
    > 734595:[04/12/13 12:11:54.466]:IDM_ExportIRM
    > PT:java.lang.NoSuchMethodError:
    > com.novell.nds.dirxml.driver.jdbc.util.table.JDBCP arentTable.getReferential()Z
    > 734596: at
    > com.novell.nds.dirxml.driver.jdbc.JDBCTriggerlessP ublicationShim.detectCycles(Unknown
    > Source)
    > 734597: at
    > com.novell.nds.dirxml.driver.jdbc.JDBCTriggerlessP ublicationShim.afterConnect(Unknown
    > Source)
    > 734598: at
    > com.novell.nds.dirxml.driver.jdbc.JDBCPublicationS him.initialConnect(Unknown
    > Source)
    > 734599: at
    > com.novell.nds.dirxml.driver.jdbc.JDBCPublicationS him.start(Unknown
    > Source)
    > 734600: at
    > com.novell.nds.dirxml.driver.jdbc.JDBCPublicationP roxy.start(Unknown
    > Source)
    > 734601: at
    > com.novell.nds.dirxml.engine.Publisher.run(Publish er.java:519)
    > 734602: at java.lang.Thread.run(Unknown Source)
    > 734603:
    > 734604:[04/12/13 12:11:54.467]:IDM_ExportIRM PT:Shutting down...


    The extended log is in http://pastebin.com/JDNFLP39

    Anybody have any idea about what happens?
    Thanks in advance.


    --
    shinojosa
    ------------------------------------------------------------------------
    shinojosa's Profile: https://forums.netiq.com/member.php?userid=539
    View this thread: https://forums.netiq.com/showthread.php?t=47543


  2. #2
    Join Date
    Dec 2007
    Location
    Brooklyn, NY
    Posts
    6,213

    Re: Driver JDBC 3.6.0 shut down unexpectedly -

    The error is:
    java.lang.NoSuchMethodError:
    com.novell.nds.dirxml.driver.jdbc.util.table.JDBCP arentTable.getReferential()Z

    So the server it shuts down on, cannot find a class it needs.

    The JDBC driver has its core NetIQ provided JDBC IDM driver shim.

    But you need an additional JAR for the target DB, so oracle has a couple
    of versions. There is jTDS as well which is a good replacement for many
    vendor specific JARs.

    But the class seems like it should be in the NetIQ provided JAR.

    Look at the directory holding your jars (something like
    /opt/novell/eDirectory/dirxml/classes or somesuch, under eDir not IDM,
    as you would expect) and compare the two folders for different files and
    versions.


    On 4/12/2013 12:04 PM, shinojosa wrote:
    >
    > I have two servers IDM 4.0.2 Patch 1a (IDM1 and IDM2) whit JDBC driver
    > 3.6.0, connected to Oracle 11g. The driver up and run correctly on IDM1
    > but when i shutdown the driver and try to up it on IDM2, the driver
    > start to process and a few seconds after it turn off.
    >
    > I dont know if the next error produce this action:
    >
    >> 734587:[04/12/13 12:11:54.464]:IDM_ExportIRM PT:Metadata has been
    >> retrieved.
    >> 734588:[04/12/13 12:11:54.464]:IDM_ExportIRM PT:BEGIN Set transaction
    >> isolation level.
    >> 734589:[04/12/13 12:11:54.464]:IDM_ExportIRM PT: CALLING
    >> Connection.getTransactionIsolation()
    >> 734590:[04/12/13 12:11:54.464]:IDM_ExportIRM PT: CALLED
    >> 734591:[04/12/13 12:11:54.465]:IDM_ExportIRM PT: Transaction isolation
    >> level: read committed
    >> 734592:[04/12/13 12:11:54.465]:IDM_ExportIRM PT:END Set transaction
    >> isolation level.
    >> 734593:[04/12/13 12:11:54.465]:IDM_ExportIRM PT:Interpreting filter.
    >> 734594:[04/12/13 12:11:54.465]:IDM_ExportIRM PT:Unhandled Exception:
    >> java.lang.NoSuchMethodError:
    >> com.novell.nds.dirxml.driver.jdbc.util.table.JDBCP arentTable.getReferential()Z
    >> 734595:[04/12/13 12:11:54.466]:IDM_ExportIRM
    >> PT:java.lang.NoSuchMethodError:
    >> com.novell.nds.dirxml.driver.jdbc.util.table.JDBCP arentTable.getReferential()Z
    >> 734596: at
    >> com.novell.nds.dirxml.driver.jdbc.JDBCTriggerlessP ublicationShim.detectCycles(Unknown
    >> Source)
    >> 734597: at
    >> com.novell.nds.dirxml.driver.jdbc.JDBCTriggerlessP ublicationShim.afterConnect(Unknown
    >> Source)
    >> 734598: at
    >> com.novell.nds.dirxml.driver.jdbc.JDBCPublicationS him.initialConnect(Unknown
    >> Source)
    >> 734599: at
    >> com.novell.nds.dirxml.driver.jdbc.JDBCPublicationS him.start(Unknown
    >> Source)
    >> 734600: at
    >> com.novell.nds.dirxml.driver.jdbc.JDBCPublicationP roxy.start(Unknown
    >> Source)
    >> 734601: at
    >> com.novell.nds.dirxml.engine.Publisher.run(Publish er.java:519)
    >> 734602: at java.lang.Thread.run(Unknown Source)
    >> 734603:
    >> 734604:[04/12/13 12:11:54.467]:IDM_ExportIRM PT:Shutting down...

    >
    > The extended log is in http://pastebin.com/JDNFLP39
    >
    > Anybody have any idea about what happens?
    > Thanks in advance.
    >
    >



  3. #3
    shinojosa NNTP User

    Re: Driver JDBC 3.6.0 shut down unexpectedly -


    Thanks Geoffc,

    Patch JDBC_Driver_v360.tar.gz was applicated on IDM1 but the restart of
    eDir wasn't done. So i guess the eDir didn't have the correct Jars.
    After the edir restart, the driver started withot problems.

    Thanks a lot.

    Regards.


    --
    shinojosa
    ------------------------------------------------------------------------
    shinojosa's Profile: https://forums.netiq.com/member.php?userid=539
    View this thread: https://forums.netiq.com/showthread.php?t=47543


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •