• Reports Conversion
  • Oracle HCM Analytics
  • Oracle Health Analytics
  • Services
    • ETL SolutionsETL Solutions
    • Performed multiple ETL pipeline building and integrations.

    • Data Lake IconData Lake
    • Experienced in building Data Lakes with Billions of records.

    • e-flyer migration solutions menuMigration Solutions
    • Modernize BI reporting with automated migration.

    • BI Products MenuBI products
    • Successfully delivered multiple BI product-based projects.

    • Legacy Scripts MenuLegacy scripts
    • Successfully transitioned legacy scripts from Mainframes to Cloud.

    • AI/ML Solutions MenuAI ML Consulting
    • Expertise in building innovative AI/ML-based projects.

  • Contact Us
  • Blogs
  • ETL Insights Blogs
  • Informatica PowerCenter Error Handling Debugging

Contents

1/11
Where Do Errors Go? A Quick Map Common Session Failures and What They Usually Mean Read the Logs in the Right Order Row Error Logging: Set It Up Once Recover Failed Sessions Without Reprocessing Debug Mapping Logic Alerting and Monitoring PowerCenter in 2027: Fix Now, Plan the Exit Public Sector and Government Considerations Frequently Asked Questions Scope Your PowerCenter Work with DataTerrain
  • 17 Nov 2026

PowerCenter Error Handling: Where Did Rejected Rows Go?

In Informatica PowerCenter, failed rows land in different places depending on how the session is configured. By default, transformation errors go to the session log and rejected rows go to the reject file. If you turn on row error logging, errors go to error tables or an error file instead, and the reject file is no longer created. With full pushdown optimization, the database handles errors, and the Integration Service does not write reject rows to the reject file. To handle errors well, choose one logging method, read the session log from the first error, set a recovery strategy, and use the Debugger for logic problems. PowerCenter 10.5.x standard support also ended on March 31, 2026, so decide how long you will keep investing in it.

Most PowerCenter troubleshooting advice is a list of generic tips. The questions that cost teams time are more specific: where did my rejected rows go, why will this session not recover, and which log should I read first? This page answers those, and then covers what the 2026 support date means for how much effort you put into old workflows.

If you run a lot of PowerCenter, our ETL operations and workflow efficiency articles cover the surrounding practices.

Quick Summary

Pick one error logging method per session, because PowerCenter changes where failed rows go depending on the choice. Read session logs from the first error, use tracing levels sparingly, and configure a recovery strategy before a failure forces the question. Treat the March 2026 support date as a planning input for your PowerCenter estate.
informatica-powercenter
  • Share Post:
  • LinkedIn Icon
  • Twitter Icon

Key Takeaways

  • Where errors land depends on configuration. Default logging, row error logging, and pushdown each behave differently.
  • Row error logging replaces the reject file. Enable it deliberately, and do not expect both.
  • Read the first error, not the last. Later messages are often consequences.
  • Recovery must be configured in advance. Resuming from the last checkpoint has rules that not every session meets.
  • Support dates affect effort. Standard support for PowerCenter 10.5.x ended on March 31, 2026.

Where Do Errors Go? A Quick Map

Situation Where Failed Rows or Messages Land Watch Out For
Default sessionTransformation errors in the session log, rejected rows in the reject fileEasy to miss if nobody reads the files
Row error logging to tablesError tables, including the source row dataNo reject file is created, and dropped rows are not written to the session log
Row error logging to a fileAn error log fileSame replacement of the reject file
Verbose data tracingRow data in the session log, which can also be added alongside row error loggingSlows the session and enlarges logs
Full pushdown optimizationHandled by the databaseThe Integration Service does not write reject rows to the reject file
XML sourcesThe session logRow errors from XML sources cannot be logged to error tables

What this means for you: Before a failure forces the question, decide which method each session uses and write it down.

Common Session Failures and What They Usually Mean

  • Connection and permission failures. Network or firewall changes, expired credentials, and locked accounts stop a session before data moves.
  • Missing or changed sources. A source file that did not arrive, or a table whose columns changed, breaks reads. Our article on schema evolution explains how to plan for source changes.
  • Data truncation and type errors. Values that exceed a column’s length or precision, or that do not convert cleanly, are the most common row errors.
  • Lookup surprises. A lookup that finds no match returns NULL, which then flows into later logic. Handle the null case explicitly, with a default value or a check.
  • Slow sessions. Heavy joins, large lookups, and undersized buffers show up as time, not errors. Compare read, transform, and write statistics against a healthy run.

Read the Logs in the Right Order

  1. Start with the session log, and find the first error, not the last. Later messages are often consequences.
  2. Check the Workflow Monitor for which task failed and when.
  3. Use tracing levels with care. Normal tracing is the default, and the verbose levels log far more detail, with verbose data logging each row. Use them on a small sample, because they slow sessions and flood logs.
  4. Search large logs with grep on Linux or Find on Windows for the error code and surrounding lines.
  5. Query the error tables if row error logging is on, and filter by session and error type.

Message codes carry a short prefix that points to the area, so note the prefix when you search Informatica’s documentation or ask for support.

Row Error Logging: Set It Up Once

When you enable relational error logging, PowerCenter creates error tables the first time the session runs. Informatica documents these tables:

  • PMERR_DATA stores data and metadata about a transformation row error and its source row.
  • PMERR_MSG stores metadata about the error and the error message, including whether it was a reader, writer, or transformation error.
  • PMERR_SESS stores metadata about the session.

If you use the same table prefix across sessions, you can collect row errors from many sessions into one set of tables, and a session parameter in a parameter file keeps that manageable. Two cautions apply. First, the error tables store the source row data, so treat them as sensitive. Second, row errors from XML sources cannot be logged this way and appear in the session log.

What this means for you: Agree on one table prefix and one retention rule, then query the tables as part of daily monitoring.

Recover Failed Sessions Without Reprocessing

Informatica offers three recovery strategies for a session: resume from the last checkpoint, restart the task, or fail the task and continue the workflow.

  • Resume from the last checkpoint restarts at the point of interruption using saved state. It cannot be used with mapping variables, and the recovery run must produce the same data as the original, so sessions that cannot produce repeatable data are not valid candidates.
  • Restart task reruns the session from the beginning, so confirm that reruns are safe for your targets.
  • Fail task and continue workflow marks the session failed and lets the rest of the workflow run.

To recover, right-click the session in the Workflow Monitor and choose Recover Task, or use the pmcmd starttask command with the recover option. Test recovery on a non-production run before you depend on it, and pair it with incremental loads and duplicate checks. Our automated ETL testing and data migration testing tools articles describe how to prove that a rerun leaves the target correct.

Debug Mapping Logic

  • Use the Debugger in the Designer. Set breakpoints, step through transformations, and watch values, ideally on a small sample before a full run.
  • Use the ERROR and ABORT functions deliberately. ERROR skips a row and logs a message, while ABORT stops the session with a message. They turn a business rule into a controlled failure.
  • Be careful with lookup caches. A dynamic lookup cache is designed to keep the cache in step with a target, so use it for that, not as a failure fix.
  • Add targeted logging. Write key counts and timings to a logging table so you can compare runs and spot trends.

Alerting and Monitoring

Decision tasks can branch on session status, email tasks can notify the right team, and command tasks can trigger a recovery script. Standardize these across workflows, store run history in a logging database, and review error trends weekly. Our ETL data pipeline automation article shows how teams extend this into broader automation.

PowerCenter in 2027: Fix Now, Plan the Exit

Informatica’s own site says PowerCenter 10.5.x standard support ended on March 31, 2026, and third-party sources report extended support to about March 2027, so confirm the dates for your version. Salesforce completed its acquisition of Informatica in November 2025. None of this means workflows stop running, but it changes how much to invest in them.

A sensible approach is to fix the errors that cause real risk now, document the rest, and decide a direction:

  • Stay and extend. Buy extended support while you plan, as described on our Informatica ETL consulting services page.
  • Move to the cloud platform. Compare PowerCenter with Informatica’s cloud service in our PowerCenter vs IICS comparison, and see our Informatica IICS migration page.
  • Move to another platform. Our Informatica to Databricks article covers the lakehouse route, and our ETL migration solution overview covers the wider process.

AI assistants will increasingly use the data these pipelines deliver, so tested, traceable loads matter more than before. That is an expectation, not a certainty, but clean error handling today makes any later migration easier. If you are also weighing Oracle tools, see our ODI vs Informatica comparison, and for general practices, see our article on maximizing data integration success with Informatica.

Public Sector and Government Considerations

This section is planning guidance, not a statement of DataTerrain’s authorization status or government work. Public sector and other regulated teams should check these points:

  • Audit evidence. Keep session logs, error tables, and recovery records as evidence where retention rules require it.
  • Sensitive data in error tables. Row error tables store source row data, so apply the same access controls as the source, as our data security compliance article explains.
  • Support status in the risk register. Record that PowerCenter 10.5.x standard support has ended, along with your extended support and exit plan.
  • Change control. Fixes and migrations should follow your approval cycles, with a rollback plan.

Frequently Asked Questions

Where are rejected rows stored in Informatica PowerCenter?
By default, rejected rows go to the reject file and transformation errors go to the session log. If you enable row error logging, errors go to error tables or an error file instead, and the reject file is not created. With full pushdown optimization, the database handles errors, and no reject rows are written to the reject file.
How do you recover a failed PowerCenter session?
Configure a recovery strategy of restart or resume from the last checkpoint, then right-click the session in the Workflow Monitor and choose Recover Task, or use the pmcmd starttask command with the recover option. Resume from the last checkpoint cannot be used with mapping variables and needs repeatable data.
What is the difference between a reject file and row error logging?
The reject file is the default place for rows the target rejects, while row error logging collects errors, messages, and source row data into relational tables or a file. Turning on row error logging replaces the reject file, so choose one on purpose.
How do you debug a mapping in PowerCenter?
Use the Debugger in the Designer to set breakpoints and step through transformations on a small sample, use verbose tracing only on limited runs, and use the ERROR and ABORT functions to turn business rules into controlled failures.
Is Informatica PowerCenter still supported?
Informatica’s site states that PowerCenter 10.5.x standard support ended on March 31, 2026. Third-party sources report extended support to about March 2027, so confirm the dates for your version with Informatica.

Scope Your PowerCenter Work with DataTerrain

The costly mistake is spending months polishing workflows without deciding how long they will run. DataTerrain brings 17+ years and 400+ clients in data and reporting modernization, with PowerCenter stabilization, upgrade or migration planning, automated validation, and operating handover planned together.

Talk to our ETL team

Related Reading

Informatica PowerCenter and MDM   |   Advantages of Informatica PowerCenter   |   Mastering Data Quality with Informatica   |   Informatica Cloud vs SnapLogic   |   SnapLogic vs Informatica   |   AWS Glue vs Informatica Cloud

Categories
  • All
  • BI Insights Hub
  • Data Analytics
  • ETL Tools
  • Oracle HCM Insights
  • Legacy Reports conversion
  • AI and ML Hub
Customer Stories
  • All
  • Data Analytics
  • Reports conversion
  • Jaspersoft
  • Oracle HCM
Recent posts
  • informatica-powercenter
    PowerCenter Error Handling: Where Did...
  • what-is-oracle-etl
    What Is Oracle ETL? A Family of Tools, Not One...
  • odi-oracle-vs-traditional-etl
    Oracle Data Integrator vs Traditional...
Connect with Us
  • About
  • Careers
  • Privacy Policy
  • Terms and condtions
Sources
  • Customer stories
  • Blogs
  • Tools
  • News
  • Videos
  • Events
Services
  • Reports Conversion
  • ETL Solutions
  • Migration Solutions
  • Data Lake
  • Legacy Scripts
  • Oracle HCM Analytics
  • BI Products
  • AI ML Consulting
  • Data Analytics
Get in touch
  • connect@dataterrain.com
  • +1 650-701-1100

Subscribe to newsletter

Enter your email address for receiving valuable newsletters.

logo

© 2026 Copyright by DataTerrain Inc.

  • twitter