Results for “analyze_table”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSD_ANALYZE_TABLES is an APPS-owned PL/SQL package shipped as part of the Oracle E-Business Suite database tier. It is classified in the ETRM repository under the API classification OTHER, indicating that it is an internal utility rather than a published, supported business API. The package is declared with AUTHID CURRENT_USER, so its unqualified object references resolve against the privileges of the calling schema rather than the defining schema.

Its purpose is narrowly scoped: it provides a programmatic wrapper around Oracle optimizer statistics collection for a designated database table. In an EBS environment the Cost-Based Optimizer depends on accurate statistics, and the concurrent "Gather Schema Statistics" program (FND_STATS) normally performs this work on a scheduled basis. MSD_ANALYZE_TABLES offers a lighter-weight, callable alternative that permits a single table to be analyzed on demand from within PL/SQL, without submitting the full concurrent request. The $Header line records an original file version of 115.0 dated 2002, so the object is long-standing and stable, and the metadata shows it is referenced by nine other packages, which suggests it is embedded in a wider chain of internal EBS maintenance logic rather than being invoked in isolation.

Key Procedures and Functions

The documented interface consists of a single procedure. Because this is a package specification with no corresponding documentation of a body, only the following entry is exposed and confirmed by the ETRM metadata:

• ANALYZE_TABLE — Accepts a table name and a type indicator and performs statistics analysis for that table. The parameters are declared as p_table_name (IN VARCHAR2) and p_type (IN NUMBER); the numeric type argument selects the mode of analysis, consistent with the DBMS_STATS or ANALYZE conventions that distinguish computation of statistics from deletion or validation. Callers must supply a valid table name and a recognized type value; behavior for unsupported values is not documented.

The specification additionally declares two PL/SQL collection types, table_type (a RECORD containing table_name and table_type) and table_type_list (an associative array of table_type indexed by binary_integer). These are declared within the package for internal use and are not documented as callable routines. No public functions are exposed.

Tables Accessed

The ETRM metadata records one referenced table via APPS synonyms: PLITBLM. Because the package is compiled AUTHID CURRENT_USER, and because statistics utilities are dynamic in nature, the actual target of analysis is the table named at runtime by p_table_name rather than a statically listed object. PLITBLM therefore represents the documented static dependency; it is a system-level table used by the EBS statistics infrastructure, and the package reads from or writes to it in the course of executing ANALYZE_TABLE.

It should be noted that no application data tables are declared as static dependencies. Any additional objects touched are resolved dynamically at execution time through the caller's schema context.

Usage Notes

Because MSD_ANALYZE_TABLES is categorized as OTHER and carries no documented form, concurrent program, or menu attachment, it is not part of the supported end-user interface. Invocation is expected from custom PL/SQL code or from other EBS packages in the internal call chain — the metadata confirms nine referencing packages. Typical usage is ad hoc or post-maintenance statistics refresh on a single table where a full FND_STATS run would be disproportionate.

Administrators should prefer the supported Gather Schema Statistics concurrent program for routine maintenance and reserve direct calls to this package for diagnostic or development scenarios. Any use should be validated in a non-production environment first, since the package is internal, undocumented beyond its specification, and unsupported by Oracle. Custom code depending on it should be reviewed before an upgrade to 12.1.1 or 12.2.2, as internal utility packages may change without notice.