Search Results dbms_sqlpa




Overview

SYS.DBMS_SQLPA is the SQL Performance Analyzer (SPA) PL/SQL package shipped with the Oracle database kernel and exposed in Oracle E-Business Suite 12.1.1 and 12.2.2. It provides a programmatic interface for building, executing, and reporting on SQL performance analysis tasks, which allow an administrator to capture a workload of SQL statements, run it against a baseline environment, replay the identical workload after a change (a database upgrade, patch application, parameter change, or optimizer statistics refresh), and compare the two executions to quantify the performance impact before the change is promoted to production.

Within EBS the package is owned by SYS and classified as an OTHER API in the ETRM repository. It is not an application-tier business API; no EBS form or concurrent program calls it directly as part of standard processing. It is leveraged by DBAs and by Oracle's own tools—most notably the SQL Tuning Advisor infrastructure—to support pre- and post-upgrade validation such as the recommended workflow executed during an EBS 12.1.1 to 12.2.2 upgrade or a database release upgrade.

Key Procedures and Functions

The documented interface exposes eighteen procedures and functions that follow the standard Advisor task lifecycle:

These procedures wrap the underlying task infrastructure in SYS.DBMS_ADVISOR.

Tables Accessed

SPA does not read or write EBS application tables. All state is persisted in the Advisor repository—principally the task, parameter, and result tables maintained by DBMS_ADVISOR (for example the DBA_ADVISOR_* and DBA_SQLPA_* views). The package additionally references SQL_BINDS when reconstructing bind information for captured statements, and depends on the STANDARD package. Results are queried through dictionary views rather than EBS synonyms.

Usage Notes

Because DBMS_SQLPA is a SYS-owned kernel package, it is invoked from SQL*Plus, SQL Developer, or custom PL/SQL by a DBA holding the ADVISOR privilege—not from EBS forms or concurrent managers. The canonical EBS pattern is to create a SQL tuning set on the pre-change system, create and execute an SPA task to establish the baseline, repeat the capture after the change, execute the comparison task, and then call REPORT_ANALYSIS_TASK to review regressions and improvements. It should be used when validating database upgrades, optimizer changes, initialization parameter modifications, or large patch rollouts. ETRM records it as referenced by four other packages, including DBMS_SQLTUNE_UTIL1, DBMS_WRR_INTERNAL, and PRVT_SQLADV_INFRA, confirming its role as shared infrastructure rather than a standalone end-user API.