Common issues with DataConnect
Common IBM® TRIRIGA® DataConnect issues include missing staging tables or staging table fields, invalid table columns, and changed business objects that might need to be republished.
| Error message | Where found | How to fix |
|---|---|---|
A business object: XX, does not have staging table. [XX = business object name] |
From the DataConnect task run time when the workflow is running, a WFRuntimeException in the server.log | The staging table is missing for the XX business object. Task fails in the workflow. |
An error occurs while processing the staging records: XX. [XX = staging table record fields] |
From the DataConnect task run time when the workflow is running | Something wrong occurred during the DataConnect task execution. One possible issue is on update the DC_PATH did not accurately define a smart object to update. |
| Cannot delete the BO, there are Pending DataConnect jobs. | User Interface | The Processing DataConnect job needs to complete before the business object can be deleted. Delete when the processing job is completed. |
| Cannot publish the Business Object at this time. There are DataConnect jobs either WAITING or PROCESSING. These must complete first before the publish can complete. | User Interface | A Processing or Waiting DataConnect job needs to be cleared out before the Publish of the object is successful. Both must clear out without intervention. Republish when there are no pending jobs. |
| DataConnect Agent - The triDataConnectJob Business Object cannot be found. Make sure to import before using the DataConnect Agent. | From the DataConnect Agent, a PlatformRuntimeException in the server.log | Apply the most recent triDataConnectJob object migration package before you run or use DataConnect. |
| DataConnect Agent - The triDataConnectJob Business Object is not the correct version. Make sure to import before using the DataConnect Agent. | From the DataConnect Agent, a PlatformRuntimeException in the server.log | Apply the most recent triDataConnectJob object migration package before you run or use DataConnect. |
DataConnectTaskHandler - The Staging table: XX does not contain the staging field: YY. [XX = staging table name] [YY = field name] |
From the DataConnect task runtime when the workflow is executing, a warning entry in the server.log | The staging table is missing fields that are expected. This result might occur if the staging table is out of sync with the business object. Republish the business object when the DataConnect Job is completed. |
DataConnectTaskHandler: Cannot find a parent smart object whose object path is: XX. [XX = DC_PATH from the staging table] |
From the DataConnect task runtime when the workflow is executing, a warning entry in the server.log | The run time cannot find the parent that is identified in the staging table field DC_PATH. The smart object is created; just the parent is not set for the smart object. |
DataConnectTaskHandler: performing transition action with an invalid state, XX on the SmartObject: YY. [XX = state] [YY = smart object ID] |
From the DataConnect task runtime when the workflow is executing, a WFRuntimeException in the server.log | Check the job’s business object state transitions to make sure that it defined the state transitions in the base triDataConnectJob. |
The BO for the job YY, XX is not a valid BO. From the DC_JOB table [XX = BO_NAME] [YY = JOB_NUMBER] |
From the DataConnect Agent, an info entry in server.log | The BO_NAME column in the DC_JOB table for job YY is not a valid business object. Check to make sure that the name is correct and is in the triDataConnectJob module. Fix the entry and reset the STATE to READY (or 1). |
The JOB_RUN_CTL XX is not valid for job YY. From the DC_JOB table [XX = JOB_RUN_CTL] [YY = JOB_NUMBER] |
From the DataConnect Agent, an info entry in server.log | The JOB_RUN_CTL column for job YY is invalid in the DC_JOB table. Only 0 (single threaded) or 1 (multi-threaded) are valid entries. Fix the entry and reset the STATE to READY (or 1). |
The JOB_TYPE XX is not valid for job YY. From the DC_JOB table [XX = JOB_TYPE] [YY = JOB_NUMBER] |
From the DataConnect Agent, an info entry in server.log | The JOB_TYPE column for job YY is invalid in the DC_JOB table. Only 1 (in-bound) is valid. Fix the entry and reset the STATE to READY (or 1). |
Unable to associate user ID BB for the job YY using the BO XX. From the DC_JOB table [BB = USER_ID] [XX = BO_NAME] [YY = JOB_NUMBER] |
From the DataConnect Agent, an info entry in server.log | The agent was unable to use the USER_ID column to associate the newly created DataConnect Job to the user. Make sure the USER_ID is a valid T_MYPROFILE spec_id. Fix the entry and reset the STATE to READY (or 1). |
Unable to create the BO for the job YY using the BO XX. From the DC_JOB table [XX = BO_NAME] [YY = JOB_NUMBER] |
From the DataConnect Agent, an info entry in server.log | The agent was unable to create the DataConnect Job smart object. Check to make sure that the name is correct and is in the triDataConnectJob module. Fix the entry and reset the STATE to READY (or 1). |
Unable to map fields necessary for DataConnect to work properly for the job YY using the BO XX. From the DC_JOB table [XX = BO_NAME] [YY = JOB_NUMBER] |
From the DataConnect Agent, an info entry in server.log | The agent was unable to map the necessary fields to the newly created DataConnect Job. Check to make sure that the XX business object defined all of the fields in the base triDataConnectJob BO. Fix the entry or business object, possibly republish if the business object changed, and reset the STATE to READY (or 1). |
Unable to post workflow event SYSTEM DC PROCESS JOB for the job YY using the BO XX. From the DC_JOB table [XX = BO_NAME] [YY = JOB_NUMBER] |
From the DataConnect Agent, an info entry in server.log | The agent was unable to post a workflow event for the newly created DataConnect Job. The reason might be because there is no published workflow for the SYSTEM DC PROCESS JOB and the XX business object. Check to make sure that the workflow is published for the event and the XX business object. Fix the entry or workflow and reset the STATE to READY (or 1). |
Unable to Publish, there are existing DataConnect jobs processing or waiting for the Business Object. |
From the Publish Agent, a PlatformRuntimeException in the server.log | The Processing or Waiting DataConnect job needs to be cleared out before the Publish of the object is successful. Both must clear out without intervention. Republish when there are no pending jobs. |
Unable to transition job to triDCStartProcessing for the job YY using the BO XX. From the DC_JOB table [XX = BO_NAME] [YY = JOB_NUMBER] |
From the DataConnect Agent, an info entry in server.log | Check the state transitions for business object XX to make sure that XX defined the state transitions in the base triDataConnectJob in Module triDataConnectJob. Fix the entry or business object, possibly republish if the business object changed, and reset the STATE to READY (or 1). |