top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Where to store informatica rejected data? How to extract the informatica rejected data ?

+1 vote
390 views
Where to store informatica rejected data? How to extract the informatica rejected data ?
posted Apr 9, 2015 by Amit Sharma

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

1 Answer

0 votes

The reject rows say for example due to unique key constrain is all pushed by session into the $PMBadFileDir (default relative path is <INFA_HOME/PowerCenter/server/infa_shared/BadFiles) which is configured with path at Integration Service level. Every Target will have property saying Reject filename which gives the file in which rejects rows are stored.

answer Apr 9, 2015 by Manikandan J
Similar Questions
+1 vote
How to extract the number(0-9) from the string in informatica?

I want to extract the number(0-9) from the string. e.g.
1.if src is *J$456*&56 then tgt should be 45656
2.if src is &*(>123>>789&^ then tgt should be 123789

This is just an example, special characters or alphabets are random in string, so how to extract only numbers?

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

+5 votes
How to extract number from a string in Informatica?

I want to extract the number(0-9) from the string. e.g. if src is *Ax456*&56 then dst should be 45656.

...