Search Results wf events




The SYSTEM.ROLLING$EVENTS table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical system-level table that tracks rolling patch application events during maintenance operations. This table is part of Oracle's Online Patching (ADOP) framework, introduced in EBS 12.2 to enable zero-downtime patching. Below is a detailed technical breakdown of its purpose, structure, and significance.

Purpose and Context

In Oracle EBS 12.2, the ADOP (Online Patching) utility allows patches to be applied to a secondary patch edition while the primary run edition remains operational. The SYSTEM.ROLLING$EVENTS table logs metadata about patching sessions, including patch starts, completions, failures, and cutover operations. It serves as an audit trail for administrators to monitor patching progress and troubleshoot issues.

Table Structure

The table contains columns that capture essential patching event details, such as:
  • EVENT_ID – A unique identifier for each patching event.
  • EVENT_TYPE – The type of event (e.g., PATCH_START, PATCH_END, CUTOVER).
  • EVENT_TIMESTAMP – The timestamp when the event occurred.
  • SESSION_ID – The ADOP session ID associated with the event.
  • PATCH_ID – The patch number being applied (if applicable).
  • STATUS – The status of the event (e.g., SUCCESS, FAILED, IN_PROGRESS).
  • ERROR_MESSAGE – Detailed error logs if the event failed.

Usage in Patching Cycles

During an ADOP cycle, the table is updated at key stages:
  1. Prepare Phase: Logs initialization of the patching environment.
  2. Apply Phase: Records patch application attempts and outcomes.
  3. Finalize/Cutover Phase: Tracks the transition from the patch edition to the run edition.
  4. Cleanup Phase: Notes the completion of post-patch tasks.

Significance in Troubleshooting

Administrators query this table to:
  • Verify if a patch was applied successfully.
  • Identify failed patching sessions and diagnose errors.
  • Monitor long-running patching operations.
  • Audit historical patching activities for compliance.

Differences in EBS 12.1.1

In EBS 12.1.1 (which lacks Online Patching), the table may still exist but is less prominent, as traditional patching methods (adpatch) do not rely on it. However, in 12.2.2, it is integral to the ADOP framework.

Best Practices

  • Regularly archive old records to prevent table bloating.
  • Query with SYSTEM privileges, as it is owned by the SYS schema.
  • Use ADOP utilities (adop -status) instead of direct queries when possible.

Conclusion

The SYSTEM.ROLLING$EVENTS table is a cornerstone of Oracle EBS 12.2’s Online Patching infrastructure, providing visibility into patching operations. Its structured logging mechanism ensures traceability and aids in maintaining system reliability during maintenance. For EBS 12.1.1, its role is minimal, but in 12.2.2, it is indispensable for patch lifecycle management.