The Most Common Informatica Errors

Contents
1. INTRODUCTION............................................................................................................................... 2 2. DATABASE ERRORS:.............................................................................................................................. 2 2.1 CMN _ERRORCODES:...................................................................................................................... 2 2.2 WRT_ERRORCODES:....................................................................................................................... 2 2.3 RR_ERRORCODES:.......................................................................................................................... 3 2.4 BLKR_ERRORCODES:...................................................................................................................... 4 2.5 DBG_ERRORCODES: ....................................................................................................................... 5 3. UNIX ERRORS: ........................................................................................................................................ 5 3.1 TM_ERRORCODES........................................................................................................................... 5 3.2 VAR_ERRORCODE ........................................................................................................................... 5 4. TRANSFORMATION ERRORS:............................................................................................................... 6 4.1 TE ERRORS....................................................................................................................................... 6 5. COMMIT ERROR...................................................................................................................................... 6

1. INTRODUCTION The commonly encountered errors in Informatica and the most probable solutions for the same are listed below. 1. 2. 3. 4. Database Errors Unix errors Transformation Errors Commit Error

2. DATABASE ERRORS: 2.1 CMN _ERRORCODES: These errors mostly occur when they are database errors, internal errors, errors in memory allocation, or when the mapping contains Lookup or Joiner transformations. The most common among them are listed below: 2.1.1. CMN_1022 Database driver error [ORA-00904]E.g.: ABC.xyz invalid identifier Cause: These errors mostly occur when they are database errors, In the Table ABC, xyz field not exists or the field name entered incorrectly Resolution: Enter the field name correctly or check the table columns for correct field names. 2.1.2. CMN_1022 Database driver error...CMN_1022 [ORA-12535: TNS: operation timed out Database driver error...Function Name: Connect. Database Error: Failed to connect to database using user [ABC] and connection string [XYZ] Cause: Incorrect connection strings might be mentioned in the sessions of the workflows. Or connection string may not have been specified. Resolution: Enter the correct connection string in the sessions and workflows. 2.1.3. CMN_1701 Error: Data for Lookup <transformation name> fetched from the database is not sorted on the condition ports. Please check your Lookup SQL override. Cause: You specified a SQL override for this Lookup transformation and specified the ORDER BY clause incorrectly. Resolution: When you override the lookup query ORDER BY clause, you must put the condition ports first. 2.2 WRT_ERRORCODES: These are the common database errors occur when power center server writes data to the target. The most common among them are listed below: 2.2.1. WRT_8229 Database errors occurred (ABNBASEL_DEV.PK_TGT_DETAILS) violated ORA-00001: unique constraint

Cause: The unique constraint violated on the primary key of the target table by entering the same row twice.

Resolution: Correct the mapping such that only distinct records should populate the target table. 2.2.2. WRT_8116 ERROR: Target table <target table name> has no keys specified. Row # <row ID> in bad file. Cause: You attempted to perform an UPDATE or a DELETE. These commands require a primary key be defined on the target table. Resolution: Go to the target definition and define a primary key. 2.2.3. WRT_8117 ERROR: Target table <table name> does not allow INSERT. Row # <row ID> in bad file. Cause: You attempted to INSERT rows into the target table. However, you might not have been granted rights to INSERT into the specified table. Resolution: Contact your database administrator. 2.2.4. WRT_8118 ERROR: Target table <table name> does not allow UPDATE. Row # <row ID> in bad file. Cause: You attempted to UPDATE rows into the target table. However, you might not have been granted rights to UPDATE into the specified table. Resolution: Contact your database administrator. 2.2.5. WRT_8119 ERROR: Target table <table name> does not allow DELETE. Row # <row ID> in bad file. Cause: You attempted to DELETE rows from the target table. However, you might not have the rights to DELETE from the specified table. Resolution: Contact your database administrator. 2.2.6. WRT_8004 Writer initialization failed [Error opening session output file [/file path] [err no=#] [error=Permission denied]]. Writer terminating. Cause: This error will come if the file you need, has no permission to access with the User ID currently you are using. Resolution: Check the prosperities of the file and do change mode from the owner User ID of that file. 2.3 RR_ERRORCODES: These errors might appear when the power centre reads the relational database sources. 2.3.1. RR_4036 Error connecting to database [<Error Message> Database driver error...Function Name: Connect Database Error: For E.g. Failed to connect to database using user [ABNBASEL_DEV] and connection string [ABNBASEL]

E.g. of an Error Message: [ORA-12541: TNS: no listener Database driver error...Function Name: Connect Database Error: Failed to connect to database using user [ABNBASEL_DEV] and connection string [ABNBASEL]. (Or) RR_4036 Error connecting to database [ Database driver error... Function Name: Logon ORA-01034: ORACLE not available Cause: It happens when the Informatica Server fails to connect to the database. It might happen as a result of incorrect logging, or when Informatica is not able to locate TNS details such as the connect string, user name and password for that database. Resolution: Check for correct TNS usernames passwords and connect string in the tnsnames.ora file in Oracle and restart the workflow from the failed task in the monitor. 2.3.2. RR_4035 SQL Error [ORA-01007: variable not in select list Cause: This error occurs when the select statement in the SQL override query did not contain all the field names which are connected from the source. Resolution: Make sure that the entire field names which you are connected are should be in the select statement of the SQL override query. The best method to avoid this is first doing Generate SQL and then change that query accordingly to your conditions. 2.3.3. RR_4035 SQL Error [ ORA-00932: inconsistent data types (Or) ORA_0I858: non numeric value found where expecting numeric value Cause: There may be two reasons for this error the data types in the source and the source qualifier are may be different or the selection order of the variables is not in sync with the order which they have connected means the order is different from the order which we get by doing generate SQL. Resolution: Correct the mapping such that all the data types are in sync and do generate SQL and then change that query according to your requirement. 2.3.4. RR_4043 ERROR: One or more fields used to partition source(s) of Source Qualifier <Source Qualifier name> have been deleted. Please edit and save the session to correct the partitioning information. Cause: You defined a partition key for a port in the source qualifier that you deleted. Resolution: Edit the session to remove the partition key from the Source Qualifier. Then save the new partition information in the session and run it again. 2.4 BLKR_ERRORCODES: 2.4.1. BLKR_16001 Error connecting to database... Cause: The Power Center Server failed to connect to the database. You may have logged in incorrectly.

Resolution: Log in with the correct information. Usernames and passwords may be casesensitive. 2.5 DBG_ERRORCODES: These messages might appear when the Power Center Server encounters a problem during loading and debugging: 2.5.1. DBG_21173 ERROR: Lookup port not specified in lookup override Cause: This error occurs when any of the port is specified as look up used in the look up over ride query. port and that port is not

Resolution: Check the look up over ride query that the entire look up ports is selected in the look-up over ride query. 2.5.2. DBG_21263 ERROR: Invalid look up over ride

Cause: This error occurs when any of the port is specified as look up port and that port is not used in the look up over ride query or the name mentioned in the lookup up over ride query contains the table alias name For e.g. the over ride contains select emp.EMP_NAME but the look up port name is only EMP_NAME Resolution: Please use aliasing names to the look up ports .In the above example should have port in the SQL override as like EMP.EMP_NAME AS EMP_NAME 3. UNIX ERRORS: 3.1 TM_ERRORCODES These errors are generated by Data transformation manager 3.1.1. TM_6056 Error executing shell command... Cause: This happens when the Informatica Server encounters an error while executing a userspecified shell script. Any non-zero return value is an error. The path of the shell script where the error has possibly occurred is given in the error message. Resolution: Review the shell script for the based on the error. Restart workflow once problem is detected and restart workflow. 3.1.2. TM_6099 Error in executing post-session shell commands: session <session name>. Cause: An error occurred while executing post-session shell commands for the specified session. Resolution: Make sure all post-session shell commands are specified correctly, and those commands can be found in the Power Center Server account path 3.2 VAR_ERRORCODE

3.2.1. VAR_27015 Cannot find specified parameter file <file name> for session <session name>. Cause: The Power Center Server could not find the user-specified parameter file, so it failed the session. Resolution: Create the parameter file, set the path correctly, or remove the parameter file name specified in the session properties. 3.2.2. VAR_27026 Error: Missing initial string value for <variable>: <name>. Cause: The Power Center Server cannot find the initial string value for the specified variable in the session parameter. Resolution: Add the initial value in the parameter file. 4. TRANSFORMATION ERRORS: 4.1 TE ERRORS These error messages are related to transformations used in the session: 4.1.1. TE_7007 Transformation Evaluation Error [<<Expression Error>> Error Description Expression].. Current row skipped... For Example: TE_7007 Transformation Evaluation Error [<<Expression Error>> [TO_DATE]: invalid string for converting to Date ... t: TO_DATE(s:'vfd',s:'MM/DD/YYYY')]; current row skipped... Cause: This error occurs when the function in the expression can not evaluate the stated expression. In the above example To_Date function cannot convert the vfd string in to the specified date format. Resolution: Check the Expression input variable that correct data is coming from the source or not. 4.1.2. TE_7072 Aggregate Error: Expecting keys to be descending. Cause: You selected the Sorted Input option in an Aggregator transformation, but the data entering the Aggregator transformation is not sorted. Resolution: Sort the data before the Aggregator transformation, or clear the Sorted Input option. You can sort the data using the Sorted Ports option in the Source Qualifier transformation, or you can use a Sorter transformation. 5. COMMIT ERROR This is the very common error occur in Informatica while loading a table .It is very difficult to find out the reason because the error description is not present in session log. If Error "WRT_8076 Writer run terminated. [Commit Error]. Appears during the load.

The various possible causes and the possible solution have been listed below: Cause: The common cause to this error will be the target load type in the session properties is set to bulk mode. Action: The target load type in the session properties is set to Normal. Cause: The table is not present in the database or the table structure is different in the database. Action: 1.Check the table is present in the database or not. (Or) 2. Check the table structure imported to Informatica is same as the table structure in the database. Cause: The unavailability of the table space or unavailability of UNIX space of the particular table. Action: The table space should be increased. Cause: For the partitioned tables there is no partition defined for incoming data. Action: Check for the partition or create partition in the database. Cause: In the session properties the connection string to database is not correctly given. Action: Check the session properties and change the connection string. Cause: The data coming has larger precision value than the specified precision for the target fields Action: Increase the precision value of the target fields.