Printable View
Hai,
I am facing a problem when I am trying to connect to oracle database through a client. It is giving the message as below.
ERROR: ORA-01034: ORACLE not available
ORA-07429: smsgsg: shmget() failed to get segment.
SVR4 Error: 2: No such file or directory
the platform is
os - sun solaris 2.8
oracle - 7.3.4
If any one can help me out in this regard.
Thanks & Regards.,
( assuming your DB is up and running except the client connection problem... )
Check if you set the ORACLE_SID,ORACLE_HOME to the right values and unset the ORACLE_PATH and give a try connecting the database..
dear reddy,
Let me give some more details.
1) The database is in unix environment and the client is windows based.
2) In the same server two databases are existing. One database I am able to connect through the client. Where as one it is giving the error as I mentioned.
3) I have simulated by increasing the shmmax value also.
4) the same set up is available in one more server E450 sun server where both the databases are up and people are able to connect to both the database through their respective clients. I have checked up the oracle parameters at OS level in both the servers. coming to the databases it is the cold backup restoration. I am able to bring up the database and connect to the server through sqlplus.
Now can you tell me still any points I have to check. I tried your method also.
As I said in my previous post , the whole idea is performance
rather faster recovery , so i don't suggest JANE to set FAST_START_IO_TARGET unless he wanted to have a 60 sec. recovery...
And my DB(s) is running on 8.1.7 and and the LOG_CHECKPOINTS_TO_ALERT is set to TRUE and we did not observe any performance issue till now.. This parameter will be observed only at every log switch by ORACLE, just to write entries in Alert.log , So if we have less number of log switches , this parameter ( TRUE value ) will do good..
Malladi,
Pl ignore the previous post ...its post for some other thread.
OK , did you try TNSPING from your client and working fine , and also you may wish to check the tnsname.ora enties for the same server..
Dear Madhu,
I have tried the TNSPING from client. It is OK. But we R not able to connect to database.
I have tried even increasing the SGA and setting the ulimit parameters as per live server. But still it is not getting connected. I have even increased the shared_pool_size in init(sid).ora and tried then also it is not connecting.
regards.,
Please see that the listener services is started in your server.
Also as u said that u are trying to connect to the oracle from cleint please see ur sqlnet entry, where u have meintioned host, sid,port, correctly.
-pravin
Dear Pravin,
As I have already mentioned in my earlier message saying that there are two databases on the same server. I am able to connect to that server through client by changing the sid at tnsnames at the client end.
I have created server level tnsnames.ora for this particular database to simulate any listener problem. I have tried tnsping from server. it is ok. but when I am trying to connect to the database through listener it is giving the error.
Regards.,
can u post that eror message
dear pravin,
the error message is as follows.
ERROR: ORA-01034: ORACLE not available
ORA-07429: smsgsg: shmget() failed to get segment.
SVR4 Error: 2: No such file or directory
the platform is
os - sun solaris 2.8
oracle - 7.3.4
regards.,
Naren,
try to unset the env. variable ORACLE_PATH on client machine and post the tsnnames.ora from the client m/c.
and try setting the ORACLE_HOME and ORACLE_SID from the client and give a try...
dear madhu,
I have unset the oracle_path in the client and set the oracle_sid and oracle_home.
but still it is giving the same error.
regards,
Error: ORA 7429
Text: smsgsg: shmget() failed to get segment.
-------------------------------------------------------------------------------
Cause: a shared memory segment used for all part of the SGA could not be
retrieved.
Action: Use the system error number in the error message to determine why
the segment could not be retrieved. If it does not exists, shutdown
the database using the "abort" option, and then restart it.
If the get failed because the permissions are incorrect, make sure
that the ownership of the oracle executable is the same as that on
the shared memory segment.
*** Important: The notes below are for experienced users - See [NOTE:22080.1]
Explanation:
This is typically reported when a user tries to connect to a
database but either the database is NOT running or the user has
their environment set up incorrectly.
Diagnosis:
- Is the database actually running ?
- Is the connection attempt local or to a remote database ?
Local:
- Check ORACLE_HOME and ORACLE_SID are correct:
env | grep ORACLE
The ORACLE_SID is case sensitive and MUST match the instance
ORACLE_SID.
- Check ORACLE_HOME and the ORACLE_SID thus:
cd $ORACLE_HOME/dbs
ls -l sgadef$ORACLE_SID.*
If the 'cd' fails ORACLE_HOME is incorrect. If the 'ls' shows
no files then either the database is not running OR
ORACLE_SID is wrong.
- Check the Operating System error number after the ORA 7429
message.
Error 2 Is typically wrong ORACLE_SID or ORACLE_HOME
Error 13 Is typically incorrect permissions on the
'oracle' executable. As the Oracle user ensure
the permissions are correct thus:
cd $ORACLE_HOME/bin
chmod 4755 oracle
If the database is started as 'root' and the
permissions are wrong you need to:
Shutdown the database as root
Change the permissions as above
Restart the database
TCP/IP:
- For SQL*Net V1 over TCP/IP ensure that the ORACLE_HOME in
the oratab file (/etc/oratab or /var/opt/oracle/oratab)
is EXACTLY correct for the instance.
- For SQL*Net V2 over TCP/IP ensure that the ORACLE_HOME in
the listener.ora file is EXACTLY correct for the instance.
This file should be in one of:
/etc/listener.ora
$TNS_ADMIN/listener.ora
/var/opt/oracle/listener.ora
or $ORACLE_HOME/network/admin/listener.ora