Search Results start_plan

Overview

SYS.DBMS_ROLLING is an Oracle-supplied database package (defined with AUTHID CURRENT_USER) that orchestrates rolling upgrades and rolling migrations across a set of Oracle Data Guard administered databases. Within the Oracle E-Business Suite 12.1.1 / 12.2.2 environment, this package is the engine that supports Oracle's "zero downtime" patching and upgrade strategy, allowing an EBS database and its associated physical standby databases to be upgraded to a higher binary version while the primary remains available to users. The package coordinates the sequence of upgrade phases — initialization, plan construction, execution, switchover, finish, and optional rollback — against every database listed in the Data Guard configuration (DG_CONFIG). For EBS customers, this functionality is most relevant to major version upgrades and to the reduced-downtime upgrade approach documented for moving between database releases. The package is owned by SYS and is classified under the "OTHER" API category in ETRM, indicating it is an Oracle core database utility exposed for administrative use rather than an EBS application-level API.

Key Procedures and Functions

Nine procedures are documented for DBMS_ROLLING:

• INIT_PLAN — The mandatory first call. It communicates with the complete set of databases in DG_CONFIG and creates a default rolling upgrade configuration, establishing the foundation for subsequent phase planning.
• SET_PARAMETER — Sets configurable rolling upgrade parameters that tailor the upgrade plan to the environment.
• BUILD_PLAN — Either builds a complete upgrade plan or modifies the remaining unprocessed portion of an existing plan, interpreting the configured parameters to produce a customized plan.
• START_PLAN — Begins execution of the START phase instructions in the upgrade plan. This is the procedure most frequently referenced by administrators initiating the rolling upgrade sequence.
• SWITCHOVER — Executes the SWITCHOVER phase instructions, transitioning the upgraded standby databases to the primary role.
• FINISH_PLAN — Executes the FINISH phase instructions after START and SWITCHOVER complete, once the original primary and its physical standbys have been restarted on the higher version binaries. Upon completion, the original primary and standbys have recovered the upgrade redo.
• ROLLBACK_PLAN — Returns the group of administered databases to their initial state by flashing back all databases in the leading change group to their guaranteed restore points. It is permitted only if switchover has not yet been performed.
• DESTROY_PLAN — Purges all rolling upgrade state from the database and is called upon completion of the rolling upgrade.

Tables Accessed

The provided ETRM metadata does not document any tables referenced via APPS synonyms, and the package is not referenced by any other EBS packages. DBMS_ROLLING operates primarily on Oracle core internal tables and Data Guard views that track rolling upgrade state, restore points, and DG_CONFIG membership rather than on EBS application schema tables such as those in the APPS or FND schemas. Consequently, no EBS-level table dependencies are exposed for this object.

Usage Notes

DBMS_ROLLING is invoked directly from a SQL*Plus or equivalent database session by a privileged DBA, not from EBS forms or concurrent programs. It is not registered as an EBS application API and has no APPS-layer callers. Typical invocation follows a strict procedural sequence: INIT_PLAN, optional SET_PARAMETER calls, BUILD_PLAN, START_PLAN, SWITCHOVER, FINISH_PLAN, and finally DESTROY_PLAN to clean up state. ROLLBACK_PLAN is available as a recovery path only before switchover. Because the package powers a database-level operation, its use in EBS environments should be coordinated with the EBS upgrade lifecycle and with the documented reduced-downtime upgrade procedures for the specific release (12.1.1 or 12.2.2) being applied.