Notification Job Fails On Every Run In Oracle Lite 10.3.0.2.0 (Doc ID 1223487.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle Lite - Version: 10.3.0.2.0 to 10.3.0.2.0 - Release: 10.3 to 10.3
Information in this document applies to any platform.
Affected Database: Oracle

Symptoms

Everytime the notification job run it failes with the following error.


java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:304)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:625)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:181)
at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:629)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1153)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2932)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3004)
at oracle.lite.sync.NotificationAgent.mergeNotification(Unknown Source)
at oracle.lite.sync.NotificationAgent.execute(Unknown Source)
at oracle.lite.job.JobThread.run(Unknown Source)


This was a problem previously fixed in 10.3.0.1.0 

After upgrading  to 10.3.0.2.0 and problem is no longerChecked for relevance on DD-Mon-YYYY fixed.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms