Oracle Database / SQL Performance & Memory
Inspect parallel workers before increasing application concurrency
A batch can use many workers and compete with foreground requests. Inspect the current parallel sessions and their coordinator.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT qcsid, qcserial#, qcinst_id, sid, serial#, server_group, server_set FROM v$px_session;Read the result
Rows describe participating parallel sessions on this instance. Worker counts and requested degree are not the same as application connection count.
Resolve and verify
Identify the coordinator's SQL and compare demand with CPU and resource policy. Tune the statement or schedule and degree through the DBA rather than adding more concurrent jobs.
Operational precautions
In RAC, collect instance-aware evidence. Raising parallelism can increase memory, TEMP and I/O pressure.