Oracle Database / Accounts, Security & Access
ORA-01034: verify the intended instance rather than assuming total outage
Oracle not available can mean a stopped instance or a client pointing at the wrong local instance context. Correlate it with the complete error stack.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
printenv ORACLE_SID ORACLE_HOMERead the result
In the database host's Linux shell, these show the terminal's selected local instance and home. They do not prove the database is stopped or identify the service manager's state.
Resolve and verify
Compare the values with the approved inventory and managed instance status. Have the DBA start or repair the intended instance only after understanding why it is unavailable.
Operational precautions
Do not launch a second instance or issue startup against guessed environment values.