OracleInstance & database
Installed components and their status
Everything in DBA_REGISTRY. Anything not VALID after a patch or upgrade needs attention before you hand the database back.
Not yet verified. How scripts are tested
1CLEAR COLUMNS2SET LINESIZE 140 PAGESIZE 100 TRIMOUT ON TAB OFF3COLUMN comp_id HEADING "ID" FORMAT A104COLUMN comp_name HEADING "COMPONENT" FORMAT A455COLUMN version FORMAT A156COLUMN status FORMAT A107 8SELECT comp_id, comp_name, version, status9FROM dba_registry10ORDER BY comp_id;Save it as ora-components.sql and run it with SQL> @ora-components.
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.
- Applied patches (datapatch history)Release updates and one-off patches applied through datapatch, newest first. Confirms the SQL side of a patch actually ran.