Cloud ETL
Informatica PowerCenter
The repository database holds mappings, sessions and run statistics — including per-target row counts.
PowerCenter estates are among the oldest still carrying critical load, and they are
well served by their own repository. The repository database exposes a set of
REP_* views describing mappings, sessions, workflows and — most usefully — per
target-instance row statistics for every session run.
REP_SESS_TBL_LOG is the standout. It records applied, affected and rejected
rows per target per session, which is a complete reconciliation recorded automatically. Very
few platforms offer this, and most teams running PowerCenter have never queried it.
What Decim reads from Informatica PowerCenter
Every item below is read-only, and each is a specific view, endpoint or file rather than a category of access. If something here is unacceptable in your environment, it can be removed from the query catalogue — see the agent for how that works.
| What | From | Why it matters |
|---|---|---|
| Session runs | REP_SESS_LOG | Status, start, end and error per session run |
| Per-target row counts | REP_SESS_TBL_LOG | Applied, affected and rejected rows per target instance |
| Workflow structure | REP_WORKFLOWS, REP_TASK_INST | Task order and dependencies |
| Mappings | REP_ALL_MAPPINGS | Mapping inventory and their folders |
| Source/target fields | REP_SRC_FLD, REP_TARG_FLD | Column-level structure |
| Connections | REP_SESSION_CNXS | Which physical systems a session touched |
| Schedules | REP_WFLOW_RUN | Workflow run history and cadence |
Permissions required
Written out in full, because "read-only access" is not a specification. Nothing below grants the ability to write, and row access is requested only on the specific tables you name.
-- The repository is an ordinary Oracle or SQL Server database.
-- Grant SELECT on the REP_ views only — never on the underlying OPB_
-- tables, which are internal and not a supported interface.
GRANT SELECT ON REP_SESS_LOG TO decim_agent;
GRANT SELECT ON REP_SESS_TBL_LOG TO decim_agent;
GRANT SELECT ON REP_WORKFLOWS TO decim_agent;
GRANT SELECT ON REP_TASK_INST TO decim_agent;
GRANT SELECT ON REP_ALL_MAPPINGS TO decim_agent;
GRANT SELECT ON REP_SESSION_CNXS TO decim_agent;
-- The reconciliation this platform gives you for free:
SELECT SESSION_NAME, TABLE_NAME,
SUCCESSFUL_ROWS, FAILED_ROWS, THRUPUT
FROM REP_SESS_TBL_LOG
WHERE SESSION_TIMESTAMP >= SYSDATE - 1
ORDER BY FAILED_ROWS DESC;What it builds
What this source contributes to the pipeline topology and to the evidence available during an investigation:
- Workflow and session topology with task dependencies
- Per-target row counts — applied, affected and rejected — for every run
- Which physical connections each session used
- Mapping inventory, including mappings no workflow references
Nodes learned from a definition are marked declared; nodes observed running are marked observed; nodes both declared and observed are verified. Where two sources disagree, the disagreement is recorded as a drift note rather than resolved silently.
Failure modes it surfaces
What this source is uniquely good at proving — and, just as usefully, at disproving. An investigation that can refute a hypothesis cheaply is worth as much as one that confirms it.
| Failure mode | The signal |
|---|---|
| Rows rejected silently | FAILED_ROWS non-zero on a succeeded session |
| Session succeeded with zero rows | SUCCESSFUL_ROWS at zero |
| Workflow stopped being scheduled | No run rows after a date, with no failure |
| Connection repointed | Connection value differing from the previous good run |
Limits
What this integration cannot tell you. Stated because an investigation that overstates its sources produces confident wrong answers, which is worse than an honest blocked.
- Reject files themselves live on the integration service host, not in the repository
- The
REP_views are documented but vary between PowerCenter versions - Informatica Cloud (IICS) has a completely different metadata surface and is not covered by this page
Related integrations
- Oracle Database — ALL_SOURCE for PL/SQL bodies, DBA_TAB_MODIFICATIONS for write activity, DBA_SCHEDULER_JOBS for schedules.
- SSIS — SSISDB holds executions, per-component row counts and the parameter values actually used.
- SQL Server Agent — Job steps are rows in msdb, not files in git. Reads sysjobs, sysjobsteps and sysjobhistory.
See all integrations, or how the sources are combined into one graph.
Get started
Investigating a Informatica PowerCenter pipeline?
Bring an incident you already know the answer to. If Decim gets it wrong, that is a more useful demo than one where it doesn't.