Oracle Business Intelligence Application Architect
☎ +91 9994883085
Don't miss

Sunday, 7 July 2013

correct the rejected files in Informatica

By on 11:24:00

During a session, the Informatica Server creates a reject file for each target instance in the mapping. If the writer or the target rejects data, the Informatica Server writes the rejected row into the reject file. By default, the Informatica Server creates reject files in the $PMBadFileDir server variable directory.
The reject file and session log contain information that helps you determine the cause of the reject. You can correct reject files and load them to relational targets using the Informatica reject loader utility. The reject loader also creates another reject file for the data that the writer or target reject during the reject loading. 
Complete the following tasks to load reject data into the target:
  • Locate the reject file.
  • Correct bad data.
  • Run the reject loader utility

NOTE: You cannot load rejected data into a flat file target

After you locate a reject file, you can read it using a text editor that supports the reject file code page.
Reject files contain rows of data rejected by the writer or the target database. Though the Informatica Server writes the entire row in the reject file, the problem generally centers on one column within the row. To help you determine which column caused the row to be rejected, the Informatica Server adds row and column indicators to give you more information about each column:
  • Row indicator. The first column in each row of the reject file is the row indicator. The numeric indicator tells whether the row was marked for insert, update, delete, or reject.
  • Column indicator. Column indicators appear after every column of data. The alphabetical character indicators tell whether the data was valid, overflow, null, or truncated.
The following sample reject file shows the row and column indicators:

Row Indicators

The first column in the reject file is the row indicator. The number listed as the row indicator tells the writer what to do with the row of data.

describes the row indicators in a reject file:

Table 15-1. Row Indicators in Reject File
Row Indicator
Rejected By
Writer or target
Writer or target
Writer or target
If a row indicator is 3, the writer rejected the row because an update strategy expression marked it for reject.
If a row indicator is 0, 1, or 2, either the writer or the target database rejected the row. To narrow down the reason why rows marked 0, 1, or 2 were rejected, review the column indicators and consult the session log.

Column Indicators

After the row indicator is a column indicator, followed by the first column of data, and another column indicator. Column indicators appear after every column of data and define the type of the data preceding it.

describes the column indicators in a reject file:

Table 15-2. Column Indicators in Reject File
Column Indicator
Type of data
Writer Treats As
Valid data.
Good data. Writer passes it to the target database. The target accepts it unless a database error occurs, such as finding a duplicate key.
Overflow. Numeric data exceeded the specified precision or scale for the column.
Bad data, if you configured the mapping target to reject overflow or truncated data.
Null. The column contains a null value.
Good data. Writer passes it to the target, which rejects it if the target database does not accept null values.
Truncated. String data exceeded a specified precision for the column, so the Informatica Server truncated it.
Bad data, if you configured the mapping target to reject overflow or truncated data.

After you correct the target data in each of the reject files, append “.in” to each reject file you want to load into the target database. For example, after you correct the reject file, t_AvgSales_1.bad, you can rename it

After you correct the reject file and rename it to, you can use the reject loader to send those files through the writer to the target database.

Use the reject loader utility from the command line to load rejected files into target tables. The syntax for reject loading differs on UNIX and Windows NT/2000 platforms.

Use the following syntax for UNIX:
pmrejldr pmserver.cfg [folder_name:]session_name

Use the following syntax for Windows NT/2000:

pmrejldr [folder_name:]session_name


  1. Hi kashif thanks for all your posts can please help me in one issue that I want a sample file view after correcting the reject file I want to know how the data looks from murali


Blog Archive


1z0-482 Dumps (2) 1Z0-525 Dumps (1) BI Apps Installation (1) BI Publisher Interview Questions (1) BICS (2) Business Intelligence (1) DATA WAREHOUSE ADMINISTRATOR CONSOLE (18) Data Warehousing (48) E-BIZ R12 (1) E-BIZ R12 INSTALLATION (1) Essbase (1) hmailserver (1) Hyperion (1) Hyperion Essbase (2) Hyperion Essbase Interview Questions (1) Hyperion financial management (1) Informatica (163) Informatica Installation 9.6.1 (2) Informatica Interview Question (47) Informatica Online Training (1) informatica scenarios questions (1) Informatica Training (1) Informatica Training Chennai (1) JAVA (1) linux (1) Normalization in Oracle (1) OBIA (1) OBIA (3) OBIA Installation (33) OBIEE (2) OBIEE 10G (8) OBIEE 11G (138) OBIEE 11g dumps (2) OBIEE 11g Interview Questions (1) OBIEE 12c (20) OBIEE 12c Architecture (1) OBIEE 12C TRAINING (1) OBIEE certification (2) OBIEE Interview Question (1) OBIEE Publisher Interview Questions (1) OBIEE TRAINING CHENNAI (1) OBIEE TRAINING ONLINE (1) ODI (Oracle data integrator) (2) odi 11g certification (1) ODI dumps (2) Oracle Administrator (20) Oracle Business Intelligence Application (3) Oracle Data Integrator (2) Oracle Data Integrator Interview questions for experience (1) Oracle Database (3) Oracle Database 12c Installation steps (3) Oracle Database Installation in Linux 6 (2) Oracle E-Business R 12.3 (1) Oracle Hyperion Planning and Budgeting Questionnaire (2) oracle Joins (1) Power BI (5) RCU INSTALLATION (1) scorecard in obiee 11g (1) SQL (3) SQL Interview Questions (1) sql server 2008 (2) Sql server installation (1) WinSCP (1)