We upgraded to IDM 3.5 (engine and drivers) in our test lab, however when
we went to test our upgraded JDBC driver for our Lawson HR system (on
Oracle9i), we no longer had a connection. (Yes, we do realize that we
should have confirmed that the driver was working PRIOR to upgrading it.)
We discovered that the Lawson test server was changed and we weren’t
notified. When we reconnected to the new test server with the upgraded
driver, changes would not sync and this is what the log shows:

[04/26/07 14:33:22.388]:LAWSON JDBC PT:BEGIN Row.
[04/26/07 14:33:22.388]:LAWSON JDBC PT: RECORD_ID: 343057
[04/26/07 14:33:22.388]:LAWSON JDBC PT: TABLE_KEY:
'empnbr=16217'
[04/26/07 14:33:22.389]:LAWSON JDBC PT: STATUS: 'N'
[04/26/07 14:33:22.389]:LAWSON JDBC PT: EVENT_TYPE: 3; update
field (remove-all-values)
[04/26/07 14:33:22.389]:LAWSON JDBC PT: PERPETRATOR: NULL
[04/26/07 14:33:22.389]:LAWSON JDBC PT: TABLE_NAME: 'idm'
[04/26/07 14:33:22.389]:LAWSON JDBC PT: COLUMN_NAME:
'p01dept_desc'
[04/26/07 14:33:22.389]:LAWSON JDBC PT: OLD_VALUE: NULL
[04/26/07 14:33:22.389]:LAWSON JDBC PT: NEW_VALUE: 'I.S. -
Enterprise Dev '
[04/26/07 14:33:22.389]:LAWSON JDBC PT:END Row.
[04/26/07 14:33:22.389]:LAWSON JDBC PT:SELECT EMPNBR, TERM_DATE,
DATE_HIRED, ADJ_HIRE_DATE, BIRTHDATE FROM DIRXML.IDM WHERE EMPNBR = ?
[04/26/07 14:33:22.390]:LAWSON JDBC PT: IN @ index 1, field
'EMPNBR', value = 20424
[04/26/07 14:33:22.394]:LAWSON JDBC PT: RS field 'TERM_DATE',
length: 21, value = '1700-01-01 00:00:00.0'
[04/26/07 14:33:22.395]:LAWSON JDBC PT: RS field 'DATE_HIRED',
length: 21, value = '2003-06-03 00:00:00.0'
[04/26/07 14:33:22.395]:LAWSON JDBC PT: RS field
'ADJ_HIRE_DATE', length: 21, value = '2003-06-03 00:00:00.0'
[04/26/07 14:33:22.395]:LAWSON JDBC PT: RS field 'BIRTHDATE',
length: 21, value = '1982-08-13 00:00:00.0'
[04/26/07 14:33:22.399]:LAWSON JDBC PT:Receiving DOM document from
application.
[04/26/07 14:33:22.400]:LAWSON JDBC PT:
<nds dtdversion="2.0" ndsversion="8.x" xmlns:jdbc="urn:dirxml:jdbc">
<source>
<product build="20070301_0610" instance="LAWSON JDBC"
version="3.5.0">DirXML Driver for JDBC</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<status level="error" type="driver-general">
<description>java.lang.NullPointerException</description>
<jdbc:exception jdbc:class="java.lang.NullPointerException">
<jdbc:stack-trace>java.lang.NullPointerException
at
com.novell.nds.dirxml.driver.jdbc.util.event.JDBCE vent.GetPerpetrator(Unknown
Source)
at
com.novell.nds.dirxml.driver.jdbc.util.event.JDBCE vent.getPerpetratorsAsString(Unknown
Source)
at
com.novell.nds.dirxml.driver.jdbc.JDBCTriggeredPub licationShim.appendCustomEventInfo(Unknown
Source)
at
com.novell.nds.dirxml.driver.jdbc.JDBCTriggeredPub licationShim.appendModifyElement(Unknown
Source)
at
com.novell.nds.dirxml.driver.jdbc.JDBCTriggeredPub licationShim.handleModify(Unknown
Source)
at
com.novell.nds.dirxml.driver.jdbc.JDBCTriggeredPub licationShim.appendEvent(Unknown
Source)
at
com.novell.nds.dirxml.driver.jdbc.JDBCTriggeredPub licationShim.appendEvents(Unknown
Source)
at
com.novell.nds.dirxml.driver.jdbc.JDBCTriggeredPub licationShim.handleEventGroup(Unknown
Source)
at
com.novell.nds.dirxml.driver.jdbc.JDBCTriggeredPub licationShim.waitForEvents(Unknown
Source)
at
com.novell.nds.dirxml.driver.jdbc.JDBCPublicationS him.pollImpl(Unknown
Source)
at
com.novell.nds.dirxml.driver.jdbc.JDBCPublicationS him.pollLoop(Unknown
Source)
at
com.novell.nds.dirxml.driver.jdbc.JDBCPublicationS him.start(Unknown Source)
at
com.novell.nds.dirxml.driver.jdbc.JDBCPublicationP roxy.start(Unknown
Source)
at
com.novell.nds.dirxml.engine.Publisher.run(Publish er.java:388)
at java.lang.Thread.run(Thread.java:534)
</jdbc:stack-trace>
</jdbc:exception>
</status>
</input>
</nds>


Also the driver status for the publisher channel indicates the following:
“Object name not provided” after the error message.

I have thoroughly examined the driver config, schema mapping and filters
and can’t find anything. I’ve given the Oracle DBA the new
documentation for the Oracle Thin client driver and asked her to check and
make sure the idm database and dirxml user account were duplicated
exactly. She feels it has something to do with the upgraded driver. I
can’t proceed with the upgrade in production until I get this
working and truthfully, I’m not convinced that the problem is due to
the upgraded driver.

Any insights would be appreciated.

Thanks.