Unable to startup the database after reboot Ora-9968 Ora-1102 on Linux [ID 269223.1]
Applies to:
Oracle Server - Enterprise Edition - Version: 9.0.1.0 to 9.2.0.1 - Release: 9.0.1 to 9.2
Linux x86
Symptoms
Unable to startup the database after reboot. Getting the following error
Connected to an idle instance.
ORACLE instance started.
.
Total System Global Area 577573740 bytes
Fixed Size 451436 bytes
Variable Size 402653184 bytes
Database Buffers 163840000 bytes
Redo Buffers 10629120 bytes
ORA-1102: cannot mount database in EXCLUSIVE mode
And you will see the messages in the alertlog
ALTER DATABASE MOUNT
Wed Oct 22 13:40:29 2003
scumnt: failed to lock /test/oracle/product/920/dbs/lkTEST exclusive
Wed Oct 22 13:40:29 2003
ORA-9968: scumnt: unable to lock file
Linux Error: 11: Resource temporarily unavailable
Additional information: 26165
Wed Oct 22 13:40:29 2003
ORA-1102 signalled during: ALTER DATABASE MOUNT...
Wed Oct 22 13:41:26 2003
Cause
The error caused by the NFS locking issue.
Solution
Workarounds:
1) Use "nolock" NFS mount option (disables locking entirely).
2) Manually clear locks on NetApp filer after every client reboot.
Applies to:
Oracle Server - Enterprise Edition - Version: 9.0.1.0 to 9.2.0.1 - Release: 9.0.1 to 9.2
Linux x86
Symptoms
Unable to startup the database after reboot. Getting the following error
Connected to an idle instance.
ORACLE instance started.
.
Total System Global Area 577573740 bytes
Fixed Size 451436 bytes
Variable Size 402653184 bytes
Database Buffers 163840000 bytes
Redo Buffers 10629120 bytes
ORA-1102: cannot mount database in EXCLUSIVE mode
And you will see the messages in the alertlog
ALTER DATABASE MOUNT
Wed Oct 22 13:40:29 2003
scumnt: failed to lock /test/oracle/product/920/dbs/lkTEST exclusive
Wed Oct 22 13:40:29 2003
ORA-9968: scumnt: unable to lock file
Linux Error: 11: Resource temporarily unavailable
Additional information: 26165
Wed Oct 22 13:40:29 2003
ORA-1102 signalled during: ALTER DATABASE MOUNT...
Wed Oct 22 13:41:26 2003
Cause
The error caused by the NFS locking issue.
Solution
Workarounds:
1) Use "nolock" NFS mount option (disables locking entirely).
(Not recommended, see Note 279393.1)
2) Manually clear locks on NetApp filer after every client reboot.
References
NOTE:279393.1 - Linux/NetApp: RHEL/SUSE Setup Recommendations for NetApp Filer Storage
No comments:
Post a Comment