Database Jobs Fails With Error "ORA-27101: Shared Memory Realm Does Not Exist" [ID 413552.1]
Information in this document applies to any platform.
Enterprise Manager Grid Control - Version: 10.2.0.1 to 11.1.0.1 - Release: 10.2 to 11.1
***Checked for relevance on 22-Jan-2012***
Also /etc/oratab file is fine and therefore
NOTE:404503.1 Getting "ORA-01034" while running Grid Control Job
is not applicable in this case.
SQL>show parameter name
NAME TYPE VALUE
--------------- ------ ------------------------
db_name string abc
instance_name string abc.xyz.com
sqlnet.ora
---------
# SQLNET.ORA Network Configuration File: /u01/app/oracle/product/9.2.0/network/admin/sqlnet.ora
# Generated by Oracle configuration tools.
NAMES.DEFAULT_DOMAIN = xyz.com
NAMES.DIRECTORY_PATH= (TNSNAMES)
SQL>shutdown immediate;
SQL>startup;
Running the same job now finishes successfully.
Applies to:
Enterprise Manager Base Platform - Version: 10.2.0.1 to 11.1.0.1 - Release: 10.2 to 11.1Information in this document applies to any platform.
Enterprise Manager Grid Control - Version: 10.2.0.1 to 11.1.0.1 - Release: 10.2 to 11.1
***Checked for relevance on 22-Jan-2012***
Symptoms
Scheduling jobs from Grid Control generates the following error :ORA-01034: ORACLE not availableNo problem with the network setup ( /etc/hosts file and nslookup is fine )
ORA-27101: shared memory realm does not exist
HP-UX Error: 2: No such file or directory
Also /etc/oratab file is fine and therefore
NOTE:404503.1 Getting "ORA-01034" while running Grid Control Job
is not applicable in this case.
Changes
Cause
The database name and the instance name are differentSQL>show parameter name
NAME TYPE VALUE
--------------- ------ ------------------------
db_name string abc
instance_name string abc.xyz.com
sqlnet.ora
---------
# SQLNET.ORA Network Configuration File: /u01/app/oracle/product/9.2.0/network/admin/sqlnet.ora
# Generated by Oracle configuration tools.
NAMES.DEFAULT_DOMAIN = xyz.com
NAMES.DIRECTORY_PATH= (TNSNAMES)
Solution
1. SQL>alter system set instance_name=<db_name> scope=spfile;SQL>shutdown immediate;
SQL>startup;
Running the same job now finishes successfully.
No comments:
Post a Comment