top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

creation of error file and rejected file while running the work flow/Informatica

+2 votes
630 views

If work flow run on informatica level how to create the automatically file create error reocrds and rejected records in one file.

posted Aug 20, 2013 by Jai Prakash

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

1 Answer

0 votes

Go to Session> Config Object > Error Handling > Error Log Type > Flat File and give the flat file location details.
Note: This option is effective from Informatica 9 onwards

answer Jun 11, 2014 by Shatark Bajpai
Similar Questions
+1 vote
How to create the error file and rejected file while running the work flow

If work flow run on informatica level how to create the automatically file create error records and rejected records in one file.

+2 votes
Error while reading source file name starts with a number in informatica

The source file name in my project starts with a number for example 20070908abcd.csv. Informatica is not allowing to read the source in the designer and displays the following message:
The first character in this name cannot be a number.

Could you please let me know how to handle as many source files are of this format?

+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?

+1 vote
Rejected rows into a bad file, how to avoid that when using Informatica

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?

...