I've got a customer that is using the remote loader configuration with
an Informix DB server. The Utilization of the DB server peaks when the
driver starts to communicate with the JDBC driver on the DB server. The
vault is SLES10SP1 with IDM351. Informix v9 is running on HP-UX. In
trying to get away from doing the remote loader and move the JDBC driver
back to the IDM vault with Java, I continue to get the following:
<-- Begin Paste -->
[02/19/08 14:07:37.845]:IDV2IFAS ST:Initializing driver shim.
[02/19/08 14:07:37.846]:IDV2IFAS ST:Reading XML attribute
[02/19/08 14:07:37.860]:IDV2IFAS ST:Reading XML attribute
[02/19/08 14:07:37.864]:IDV2IFAS ST:Reading driver information from the
[02/19/08 14:07:37.865]:IDV2IFAS ST:Loading Java shim
[02/19/08 14:07:37.867]:IDV2IFAS ST:
DirXML Log Event -------------------
Message: Code(-9010) An exception occurred:
at com.novell.nds.dirxml.engine.Driver.loadShim(Drive r.java:1204)
at com.novell.nds.dirxml.engine.Driver.startShim(Driv er.java:1280)
at com.novell.nds.dirxml.engine.Driver.initialize(Dri ver.java:254)
at com.novell.nds.dirxml.engine.Driver.<init>(Driver. java:226)
at java.lang.Thread.run(Unknown Source)
[02/19/08 14:07:37.881]:IDV2IFAS STriver terminated.
<-- End Paste -->
We took the JAR files from the informix server and copied them to
/usr/lib/dirxml/classes on the vault server. I've also downloaded
version 2.1, 3.0 and 3.1 from IBM to ensure I've covered that area.
Any help with either reducing CPU utilization on the HP-UX remote loader
config or running the JDBC on the vault would be most appreciated.