Explanation: | The LMAPI target could not initialize the PowerCenter LMAPI service because the Integration Service is not running. |
User Response: | Verify that the Integration Service is running. Also verify that the LMAPITarget application connection is configured correctly. |
Explanation: | The relational targets in the mapping do not use the same relational database connection. |
User Response: | Edit the session properties so that each relational target uses the same relational connection. |
Explanation: | There is not enough memory on the node where the Integration Service process runs to create the database connection objects the Integration Service uses to connect to the relational database. |
User Response: | Close any unnecessary applications and restart the system. If this problem persists, you may need to add RAM to the node. |
Explanation: | The Integration Service could not connect to a relational database. The relational database connection used for all relational targets in the mapping contains inaccurate information for the connection parameters. |
User Response: | Verify that the relational database connection is configured correctly. |
Explanation: | The LMAPI target could not connect to the Integration Service. |
User Response: | Verify that the Integration Service is running. Also verify that the LMAPITarget application connection is configured correctly. |
Explanation: | The LMAPI target could not log in to the Integration Service after connecting to the service. |
User Response: | Verify that the LMAPITarget application connection contains correct information for the Domain Name and Integration Service Name fields. |
Explanation: | The UKey port in the LMAPI target is not connected. |
User Response: | Connect the UKey port in the mapping. The LMAPI target starts the workflows scheduled in the Scheduling Information tab based on the data it receives from this port. |
Explanation: | The Identifier port in the LMAPI target is not connected. However, the Wait for Commit option is selected in the session properties. |
User Response: | Connect the Identifier port in the mapping when you select Wait for Commit in the session properties. |
Explanation: | The LMAPI target received data for a key which does not exist on the Scheduling Information tab of the LMAPI target properties. |
User Response: | Enter a key in the Scheduling Information tab for each value that the LMAPI target will receive in the UKey port. |
Explanation: | The mapping containing the LMAPI target does not include the indicator table. However, an indicator table name is specified on the Scheduling Information tab of the LMAPI target properties. |
User Response: | Verify that the table entered for the Indicator Table field exists in the mapping. The table must contain the fields UKey, Identifier, and Status. |
Explanation: | The Indicator Table field on the Scheduling Information tab of the LMAPI target properties does not contain a value. However, the Wait for Commit option is selected in the session properties. |
User Response: | Enter the name of the indicator table in the Indicator Table field when you select Wait for Commit in the session properties. |
Explanation: | The Integration Service cannot start the workflow because it does not exist or because it does not have a unique name in the repository. |
User Response: | Verify that all workflows scheduled in the LMAPI target exist in the repository and have unique names in the repository. |
Explanation: | The LMAPI target lost its connection to the Integration Service. |
User Response: | Verify that the Integration Service is running. |
Explanation: | The LMAPI target failed to communicate with the Integration Service. |
User Response: | Verify that the Integration Service is running. |