Re: ORACLE Server not available

Thanks a lot for the info. That was exactly the problem.

It turns out that one of our UNIX SYS ADMINS (very green and now very sheepish) was fooling around on the weekend with changing ownerships on files while logged in as root, and managed to reset the owner of everything under $ORACLE_HOME. Obviously not something that you expect to happen, so it took some time to debug.

Stephen Miller
ISM, Montreal
On Mon, 26 May 1997 17:00:18 GMT, steveadams_at_acslink.net.au (Steve Adams) wrote:

>Hi Stephen,
>
>The Unix error indicates that you don't have permission on the shared
>memory segment. This normally indicates that your process is not
>running with the same effective uid as that which was used to start
>the instance, normally the oracle owner. This could happen if for
>some reason you have lost the setuid bits off the oracle executable
>($ORACLE_HOME/bin/oracle).
>
>HTH, Steve Adams
>----------
>On Sun, 25 May 1997 19:01:45 GMT, stepmil_at_ibm.net (Stephen Miller)
>wrote:
>>Environment: UNIX AIX 4.2
>> ORACLE 7.2.3
>>
>>Whenever I attempt to access ORACLE I get the following errors:
>>
>> +---------------------------------------------------------------------+
>> | sqldba mode=line |
>> | |
>> | SQL*DBA: Release 7.2.3.0.0 - Production on Sun May 25 18:38:46 1997 |
>> | |
>> | Copyright (c) Oracle Corporation 1979, 1994. All rights reserved. |
>> | |
>> | Oracle7 Server Release 7.2.3.0.0 - Production Release |
>> | With the distributed and parallel query options |
>> | PL/SQL Release 2.2.3.0.0 - Production |
>> | |
>> | SQLDBA> connect internal |
>> | Connected. |
>> | SQLDBA> shutdown immediate |
>> | DBA-00342: unable to complete internal login |
>> | ORA-01034: ORACLE not available |
>> | ORA-07320: smsget: shmat error when trying to attach sga. |
>> | IBM AIX RISC System/6000 Error: 13: Permission denied |
>> | SQLDBA> |
>> +---------------------------------------------------------------------+
>>
>>It looks like my SGA has somehow gotten corrupted, but I am unable to
>>shutdown the database. Short of a KILLing the processes, how can I bring
>>down and restart this instance? And what is the significance of the UNIX
>>errors?
>>
>>Stephen Miller
>>ISM, Montreal
>>
>
Received on Tue May 27 1997 - 00:00:00 CDT