Explanation: | The Integration Service failed to connect to the repository. |
User Response: | Verify that the Repository Service is running. |
User Response: | Review the session log for related messages. |
User Response: | Review the Repository Service logs for more information about the error. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Integration Service cannot update repository tables. |
User Response: | Review the session log for related messages. |
Explanation: | This is an operating system error. |
User Response: | Review the session log for related messages. If necessary, see the operating system documentation for appropriate action. |
User Response: | Review the session log for related messages. |
Explanation: | The Integration Service could not allocate memory for a buffer pool at a partition point, source boundary, or target boundary. The Integration Service node might not have enough memory. |
User Response: | Verify that the Integration Service node has enough memory. If deadlock recovery and connection resilience are enabled, disable them and run the session again. See the additional error message for more information. |
Explanation: | The buffer memory size is too low for the session. |
User Response: | Increase the buffer memory size. See the additional error message for more information. |
Explanation: | The thread cannot lock or unlock the buffer pool. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The DTM buffer size exceeded the recommended size. |
User Response: | The Integration Service started with the shared memory size you specified. If you want to change the memory size, stop the Integration Service, change the number of bytes to the specified size, and then restart the Integration Service. |
Explanation: | You selected a sort order that is invalid with the code page. |
User Response: | Select a valid sort order for the selected code page. |
Explanation: | The Integration Service cannot parse the stored procedure text. There might be a syntax error in the stored procedure. |
User Response: | Check the syntax of the stored procedure. Test the stored procedure in the database. Then run the session again. |
Explanation: | The context for executing the stored procedure might be invalid. |
User Response: | Review the session log for related messages. Verify the stored procedure in the database. Check the database error messages for further explanations. |
Explanation: | The stored procedure call text for a pre-target or post-target stored procedure contains one or more characters that are not in the character set of the stored procedure database code page. |
User Response: | Identify the invalid character referenced in the session log. Edit the call text so that the stored procedure call text contains characters encoded in the character sets of both the Integration Service code page and the stored procedure database code page. Configure the stored procedure database to use a code page that contains encoding for the store procedure data character set and is compatible with the Integration Service code page. |
Explanation: | The stored procedure database uses a code page that is not supported by PowerCenter. |
User Response: | Select a code page for the stored procedure database that is supported by PowerCenter and contains encoding for the stored procedure database character set. |
Explanation: | The specified sort order is incompatible with the Integration Service code page. |
User Response: | To validate code pages, select a sort order compatible with the Integration Service code page. To relax code page validation, configure the Integration Service to relax code page validation in Unicode data movement mode. |
Explanation: | The Lookup or Stored Procedure transformation is configured with the $Source or $Target variable. The mapping has more than one relational source or relational target database connection. |
User Response: | In the session properties, enter a database connection for the $Source or $Target connection. |
Explanation: | A session parameter, such as $DBConnectionName, was used to define a session connection. In the parameter file, the session parameter value does not match the name of one of the connection objects in the Workflow Manager. |
User Response: | Update the session parameter value in the parameter file so that it matches the name of a connection object in the Workflow Manager. Make sure that the session parameter type matches the connection object type. For example, use $FTPConnectionName to define an FTP connection, not a queue connection. |
User Response: | Enter a session log path that is within the session log path limit. You may need to specify a different directory or shorten the length of the name of the log file. |
Explanation: | The repository was unable to update the log file number in the database. |
User Response: | Verify that the database server and Repository Service are running. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The user who started the session does not have execute permission on one of the connection objects used by the session. |
User Response: | Verify that the user has permission on the object. |
Explanation: | The user who started the session does not have execute permission on one of the connection objects used by the session. |
User Response: | Verify that the user has permission on the object. |
Explanation: | There was an error sending statistical information to the repository. For example, the database connection may be broken. |
User Response: | Review the Repository Service log for related messages. |
Explanation: | There was an error sending statistical information to the repository. For example, the database connection may be broken. |
User Response: | Review the Repository Service log for related messages. |
Explanation: | The Integration Service cannot find the queue connection specified in the session properties. |
User Response: | Assign a valid queue connection to the session. |
Explanation: | The Integration Service could not run the session because it is invalid. |
User Response: | Review the run-time error message. |
Explanation: | There is not enough available virtual memory. |
User Response: | Increase the amount of available virtual memory on the Integration Service system. |
Explanation: | The Integration Service requires more memory. |
User Response: | Increase the amount of available virtual memory on the Integration Service system. |
Explanation: | If a mapplet associated with a mapping is changed in such a way that the target load order for the mapplet changes after you saved the mapping, the Integration Service cannot run the session. |
User Response: | Open the mapping and save it. |
Explanation: | The user name specified in the target database connection does not have table creation privileges on the target database. |
User Response: | Grant table creation privileges to the database user name specified in the target database connection. |
Explanation: | The Integration Service could not create the recovery table due to a database error. |
User Response: | Check the database error message to determine the cause of the error, and contact the database administrator. |
Explanation: | The user name specified in the target database connection does not have table creation privileges on the target database. |
User Response: | Grant table creation privileges to the database user name specified in the target database connection. |
Explanation: | The Integration Service could not create the recovery table due to a database error. |
User Response: | Check the database error message to determine the cause of the error, and contact the database administrator. |
Explanation: | The Integration Service could not retrieve information from the recovery table due to a database error. |
User Response: | Check the database error message to determine the cause of the error, and contact the database administrator. |
Explanation: | The user name specified in the target database connection does not have permission to select information from the target database. |
User Response: | Grant select privileges to the user name specified in the target database connection. |
Explanation: | The Integration Service could not retrieve information from the recovery table due to a database error. |
User Response: | Check the database error message to determine the cause of the error, and contact the database administrator. |
Explanation: | The user name specified in the target database connection does not have permission to insert information into the PM_RECOVERY recovery table. |
User Response: | Grant the database user name specified in the target database connection permission to insert data into the PM_RECOVERY recovery table. |
Explanation: | The Integration Service could not insert information into PM_RECOVERY due to a database error. |
User Response: | Check the database error message for the cause of the error, and contact the database administrator. |
Explanation: | The Integration Service cannot perform recovery because the recovery tables are not correctly formatted. |
User Response: | If you created the recovery tables manually, review the format and correct any error. You may want to allow the Integration Service to create the tables. Grant table creation privileges to the user name specified in the target database connection. |
Explanation: | The Integration Service could not initialize the PM_TGT_RUN_ID recovery table. |
User Response: | Query the PM_RECOVERY recovery table for the maximum value in the TGT_RUN_ID column. Insert this value into PM_TGT_RUN_ID. |
User Response: | Check the database error message for the cause of the error and contact the database administrator. |
Explanation: | The user specified in the target database connection does not have permission to access the recovery tables. |
User Response: | Grant permission to access the recovery tables to the user name specified in the target database connection. |
Explanation: | The Integration Service could not access the recovery tables due to a database error. |
User Response: | Check the database error message for the cause of the error and contact the database administrator. |
Explanation: | The user name specified in the target database connection does not have permission to update the recovery table. |
User Response: | Grant permission to access the recovery tables to the user name specified in the target database connection. |
Explanation: | The Integration Service could not update the recovery table due to a database error. |
User Response: | Check the database error message for the cause of the error and contact the database administrator. |
Explanation: | The user name specified in the target database connection does not have permission to delete information from the recovery table. |
User Response: | Grant permission to delete information from the recovery tables to the user name specified in the target database connection. |
Explanation: | The Integration Service could not delete information from the recovery table due to a database error. |
User Response: | Check the database error message for the cause of the error and contact the database administrator. |
Explanation: | The user specified in the target database connection does not have permission to reset information in the recovery table. |
User Response: | Grant permission to access, insert, and delete information in the recovery tables to the database user name specified in the target database connection. |
Explanation: | The Integration Service could not reset information in the recovery table due to a database error. |
User Response: | Check the database error message for the cause of the error and contact the database administrator. |
Explanation: | The user specified in the target database connection does not have permission to access the recovery table. |
User Response: | Grant permission to access the recovery tables to the user name specified in the target database connection. |
Explanation: | The Integration Service could not access the recovery table due to a database error. |
User Response: | Check the database error message for the cause of the error and contact the database administrator. |
Explanation: | The user specified in the target database connection does not have permission to access the recovery table. |
User Response: | Grant permission to access the recovery tables to the user name specified in the target database connection. |
Explanation: | The Integration Service could not access the recovery table due to a database error. |
User Response: | Check the database error message for the cause of the error and contact the database administrator. |
User Response: | Verify that the recovery tables exist on the target database. Review the session log for related messages. |
User Response: | Verify that the recovery tables exist on the target database. Review the session log for related messages. Verify that the database user name specified in the target database connection has permission to create, access, and update the recovery tables. |
User Response: | Verify that the recovery tables exist on the target database. Check previous error messages for possible causes of the error. Verify that the database user name specified in the target database connection has permission to create, access, and update the recovery tables. |
User Response: | Verify that the recovery tables exist on the target database. If the tables do not exist, you must run the session again normally with recovery enabled to create the tables and insert recovery information into them. You can also manually create the recovery tables and then run the session normally to create recovery information. If the recovery tables exist, run the session normally to create recovery information. Do not drop the recovery tables while the session is enabled for recovery. |
User Response: | Check the database error message log for possible causes of the error, and contact the database administrator. |
User Response: | Review the session log for related messages. Verify that the recovery tables exist on the target database and that the user name specified in the target database connection has permission to update the tables. |
User Response: | Enable the session for recovery. While enabled for recovery, the session must run normally and fail before you can perform recovery. |
Explanation: | The Integration Service failed the session because it cannot load to the target type using database partitioning. |
User Response: | Use pass-through partitioning for targets that do not support database partitioning. |
User Response: | To perform recovery, disable test load in the session properties. |
User Response: | Restart the session. If the problem persists, contact Informatica Global Customer Support. |
Explanation: | You tried to run a session on a 32-bit Integration Service, but the DTM buffer size is too large. |
User Response: | Decrease the DTM buffer size or run the session on a 64-bit Integration Service. |
Explanation: | The Integration Service failed to load the external session log library, possibly because of missing or invalid .dll files. |
User Response: | Take necessary action to correct the error. |
Explanation: | The Integration Service could not access the specified file. The user running the Integration Service does not have permission to read or write to the specified file for error logging. |
User Response: | Review the error message, and check the permissions on the specified file. |
User Response: | Update the session to use a different data column delimiter for error logging. |
Explanation: | The session ran in change or real-time mode, but the number of partitions for the specified transformation instances differ. Transformation instances must have the same number of partitions. |
User Response: | Configure the transformation instances to have the same number of partitions. |
Explanation: | When a session runs in change or real-time mode, the execution of the target load order groups must be consecutive. |
User Response: | To ensure consecutive execution of target load order groups, set the target load order in the Designer. |
User Response: | Disable session on grid, or debug the mapping in the Designer. |
Explanation: | The worker DTM could not connect to the master DTM in the specified timeout period. The master DTM process may have shut down unexpectedly, or there may be a network failure. |
User Response: | Contact the network administrator to verify that the network does not have connectivity issues. Contact the PowerCenter domain administrator to verify that the Integration Service is running. |
Explanation: | The master DTM process was unable to connect to the master service process to update the session status. The master DTM process may have shut down unexpectedly, or there may be a network failure. |
User Response: | Contact the network administrator to verify that the network does not have connectivity issues. Contact the PowerCenter domain administrator to verify that the Integration Service is running. |
User Response: | Create a persistent profile session, or run the temporary profile session on an Integration Service that is not assigned to a grid. |
Explanation: | The Integration Service attempted to create a log file in the PowerCenter Services installation directory but was unable to access the directory. The Integration Service could not attach the session log to the post-session email because it could not create the file in the specified directory. |
User Response: | Verify that the PowerCenter Services user has write permission for the PowerCenter Services installation directory. |
User Response: | Validate the session or configure the Integration Service to run impacted sessions. |
Explanation: | The Integration Service cannot expand a parameter or variable in the table owner name or table name prefix. |
User Response: | Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer mapping variable to a text string in the parameter file. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
User Response: | Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer mapping variable to a text string in the parameter file. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
User Response: | Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer mapping variable to a text string in the parameter file. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | There was an error saving statistics to the repository. For example, the database connection may be broken. |
User Response: | Review the Repository Service log for related messages. |
Explanation: | The Integration Service could not reset a recovery table because it encountered an error. For example, the database connection may be broken. |
User Response: | Review the session log for more information. |
Explanation: | The variable is assigned in both a pre-session variable assignment statement and in a parameter file. The Integration Service uses the value in the parameter file. |
User Response: | To use the value in the pre-session variable assignment statement, remove the variable from the parameter file. Or, configure the session and workflow so that they do not run with a parameter file. |
User Response: | Verify that the variable has not been deleted or renamed. |
User Response: | Verify that the variable has not been deleted or renamed. |
User Response: | Verify that the variable has not been deleted or renamed. |
Explanation: | The session contains a pre- or post-session variable assignment statement, but the Integration Service could not perform the variable assignment. |
User Response: | Verify that the parameters or variables in the assignment statement exist and that the names are spelled correctly. |
User Response: | Verify that the parameters or variables in the assignment statement exist and that the names are spelled correctly. |
User Response: | Start the workflow instance after one of the instances completes running. |
User Response: | To persist mapping variables for concurrent workflows, configure different workflow instance names and parameters. |
User Response: | Verify that the workflow is enabled to run concurrently. Configure unique instance names for each workflow, or enable the workflow to run concurrently without unique instance names. |