Skip to main content

correct the rejected files in Informatica

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:
3,D,1,D,,D,0,D,1094945255,D,0.00,D,-0.00,D
0,D,1,D,April,D,1997,D,1,D,-1364.22,D,-1364.22,D
0,D,1,D,April,D,2000,D,1,D,2560974.96,D,2560974.96,D
3,D,1,D,April,D,2000,D,0,D,0.00,D,0.00,D
0,D,1,D,August,D,1997,D,2,D,2283.76,D,4567.53,D
0,D,3,D,December,D,1999,D,1,D,273825.03,D,273825.03,D
0,D,1,D,September,D,1997,D,1,D,0.00,D,0.00,D

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
Meaning
Rejected By
0
Insert
Writer or target
1
Update
Writer or target
2
Delete
Writer or target
3
Reject
Writer
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
D
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.
O
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.
N
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.
T
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 t_AvgSales_1.bad.in.

After you correct the reject file and rename it to reject_file.in, 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

Comments

  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

    ReplyDelete

Post a Comment

Popular posts from this blog

Contact Me

Do You have any queries ?                   If you are having any query or wishing to get any type of help related Datawarehouse, OBIEE, OBIA, OAC then please e-email on below. I will reply to your email within 24 hrs. If I didn’t reply to you within 24 Hrs., Please be patience, I must be busy in some work. kashif7222@gmail.com

Top 130 SQL Interview Questions And Answers

1. Display the dept information from department table.   Select   *   from   dept; 2. Display the details of all employees   Select * from emp; 3. Display the name and job for all employees    Select ename ,job from emp; 4. Display name and salary for all employees.   Select ename   , sal   from emp;   5. Display employee number and total salary   for each employee. Select empno, sal+comm from emp; 6. Display employee name and annual salary for all employees.   Select empno,empname,12*sal+nvl(comm,0) annualsal from emp; 7. Display the names of all employees who are working in department number 10   Select ename from emp where deptno=10; 8. Display the names of all employees working as   clerks and drawing a salary more than 3000   Select ename from emp where job=’clerk’and sal>3000; 9. Display employee number and names for employees who earn commission   Select empno,ename from emp where comm is not null and comm>0. 10

Informatica sample project

Informatica sample project - 1 CareFirst – Blue Cross Blue Shield, Maryland (April 2009 – Current) Senior ETL Developer/Lead Model Office DWH Implementation (April 2009 – Current) CareFirst Blue Cross Blue Shield is one of the leading health care insurance provided in Atlantic region of United States covering Maryland, Delaware and Washington DC. Model Office project was built to create data warehouse for multiple subject areas including Members, Claims, and Revenue etc. The project was to provide data into EDM and to third party vendor (Verisk) to develop cubes based on data provided into EDM. I was responsible for analyzing source systems data, designing and developing ETL mappings. I was also responsible for coordinating testing with analysts and users. Responsibilities: ·          Interacted with Data Modelers and Business Analysts to understand the requirements and the impact of the ETL on the business. ·          Understood the requirement and develope