Re: ORA-1034 ORACLE not available

From: David Sidwell <dasidwel_at_us.oracle.com>
Date: 1995/05/19
Message-ID: <dasidwel-1905951810570001_at_dasidwel-mac.us.oracle.com>#1/1


In article <3pg1bh$pdh_at_booz.bah.com>, Paul Teague <teague_paul> wrote:

> Check and make sure that the user you are logging in as has all of
> the correct oracle environment variables set correctly.
> It sounds like one of the following is not set or is set incorrectly.
> ORACLE_HOME <has to point to the home directory of user oracle>
> ORACLE_SID <has to be set to the SID Identifier for the running database>
> Good lunk.
> --
> Paul Teague Systems Engineer/Unix Admin/Oracle DBA
> E-mail: pteague_at_.bah.com
> #include <Standard disclaimer> "All opinions voiced are my own, etc..."

Paul,

     The clue was that Wolfgang had stated "all files in $ORACLE_HOME have permission 644 or 755". Without the setuid bit on the oracle executable, the non-oracle users would not have access to the SGA shared memory region.
The "ORA-7320: smsget: shmat error when trying to attach sga." error implies that the segment does not exist or that the user does not have permission to access it. The lack of permission is further indicated by the following system error message:
"AT&T .... Error:13:permission denied"

Had the ORACLE_HOME environment variable not been set then the client tool would not have been able to locate the message files to display the message text.
Had the ORACLE_SID environment variable not been set then Wolfgang would have received an "ORA-2700 osnoraenv: error translating ORACLE_SID".

However, in conclusion, incorrect permissions on the oracle executable (i.e. no setuid bit), invalid or missing values for the ORACLE_HOME or ORACLE_SID environment variables, or even the fact that the database is unavailable can result in the ORA-1034 error. Received on Fri May 19 1995 - 00:00:00 CEST

Original text of this message