This issue can happen when we try to take backup of oracle database using Phoenix Oracle DTC agent and the backup fails with the message “ERROR at line 1:\nORA-01034: ORACLE, not available\nProcess ID: 0\nSession ID: 0 “
Oracle was not started up. Possible causes include the following:
1. The SGA (System Global Area) requires more space than was allocated for it.
2. The operating-system variable pointing to the instance is improperly defined.
level=error ts=2022-02-19T19:19:55.350126755-05:00 stack="failed to parse results: \nORACLE_BASE=/ora/app/oracle\nORACLE_HOME=/ora/app/oracle/product/126.96.36.199/dbhome\n\nSQL*Plus: Release 188.8.131.52.0 Production on
Sat Feb 19 19:19:54 2022\n\nCopyright (c) 1982, 2014, Oracle. All rights reserved.\n\nConnected to an idle instance.\n\nPHOENIX_ORACLE_AGENT_DTC_SQLPLUS_SCAN_START\nDECLARE\n*\nERROR at line 1:\nORA-01034: ORACLE not available\nProcess ID: 0\nSession ID: 0 Serial number: 0\n\n\nPHOENIX_ORACLE_AGENT_DTC_SQLPLUS_SCAN_END\nDisconnected\n\\ngoroutine 38 [running]:\
- If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly. See the platform specific Oracle documentation.
- The ORA-01034 error can sometimes be fixed by setting the ORACLE_SID environment variable:
- Unix/Linux :
$sqlplus sys/manager@xxx as sysdba
C:\> set ORACLE_SID=xxx
C:\> sqlplus sys/manager@xxx as sysdba
- You may find that you are experiencing ORA-01034 when attempting to upgrade your Oracle database.
- ORA-01034 is thrown during the attempt to upgrade because there is an invalid entry in one of the following files:
- The ORA-01034 is a result of a discrepancy between ORACLE_HOME and ORACLE_SID
- To resolve ORA-01034, be sure that the ORACLE_HOME and ORACLE_SID properly match within the files /etc/oratab or /var/opt/oracle/oratab .
- As a last step in solving your ORA-01034 problem and running DBUA, make sure that ORACLE_HOME is set to 'old' home, not 'new' home.
Note:Please involve DBA to verify the above steps.