Search Results edw_compile_packages




Overview
Explore in AI Chat

Overview

The concurrent program EDW_COMPILE_PACKAGES is a standard Oracle E-Business Suite utility owned by the BIS - Applications BIS product family. Its user-facing name in the Concurrent Programs form is Recompile Invalid Packages, and the documented description carries the same wording. The program exists to identify and recompile PL/SQL packages that have been left in an invalid state within the database, a condition that commonly arises after patches, upgrades, language installations, or object dependency changes. Because BIS (Business Intelligence System) and the broader Enterprise Data Warehouse (EDW) schema objects depend on a large set of PL/SQL packages, leaving compiled units invalid can cause runtime failures in extraction, transformation, and reporting processes. Running this concurrent program restores the invalid units to a valid state without requiring manual DBA intervention through SQL*Plus or the database compiler.

Execution Details

The ETRM metadata documents the following execution attributes for both Oracle EBS 12.1.1 and 12.2.2:

  • Product: BIS - Applications BIS
  • User Name: Recompile Invalid Packages
  • Description: Recompile Invalid Packages
  • Enabled: Yes
  • Execution Method: PL/SQL Stored Procedure
  • Argument Method: Standard
  • Executable: EDW_COMPILE_PACKAGES
  • Execution Filename: edw_compile_packages.compile_packages

The program therefore invokes the stored procedure edw_compile_packages.compile_packages directly through the concurrent manager. Because the execution method is PL/SQL Stored Procedure rather than a host script or Java class, no operating-system-level shell or executable is involved. The Standard argument method means that the concurrent program does not use a specialized token-based parameter scheme; parameters, if defined, are passed as ordinary concurrent program arguments.

How to Run

Users submit the program through the standard Submit Requests (SRS) window, selecting Recompile Invalid Packages from the list of available concurrent programs. The request can be scheduled on demand or as part of a recurring batch, which is common practice following an upgrade, a patch application, or a full ADOP cycle. The documented metadata does not list required parameters, and in most deployments the program is executed without user-supplied arguments. The concurrent manager processes the request under the responsibility and application of the submitting user. Because the procedure recompiles invalid database objects, the request should be granted only to users with the appropriate system administrator or DBA-level privileges, and it should not be submitted concurrently with conflicting DDL operations on the same schema.

Related Objects

The program sits alongside other maintenance and housekeeping utilities in the BIS and EDW functional area. Commonly associated objects include the EDW staging and interface tables that depend on the recompiled packages, the EDW extraction and load programs that execute those packages, and the standard Oracle diagnostics such as utlrp.sql, which performs a similar recompilation directly at the database tier. DBAs should also be aware of the DBA_OBJECTS and ALL_OBJECTS views, used to confirm object validity before and after submission, and of concurrent programs that call related EDW PL/SQL units. When invalid objects persist after the request completes, the concurrent request log should be reviewed for compilation errors, since the program reports failures through the standard concurrent manager log file. Coordination with standard patch and upgrade procedures ensures the BIS schema remains valid and available for downstream reporting.