⚡ Trace Insights

PeopleSoft Trace Insights — Browser Edition

mem: —

📁

Analyze a PeopleSoft Trace

Drop a .tracesql, .trc, or .aet file here.
Executed 100% locally in client memory — zero uploads

Initializing…

Time Distribution

Top 10 Slowest Operations

PeopleSoft Trace Settings & Diagnostics Quick Reference

Use the smallest trace that answers the question. Trace settings are additive bitmasks. SQL and PeopleCode tracing can add overhead and trace files can contain sensitive values.

Oracle: Configuring SQL Trace | Oracle: Configuring PeopleCode Trace | Oracle: Trace Section

Recommended trace recipes

Slow online page / SQL performance

TraceSQL=3

SQL statements (1) + bind variables (2). Oracle documents 3 as the typical essential SQL trace. Add 4 when commit/rollback/connect context is needed.

SQL fetch / transaction behavior

TraceSQL=7 or 15

7 adds connect/disconnect/commit/rollback. Add 8 for fetch events when row-fetch behavior matters. Higher levels increase volume.

PeopleCode execution flow

TracePC=1

Traces the program as it runs and implies program-start, external-function, and internal-function tracing. Use for event-flow and loop investigations.

PeopleCode variable/value issue

TracePC=1+4+8

Execution plus assignments and fetched values. Add 512+1024 when parameter flow matters. Use only for a targeted reproduction.

AE step / control-flow problem

TraceAE=1+2

Step sequence plus Application Engine SQL. Use when a section/step/action executes unexpectedly or you need SQL-to-step context.

AE performance

TraceAE=128; add 256

128 produces statement timings. 256 adds method/built-in detail. Add 2 when SQL attribution is needed.

AE temporary-table issue

TraceAE=4; add 8

4 traces dedicated temp-table allocation. 8 traces temp-table data and is higher volume; use it when row-level effects are important.

AE execution plan

TraceAE=2048 or 4096

Optimizer trace to file or tables, subject to RDBMS/platform support. Use when timing evidence identifies a SQL plan problem.

Integration Broker transform

TraceAE=8192

Use for transform-program problems. Oracle documents transform trace output for the original XML and transformed output.

Long-term AE SQL timing history

TraceAE=16384

SQL timings stored in PS_AE_TIMINGS_LG and PS_AE_TIMINGS_DT where supported by the PeopleTools interface/release.

TraceSQL — PeopleTools 8.63

Bit	Meaning	Use
1	Statements	SQL text.
2	Variables	Bind values.
4	Connect	Connect/disconnect/commit/rollback.
8	Fetch	Fetch occurrence and return code.
16	Most other API	Additional API calls except SSB.
32	SSB	Set Select Buffers.
64	DB-specific	Database API-specific calls.
128	COBOL	COBOL statement timings.
1024	DB2 z/OS diagnostic	Diagnostic messages from the documented %UpdateStats path.

TracePC — PeopleTools 8.63

Bit	Meaning	Use
1	Functions	Program execution; implies 64/128/256.
2	List	Entire program listing.
4	Assignments	Variable assignments.
8	Fetches	Fetched variable values.
16	Stack	PeopleCode evaluator stack; mainly language/evaluator debugging.
64	Starts	Program starts.
128	External functions	Application-written external routines.
256	Internal functions	PeopleTools internal/built-in calls.
512	Params in	Function parameters on entry.
1024	Params out	Function parameters on return.

TraceAE — Application Engine

Bit	Meaning	Use
1	Step sequence	Control flow.
2	Application SQL	SQL-to-step correlation.
4	Dedicated temp-table allocation	Allocation/locking/release.
8	Temp-table data	Rows/data effects; high volume.
128	Statement timings to file	AE bottlenecks.
256	Method/built-in detail	Detailed PeopleCode timing.
1024	Timings to tables	Batch timing tables.
2048	Optimizer trace to file	Execution/query plan evidence.
4096	Optimizer trace to tables	Plan evidence in supported environments.
8192	IB transform	Transform program tracing.
16384	SQL timings to PS_AE_TIMINGS_LG/DT	Historical SQL timing data where supported.

Scenario matrix

Problem	Start with	Next step
Slow online transaction	TraceSQL=3	Add TracePC=1 if PeopleCode attribution is required.
Wrong field/variable value	TracePC=1+4+8	Add 512+1024 for parameter flow.
Save / FieldChange loop	TracePC=1	Add TraceSQL=3; inspect repeated event and SQL chains.
Database error	TraceSQL=3	Add TraceSQL=4 for transaction context and TracePC=1 for caller attribution.
AE unexpected step	TraceAE=1+2	Add TracePC=1 for PeopleCode actions.
AE slow process	TraceAE=128	Add 256, then 2; use 2048/4096 for plan evidence.
AE temp-table contention/data	TraceAE=4	Add 8 only when needed.
IB transform error	TraceAE=8192	Also inspect Service Operations Monitor transformation details.
File attachment issue	TracePC=2048 where documented for your release	Oracle documents 2048 for statement tracing in the file-attachment troubleshooting guidance; verify the flag in your PeopleTools release/UI.

Interpretation rules used by Trace Insights

Heuristics are not proof. A repeated SQL fingerprint is a candidate N+1 pattern, not proof of N+1. A statement without WHERE is an unconstrained-SQL review signal, not proof of a full table scan. A slow statement without optimizer evidence does not prove a bad execution plan.

For a defensible root-cause conclusion, prefer correlated evidence: error → SQL → bind → PeopleCode/AE step → surrounding trace context. The analyzer shows confidence and should distinguish confirmed evidence from review candidates.

Tracing can materially affect performance. Use the minimum trace needed, reproduce narrowly, and turn tracing off after collection. Trace files can contain SQL bind values and PeopleCode values and should be handled as sensitive diagnostic artifacts.

Time Distribution

Top 10 Slowest Operations

🔀 Select Two Trace Files for Comparison