Why the status update SQL statement is different between ADB Adapter 6.x and 7.x
Article ID: KB0081066
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Database | - |
Description
DBSQL exception "ADB_TRACKINGID": invalid identifier when update entry status.’ is generated at runtime after upgraded from ADB Adapter 6.x to 7.x.
The root cause of the specific error after the upgrade is that ADB 7.x will build the SQL statement based on the logic for whether or not the ADB_TRACKINGID AESchema exists in the repository .dat file(project file), and the error occurred while in the adapter configuration the AESchema of the Publishing table contains the ADB_TRACKINGID but the Publishing table defined in DB server does not include it.
To get the problem solved, please remove the AESchema ADB_TRACKINGID from the project file or alter the Publishing table by adding the ADB_TRACKINGID column.
The root cause of the specific error after the upgrade is that ADB 7.x will build the SQL statement based on the logic for whether or not the ADB_TRACKINGID AESchema exists in the repository .dat file(project file), and the error occurred while in the adapter configuration the AESchema of the Publishing table contains the ADB_TRACKINGID but the Publishing table defined in DB server does not include it.
To get the problem solved, please remove the AESchema ADB_TRACKINGID from the project file or alter the Publishing table by adding the ADB_TRACKINGID column.
Issue/Introduction
Why the status update SQL statement is different between ADB Adapter 6.x and 7.x
Environment
Product: TIBCO ActiveMatrix Adapter for Database
Version: 7.x
All Supported OS
Feedback
Yes
No
Powered by
