Resolution:
In this scenario one will see the following errors when the status
is getting updated to "P" in the publishing table :-
------------------------------------------------------
2002 Jun 11 08:43:35:625  MESANSFAToOraclePub.MESANSFAToOraclePub Error
[Database] AEADB-100004
        Database driver code: HY000
        Database vendor message: [Oracle][ODBC][Ora]ORA-01461: can bind a
LONG value only for insert into a LONG column
2002 Jun 11 08:53:15:890  MESANSFAToOraclePub.MESANSFAToOraclePub Error
[Database] AEADB-100004
        Database driver code: 22018
        Database vendor message: [Oracle][ODBC][Ora]ORA-01722: invalid
number
-----------------------------------------------------------------------
These errors could lead ADB to an inconsistent behaviour.

This problem only happens with patched Oracle ODBC drivers like 8.1.6.6/8.1.7.5
/8.1.7.6.

These are the options/workarounds, if one faces this problem :-

1)Upgrade to ADB v4.1.0 or later and use the bundled datadirect ODBC
drivers.  Datadifrect drivers do not have this problem.
2) If you cannot upgrade for some reason, use the original Oracle ODBC
drivers which come with Oracle CD. The versions are 8.1.7.0 or 8.1.6.0.

What are the problems with Oracle ODBC driver on NT when ADB is using the batch options viz.. max-rows,batch-pubstatus-updates ?