top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Informatica skipped records need to be written to bad files

0 votes
435 views

In my case, i have an expression transformation which uses the default function ERROR('transformation') to skip the records in which date value coming inside is not in the correct format. In this, the skipped rows are not written to the reject files, so that we are getting the reconcilation problem. I need the skipped rows to be written to the bad files.Please help me how can i achieve this.

posted Aug 25, 2014 by Sunil

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

Put the Update Strategy transformation in your mapping and flag these rows for reject (use the DD_REJECT constant).

answer Aug 26, 2014 by Shweta Singh
Similar Questions
+1 vote
Need to convert data into Dat files via Informatica

I am new to Informatica

I have one staging table where data comes everyday and I need to extract data from this staging table and convert it into Dat file format and place in into a folder. so that these dat files could be a feed for another process.

I dont know how informatica does this (Conversion of data from Staging table to Dat). So please help me to know how Informatica fetch the data from staging table, transform it into Dat file and place it into a folder.

+3 votes
How to disable logging rejected files in the .bad file?

I have a few instances of the same PowerCenter session running in parallel. They attempt to insert a large number of rows into the same target table. The table has a unique constraint on the natural key columns that causes a lot of rows to be rejected due to unique constraint violation. These rows are saved in a reject file and it hurts the performance of the entire process.

I don't need a list of rejected rows - it was my conscious decision to prevent the duplicate rows on the database level, not in the mapping. This is a known side effect of this design decision.

Is there a setting to prevent the rejected rows from being logged in a reject file?

+1 vote
Informatica writes rejected rows into a bad file, how to avoid that?

I have developed an Informatica PowerDesigner 9.1 ETL Job which uses lookup and an update transform to detect if the target table has the the incoming rows from the source or not. I have set for the Update transform a condition

IIF(ISNULL(target_table_surrogate_id), DD_INSERT, DD_REJECT)

Now, when the incoming row is already in the target table, the row is rejected. Informatica writes these rejected rows into a .bad file. How to prevent this? Is there a way to determine that the rejected rows are not written into a .bad file? Or should I use e.g. a router insted of an update transform to determine if the row is insert row an then discard the other rows?

+2 votes
Informatica writes rejected rows into a bad file, how to avoid that?

I have developed an Informatica PowerDesigner 9.1 ETL Job which uses lookup and an update transform to detect if the target table has the the incoming rows from the source or not. I have set for the Update transform a condition
IIF(ISNULL(target_table_surrogate_id), DD_INSERT, DD_REJECT)

Now, when the incoming row is already in the target table, the row is rejected. Informatica writes these rejected rows into a .bad file. How to prevent this? Is there a way to determine that the rejected rows are not written into a .bad file? Or should I use e.g. a router insted of an update transform to determine if the row is insert row an then discard the other rows?

...