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: | While initializing logging module, tracing level from session attributes cannot be retrieved. |
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 host name 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 user name 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 password 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 database name 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 table name 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 object. |
User Response: | Make sure that there is enough memory on the machine where the PowerCenter Integration Service is running. |
Explanation: | Connection attributes are invalid. |
User Response: | Make sure all the connection attributes are correct. |
Explanation: | The schema defined in the mapping is incorrect. |
User Response: | Validate or re‑create the mapping. Verify that the column names, precision, and scale are the same as the table definition. |
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 Teradata Parallel Transporter connection object. |
User Response: | Make sure that there is enough memory on the PowerCenter Integration Service machine. |
Explanation: | The system does not have enough memory to allocate to the Teradata Parallel Transporter Schema object. |
User Response: | Make sure that there is enough memory on the PowerCenter Integration Service machine. |
Explanation: | No ports mapped in the mapping. |
User Response: | Validate or re‑create the mapping. |
Explanation: | GetRow() call failed on the row <row number>. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The PowerCenter Integration Service cannot get the C-datatype for the Source Qualifier. |
User Response: | Check the datatype from the Source Qualifier list of datatypes. |
Explanation: | The PowerCenter Integration Service could not write rows to Source Qualifier buffers. |
User Response: | Run the session again. If the session fails again, contact Informatica Global Customer Support |
Explanation: | EXPORT system operator failed to get data from the Teradata tables. |
User Response: | Run the session again. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Invalid host name. |
User Response: | Make sure that you specify the correct TDPID in the connection object. |
Explanation: | Reader plug-in initialization failed. |
User Response: | Validate the mapping and run the session again. |
Explanation: | The session failed to initialize because the Source Qualifier instance could not be fetched from the mapping. |
User Response: | Re‑create the mapping or run the session again. |
Explanation: | Reader partition driver initialization failed. |
User Response: | Run the session again. If the session fails again, contact Informatica Global Customer Support. |
Explanation: | Connection object has some invalid parameters. |
User Response: | Verify that all attributes in the connection object are appropriate. |
Explanation: | The PowerCenter Integration Service cannot retrieve the session attributes. |
User Response: | Verify that all attributes in the sources session object are valid. |
Explanation: | The PowerCenter Integration Service cannot retrieve the Source Qualifier attributes. |
User Response: | Verify that all attributes in the Source Qualifier are valid. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The PowerCenter Integration Service could not create the DML statement for data extraction. |
User Response: | Verify that the custom SQL is correct. Verify that field names and table names are same as in the Teradata table definition. |
Explanation: | The system does not have enough memory to allocate to the Teradata PT API 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: | The custom SQL in the session properties is incorrect. |
User Response: | Verify that the custom SQL is correct. |
Explanation: | The custom SQL in the Source Qualifier is incorrect. |
User Response: | Verify that the custom SQL is correct. |
Explanation: | The PowerCenter Integration Service could not build the DML statement for data extraction. The port business names may not match the table definition. |
User Response: | Verify that the ports are defined correctly in the mapping. |
Explanation: | The Source Qualifier contains multiple groups. |
User Response: | Update the mapping so that the Source Qualifier contains a single group. |
Explanation: | The PowerCenter Integration Service cannot get the Source Qualifier or sources field list and field information. |
User Response: | Verify that the mapping fields are defined correctly. |
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: | The SQL query in the custom SQL field is invalid. Enter a SQL query using Teradata SQL. |
User Response: | Make sure that the SQL defined in custom SQL field is valid Teradata SQL. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
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: | The Number of Sorted Ports attribute in the Teradata PT source properties exceeds the number of output fields. |
User Response: | Update the Number of Sorted Ports for the Teradata source and then restart the session. |
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. |