OracleInstance & database

Instance status on every node

Host, instance, version, status, whether logins are allowed, startup time and archiver state for every instance. A quick RAC-wide check after a restart.

Tested on 12c, 19c · verified Sep 2026

1--check status of instance:2CLEAR COLUMNS3SET PAGESIZE 100 TRIMOUT ON TAB OFF4set lines 7005column HOST_NAME format a506select HOST_NAME, instance_name, version, status,logins, to_char(STARTUP_TIME,'MM/DD/YYYY HH24:MI:SS') as STARTUP_TIME, archiver from gv$instance order by instance_name;

Save it as ora-instance-status.sql and run it with SQL> @ora-instance-status.

Open in denrepo

Helps with

• ORA-01033: ORACLE initialization or shutdown in progress
• ORA-01034: ORACLE not available

Part of these runbooks

• Users can't connect

More Oracle scripts: Instance & database

• 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.
• Applied patches (datapatch history)Release updates and one-off patches applied through datapatch, newest first. Confirms the SQL side of a patch actually ran.