gazulas

 Profile Answers by gazulas Questions by gazulas

• Feb 11th, 2006

 

go to the session log file there we will find the information regarding to the

session initiation process,

errors encountered.

load summary.

so by seeing the errors encountered during the session running, we can resolve the errors.

madhu

• Feb 15th, 2006

 

You can create some generalized transformations to handle the errors and use them in your mapping. For example for data types create one generalized transformation and include in your mapping then you will know the errors where they are occuring.

Hemant Bhavsar

• Apr 3rd, 2006

 

Also you can setup bad files and rejected files which you can use to see error records. There is a way also to reload bad/rejected records using information tools.

sreenivasareddy.aug10

 Profile Answers by sreenivasareddy.aug10 

• Jul 10th, 2009

 

Error Handling
Sometimes a stored procedure returns a database error, such as “divide by zero” or “no more rows”. The final result of a database error during a stored procedure differs depending on when the stored procedure takes place and how the session is configured.

You can configure the session to either stop or continue running the session upon encountering a pre- or post-session stored procedure error. By default, the PowerCenter Server stops a session when a pre- or post-session stored procedure database error occurs.

Rajan Raorane

 Profile Answers by Rajan Raorane 

• Oct 21st, 2010

 

Scenario in which when a load of 1000 records is loaded into the target and 100 records are bad records, those hundred goes to badfile dir which mention Session and the rest of the 900 should load to the target, I kept stop on errors as zero. But when I get even one error the session itself fails and rollbacks all the records.