Search Results action history




The SYS.REGISTRY$HISTORY table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical system-level table that tracks the history of database component registrations, patches, and upgrades applied to the Oracle database. This table is part of the Oracle Data Dictionary and is owned by the SYS schema, meaning it contains metadata about the database's evolution over time. Below is a detailed analysis of its structure, purpose, and relevance in Oracle EBS environments.

Purpose and Functionality

The SYS.REGISTRY$HISTORY table maintains a chronological record of changes made to the database registry, including:
  • Patch Applications: Tracks patches applied to the database, including interim patches, one-off fixes, and Critical Patch Updates (CPUs).
  • Upgrade History: Logs database upgrades (e.g., from 11g to 12c) and component updates (e.g., Oracle Options like Partitioning or RAC).
  • Component Registration: Records when database components (like Oracle Text, Spatial, or Advanced Security) are installed or modified.
This table is essential for auditing, troubleshooting, and compliance, as it provides a historical trail of database modifications.

Key Columns and Structure

The table includes columns such as:
  • ACTION_TIME: Timestamp of the action (e.g., patch application).
  • ACTION: Type of operation (e.g., APPLY, UPGRADE, INSTALL).
  • NAMESPACE: Category of the component (e.g., SERVER, RDBMS).
  • VERSION: Version of the component after the action.
  • ID: Unique identifier for the action (often maps to patch numbers).
  • COMMENTS: Additional details, such as patch descriptions or error messages.

Relevance in Oracle EBS 12.1.1 and 12.2.2

In Oracle EBS, the database is tightly integrated with the application tier. The REGISTRY$HISTORY table helps:
  • Validate Patch Compliance: Ensures database patches align with EBS requirements (e.g., mandatory CPU patches for security).
  • Troubleshoot Issues: Correlates database changes with application failures (e.g., a patch causing performance degradation in EBS modules).
  • Support Upgrades: Tracks dependencies during EBS upgrades (e.g., 12.1.1 to 12.2.2) where database updates are prerequisite.

Example Use Case

During an EBS 12.2.2 upgrade, DBAs query SYS.REGISTRY$HISTORY to verify that all required database patches (e.g., DATABASE PATCH SET UPDATE 12.1.0.2.0) are applied before proceeding with the application tier upgrade. Missing patches can cause upgrade failures or functional gaps.

Access and Maintenance

Only users with SYS privileges (or SELECT_CATALOG_ROLE) can query this table. Oracle automatically maintains it during patch/upgrade operations, but manual cleanup is discouraged to preserve audit integrity.

Conclusion

The SYS.REGISTRY$HISTORY table is a vital tool for DBAs and EBS administrators to ensure database stability, compliance, and alignment with EBS requirements. Its historical data is indispensable for root-cause analysis, upgrade planning, and maintaining a secure, performant EBS environment.