Tuesday, October 9, 2007

Trobleshooting

We applied the CPU Patch in 2 node RAC cluster (10.2.0.2, Linux As3.0). DBA used sqlplus to bring up the instances. We started the monitoring and found out that the monitoring is alerting the below messages:

ORA-01034: ORACLE not available
ORA-27123: unable to attach to shared memory segment
Linux Error: 22: Invalid argument
Additional information: 1
Additional information: 1081344

All the instances were up. After 30-40 minutes analysis we found the workaround to resolve this issue.

I believe that there is an unknown bug with sqlplus vs. svrctl -. I am sharing the workaround we used to resolve the issue.


Here is what happened when we used sqlplus:

SQL> startup
ORACLE instance started.

Total System Global Area 599785472 bytes
Fixed Size 1262200 bytes
Variable Size 205524360 bytes
Database Buffers 385875968 bytes
Redo Buffers 7122944 bytes
Database mounted.
Database opened.
[oracle@bev2 oracle]$ sqlplus system/xxxx@nep1

SQL*Plus: Release 10.2.0.2.0 - Production on Sat Jun 2 16:05:36 2007

Copyright (c) 1982, 2005, Oracle. All Rights Reserved.

ERROR:
ORA-01034: ORACLE not available
ORA-27123: unable to attach to shared memory segment
Linux Error: 22: Invalid argument
Additional information: 1
Additional information: 1081344


Our workaround:

I used srvctl to bring up the instances and found that everything is fine. We checked the tns connections and it went successful.

oracle@bev1 oracle]$ srvctl start instance -d nep -i nep1 -o open

[oracle@bev2 oracle]$ sqlplus system/xxx@nep1

SQL*Plus: Release 10.2.0.2.0 - Production on Sat Jun 2 16:10:47 2007

Copyright (c) 1982, 2005, Oracle. All Rights Reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options

SQL>

No comments: