DBA Registry SQL Patch – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™. Oracle EBS module: Database Administration · all Database Administration reports
Overview
DBA_REGISTRY_SQLPATCH contains information about the SQL patches that have been installed in the database. A SQL patch is a patch that contains SQL scripts which need to be run after OPatch completes. DBA_REGISTRY_SQLPATCH is updated by the datapatch utility. Each row contains information about an installation attempt (apply or roll back) for a given patch.
Run this report in Excel in seconds: download Blitz Report™ free (your first 30 reports are free) or try it in the online demo.
Report Parameters
Applied within x Days, Date From, Date To
Oracle EBS Tables Used
Report Categories
Related Reports
DBA Registry, AR Customer Upload, AR Customers and Sites, AP Supplier Upload, AP Suppliers, DBA SGA+PGA Memory Configuration, DBA Object Access Privileges
Running This SQL Without Blitz Report
The SQL source can be run in any SQL client. Some Oracle EBS SQL reports in this library use functions from the utility package xxen_util – install it first. Blitz Report™ adds parameters, Excel output with pivots, scheduling and security on top.
Download & Import Options
| Resource | Link |
|---|---|
| Excel Example Output | DBA Registry SQL Patch 22-Dec-2025 084434.xlsx |
| Blitz Report™ XML Import | DBA_Registry_SQL_Patch.xml |
| SQL Source | DBA Registry SQL Patch.sql |
| Full Report on Enginatics | www.enginatics.com/reports/dba-registry-sql-patch/ |
Executive Summary
The DBA Registry SQL Patch report tracks the history of SQL patches applied to the database. In modern Oracle versions (12c+), binary patches (applied via opatch) often require a post-install SQL step (applied via datapatch). This report confirms that the SQL portion of the patch was applied successfully.
Business Challenge
- Patch Verification: “The binary patch is installed, but did the
datapatchutility run successfully?” - Audit Trail: “When was the ‘Release Update 19.18’ applied to this database?”
- Troubleshooting: “Why are we seeing errors related to a patch that was supposed to be fixed?” (Maybe the SQL step failed).
Solution
This report queries DBA_REGISTRY_SQLPATCH.
Key Features:
- Patch ID: The Oracle bug number associated with the patch.
- Action:
APPLYorROLLBACK. - Status:
SUCCESSorWITH ERRORS. - Description: A brief description of what the patch fixes.
Architecture
The report queries DBA_REGISTRY_SQLPATCH.
Key Tables:
DBA_REGISTRY_SQLPATCH: The inventory of SQL patches.
Impact
- Compliance: Proves that security patches have been fully implemented (both binary and SQL).
- Stability: Prevents “half-patched” states where the binaries are new but the data dictionary is old.
- Version Control: Provides a clear timeline of database software changes.
Useful Links
- Blitz Report™ – World’s Fastest Oracle EBS Reporting Tool
- Oracle Discoverer Replacement – Import Worksheets into Blitz Report™
- Oracle EBS Reporting Toolkits by Blitz Report™
- Blitz Report™ FAQ & Community Q&A
- Supply Chain Hub by Blitz Report™
- Blitz Report™ Customer Case Studies
- Oracle EBS Reporting Blog
- Oracle EBS Reporting Resource Centre
© Enginatics GmbH