Results for “start_plan”

14 results




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

Overview

SYS.DBMS_ROLLING is the Oracle Database-supplied PL/SQL package that orchestrates rolling upgrade and rolling patch operations across an Oracle Real Application Clusters (RAC) environment. Within Oracle E-Business Suite 12.1.1 and 12.2.2, it is the underlying engine that supports online, minimal-downtime application of database patches and upgrades, allowing individual RAC instances to be processed sequentially while the cluster as a whole remains available to end users. In the EBS context, DBMS_ROLLING is most closely associated with the Database Preparation (dprep) and post-patch phases of the online patching cycle in 12.2.x, and with rolling database patching exercises in 12.1.1.

The package operates on a defined plan that designates a "current" instance set and a "future" instance set. Its purpose is to move the cluster through a controlled sequence of phases so that users can continue to transact on at least one instance while others are upgraded. Because it is a SYS-owned, wrapped package, its internal implementation is not readable; interaction is exclusively through the documented public API.

Key Procedures and Functions

The ETRM metadata documents the following callable routines:

  • INIT_PLAN — Initializes a new rolling plan, establishing the working structures and baseline state used by all subsequent operations.
  • BUILD_PLAN — Populates the plan with the participating instances, the designated future/current roles, and the configuration required for the rolling operation.
  • SET_PARAMETER — Sets tunable parameters that govern plan behavior, such as which instances participate or how the switchover is executed.
  • START_PLAN — Commences execution of the plan, advancing the cluster into the active rolling phase where instances are processed one at a time.
  • SWITCHOVER — Performs the transition from the current instance set to the future instance set, changing which instances serve production traffic.
  • FINISH_PLAN — Completes the plan, finalizing the operation after all instances have been converted and traffic has stabilized on the target set.
  • ROLLBACK_PLAN — Reverts the rolling operation, returning the cluster to its pre-change instance configuration when the operation cannot proceed.
  • DESTROY_PLAN — Removes the plan and its associated state entirely, cleaning up after a plan has finished or been abandoned.

Collectively these procedures constitute the complete lifecycle: initialization, construction, parameterization, execution, transition, completion, reversal, and teardown.

Tables Accessed

The ETRM record for this object documents no application tables referenced through APPS synonyms. This is expected: DBMS_ROLLING is part of the Oracle database kernel infrastructure and operates on internal SYS-managed data dictionary and repository structures rather than EBS application schema objects. Its plan metadata, instance tracking, and progress information are held in Oracle-maintained internal tables that are not exposed as APPS synonyms and are not intended for direct querying or modification by EBS administrators.

Usage Notes

DBMS_ROLLING is invoked from the database tier, not from an EBS form or a standard concurrent program. In practice it is called through SQL*Plus or a scripting harness by DBAs performing rolling database patch application or an online upgrade of the RAC cluster. The documented metadata shows the package is referenced by zero other EBS packages, confirming that it is not embedded within the application codebase and is instead an independent database utility leveraged during maintenance windows. In EBS 12.2.2 the package plays a supporting role during online patching, where the reduced-downtime architecture benefits from instance-level rolling operations; in 12.1.1 it is used in rolling patch strategies for RAC deployments. All operations must be executed as SYSDBA, and the standard sequence of INIT_PLAN, BUILD_PLAN, parameter configuration, START_PLAN, SWITCHOVER, and FINISH_PLAN (or ROLLBACK_PLAN followed by DESTROY_PLAN) should be observed.