Explanation: | The system does not have enough memory to allocate to the logging object. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The system does not have enough memory to allocate to the ILog logging object. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the logging object. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the System operator. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the host name. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the user name. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the password. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the Working database. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the table name. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to error database name. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to Error Table 1 name. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to Error Table 2 name. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the log database name. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the log table name. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the INSERT statement. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the UPDATE statement. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the delete DML statement. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the TRUNCATE TABLE statement. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the Teradata Parallel Transporter connection object. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | Schema defined in the mapping is incorrect. |
User Response: | Validate or re-create the mapping. Verify that the column names, precision, and scale match the table definition. |
Explanation: | The system does not have enough memory to allocate to the DML group. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | Initiate method of Teradata Parallel Transporter connection object failed. |
User Response: | Check the error message returned by Teradata CLI or DBS. Contact Informatica Global Customer Support. |
Explanation: | The system does not have enough memory to allocate to the connection object. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the schema object. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the DML group. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The PowerCenter Integration Service cannot commit the connection object. |
User Response: | Check the DBS/CLI error message for more information. |
Explanation: | The PowerCenter Integration Service failed in end acquisition. |
User Response: | Check the DBS/CLI error message for more information. |
Explanation: | The PowerCenter Integration Service cannot apply rows. |
User Response: | Check the DBS/CLI error message for more information. |
Explanation: | DML group built is invalid. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Sending row data request for insert, update, or delete to the Teradata database failed. |
User Response: | Drop the error and log tables if they exist in database, and restart the session. |
Explanation: | Sending a buffer data for the insert operation to Teradata database failed. |
User Response: | Drop the error and log tables if they exist in database, and restart the session. |
Explanation: | Unable to get information about buffer size, row header, row length, and row trailer in LOAD system operator. |
User Response: | Drop the error and log tables if they exist in database, and restart the session. |
Explanation: | Unable to get the number of affected rows and number of rejected rows from Teradata database. |
User Response: | Drop the error and log tables if they exist in database, and restart the session. |
Explanation: | When there is no sufficient memory to allocate to the Teradata database connection object. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | Memory is not sufficient to allocate. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | Memory is not sufficient to allocate. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | Unable to create a connection with Teradata database in Update drive for truncate table. |
User Response: | Drop the error and log tables if they exist in database, and restart the session. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Writer plug-in initialization failed. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the target drivers. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Writer target driver initialization failed. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the group drivers. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Writer Group driver initialization failed. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the partition drivers. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Writer partition driver initialization failed. |
User Response: | Validate the mapping, and then run the session again. |
Explanation: | Failure in Teradata PT API call. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Connection object has some invalid parameters. |
User Response: | Check whether all attributes in the connection object are correct. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The system does not have enough memory to allocate to the DML statement. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the Truncate Table DML statement. The PowerCenter Integration Service cannot read target table information from vector. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the Insert statement. The PowerCenter Integration Service cannot read target table information from vector. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the Update DML statement. The PowerCenter Integration Service cannot read target table information from vector. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | The system does not have enough memory to allocate to the Delete DML statement. The PowerCenter Integration Service cannot read target table information from vector. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | Row type is deleted and no primary key is defines in the target table. |
User Response: | Define a primary key in the target table and restart the session. |
Explanation: | The entire field in target table is primary key and no other column exists for update. |
User Response: | Make sure you have at least one column for update. |
Explanation: | Row type is update and no primary key is defined in the target table. |
User Response: | Define a primary key in the target table and restart the session. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Teradata internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | See the additional error message for more information. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The system does not have enough memory to allocate to an object. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | As system operator is LOAD and row type is Update. |
User Response: | Update operation is not allowed in LOAD system operator. |
Explanation: | As system operator is LOAD and row type is Update. |
User Response: | Delete operation is not allowed in LOAD system operator. |
Explanation: | The PowerCenter Integration Service cannot delete all rows of the target table. |
User Response: | Review the session log and Teradata PT log tables for related messages. Drop the error and log tables, and restart the session. |
Explanation: | The Max Sessions attribute for a Teradata PT connection object is set to an illegal value. |
User Response: | Update the Max Sessions attribute and then restart the session. |
Explanation: | The Sleep attribute for a Teradata PT connection object is set to an illegal value. |
User Response: | Update the Sleep attribute and then restart the session. |
Explanation: | The Tenacity attribute for a Teradata PT connection object is set to an illegal value. |
User Response: | Update the Tenacity attribute and then restart the session. |
Explanation: | The Block Size attribute for a Teradata PT connection object is set to an illegal value. |
User Response: | Update the Block Size attribute and then restart the session. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | An error occurred when the PowerCenter Integration Service tried to initiate the connection with Teradata PT. For example, the Teradata user name or password might be incorrect. |
User Response: | Review the session log and Teradata PT log tables for related messages. |
Explanation: | An error occurred when the PowerCenter Integration Service tried to initialize the connection with the Teradata PT writer. For example, a network problem might have occurred during initialization. |
User Response: | Review the session log and Teradata PT log tables for related messages. |
Explanation: | An error occurred when the PowerCenter Integration Service tried to deinitialize the connection with the Teradata PT writer. For example, a network problem might have occurred during deinitialization. |
User Response: | Review the session log and Teradata PT log tables for related messages. |
Explanation: | An error occurred when Teradata PT tried to issue a commit against the Teradata database. For example, a connection might have been dropped due to a network problem or fatal database error. |
User Response: | Review the session log and Teradata PT log tables for related connection errors. |
Explanation: | The Teradata framework requested a rollback for a failed transaction, but Teradata PT does not support rollback for failed transactions. |
User Response: | Review the session log and Teradata PT log tables to find the failed transaction. Check the target tables for data discrepancies. |
Explanation: | An error occurred when the PowerCenter Integration Service tried to initialize the connection with Teradata PT for reading recovery information. |
User Response: | Review the session log and Teradata PT log tables for related connection errors. |
Explanation: | An error occurred when the PowerCenter Integration Service tried to terminate the connection with Teradata PT for reading recovery information. |
User Response: | Review the session log and Teradata PT log tables for related connection errors. |
Explanation: | An error occurred when the PowerCenter Integration Service tried to initialize the connection with Teradata PT for deleting recovery information. |
User Response: | Review the session log and Teradata PT log tables for related connection errors. |
Explanation: | An error occurred when the PowerCenter Integration Service tried to terminate the connection with Teradata PT for deleting recovery information. |
User Response: | Review the session log and Teradata PT log tables for related connection errors. |
Explanation: | A connection error occurred when the PowerCenter Integration Service tried to delete recovery information. |
User Response: | Review the session log and Teradata PT log tables for related connection errors. |
Explanation: | A connection error occurred when the PowerCenter Integration Service tried to delete recovery information. |
User Response: | Review the session log and Teradata PT log tables for related connection errors. |
Explanation: | A connection error occurred when the PowerCenter Integration Service tried to delete recovery information. |
User Response: | Review the session log and Teradata PT log tables for related connection errors. |
Explanation: | The target ODBC connection could not create the recovery table in the Teradata target database due to a connection error. |
User Response: | Review the session log for related connection errors. |
Explanation: | The target ODBC connection could not truncate the target table due to an error. |
User Response: | Review the session log for related messages. |
Explanation: | The target ODBC connection could not drop the error table due to an error. |
User Response: | Review the session log for related messages. |
Explanation: | The target ODBC connection could not drop the log table due to an error. |
User Response: | Review the session log for related messages. |
Explanation: | The PowerCenter Integration Service could not get the values of some session-level properties. A system error might have occurred or the repository might have inconsistencies. |
User Response: | Fix the operating system error. Contact Informatica Global Customer Support. |
Explanation: | The license key in the Administrator tool is invalid or does not contain Teradata PT connectivity option. |
User Response: | Contact Informatica Global Customer Support to get a valid license key. |
Explanation: | The session uses a connection object of type “Teradata Parallel Transporter Connection,” which is deprecated. |
User Response: | Replace the deprecated connection object with a connection object of type “Teradata PT Connection.” |