Skip navigation

Log In

Forgot your password?
Don’t have an account? Sign Up

Sign Up

Access our rich network of apps, trials, and services.

Start the registration process by entering your email address below.

Already have an account? Log In

PowerCenter: Logging Error Rows

Free download

Posted by: Radhakrishna Sarma

Capture Informatica PowerCenter row errors into a flat file or database during runtime.


Informatica PowerCenter logs error in the session logs. In order to capture row data information related to the error into a flat file or database table during runtime you can enable row-level error logging.

In some cases enabling row-level error logging is not feasible as it disables block processing. You can then use the technique described in this solution to log errors and source data to a flat file or an error table.

Implementation Guideline

  • In the mapping, the row data is stored in the mapping variable. If the session fails, this mapping variable data is assigned to workflow variable. The session s_m_log_error uses the workflow variable to write it to a flat file or a relational table along with session and workflow name.
  • By using this method multiple error rows cannot be logged. So, it is suitable only when the sessions are configured to fail on  first error. i.e. “Stop on errors” session attribute set to ‘1’.
  • Also the example workflow uses only one instance of the session s_m_log_error as the workflow is configured not to do further processing when any session fails. In cases where workflow is configured to continue running other sessions, then the multiple instances of s_m_log_error has to be used.


  • PowerCenter version 9.1 and 9.5


Radhakrishna Sarma is an “ETL Specialist” in an Investment Bank in Singapore. Radha has got solid experience in Oracle & Informatica and is very proficient in these areas. He has made many contributions to both the Developers’ communities through many means like OTN, Devnet, personal blog etc. His contributions are remarkably known to the Informatica Developer community.


Comments Comments (6)