OracleInstance & database
Applied patches (datapatch history)
Release updates and one-off patches applied through datapatch, newest first. Confirms the SQL side of a patch actually ran.
Not yet verified. How scripts are tested
1CLEAR COLUMNS2SET LINESIZE 180 PAGESIZE 100 TRIMOUT ON TAB OFF3COLUMN patch_id HEADING "PATCH" FORMAT 99999999994COLUMN action FORMAT A105COLUMN status FORMAT A106COLUMN applied FORMAT A167COLUMN description FORMAT A70 TRUNCATE8 9SELECT patch_id, action, status,10 TO_CHAR(action_time, 'YYYY-MM-DD HH24:MI') AS applied,11 description12FROM dba_registry_sqlpatch13ORDER BY action_time DESC;Save it as ora-patches.sql and run it with SQL> @ora-patches.
Part of these runbooks
More Oracle scripts: Instance & database
- Instance status on every nodeHost, instance, version, status, whether logins are allowed, startup time and archiver state for every instance. A quick RAC-wide check after a…
- Working with the spfileShows which spfile the instance is using, where parameter files live and the order Oracle searches for them, and what SCOPE = MEMORY, SPFILE and BOTH…
- Database and instance overviewOne row per instance: host, version, uptime, role, open mode, archive log mode and whether it's a CDB. The first thing to run when you land on an…
- Non-default initialization parametersEvery parameter that has been changed from its default. Handy for comparing two databases or documenting a build.
- Processes and sessions against their limitsCurrent and peak usage of processes, sessions and transactions since startup. A PEAK % near 100 means the next connection storm will hit ORA-00020.
- Installed components and their statusEverything in DBA_REGISTRY. Anything not VALID after a patch or upgrade needs attention before you hand the database back.