Subject: Oracle Clusterware Daemon CRSD fails to start showing OCR errors after a reboot
Doc ID: 551478.1 Type: PROBLEM
Modified Date: 15-FEB-2008 Status: PUBLISHED
In this Document
Symptoms
Changes
Cause
Solution
--------------------------------------------------------------------------------
Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.2
This problem can occur on any platform.
Oracle Clusterware
Symptoms
The following are the symptoms of the problem
Fresh install of 10.2.0.1 or an upgrade from 10.1.0.X to 10.2.0.1
On Unix platforms the root.sh will complete successfully and the Clusterware stack will come up. On windows this is seen after the initial setup is completed successfully.
However after a reboot the Clusterware does not come up with the following errors
[ OCRRAW][]propropen:2: could not get name for id
[ OCRRAW][]proprseterror: Error in accessing physical storage [26] Marking context invalid
Subsequent attempts to start the clusterware do not succeed.
Changes
None
Cause
This is caused due to bug 4748946
Solution
Identify available OCR backups using 'ocrconfig -showbackup'
Dump the contents (as privileged user) of all available backups using
'ocrdump -backupfile '
Identify all the backup locations where 'ocrdump' successfully completed
Inspect the contents of the ocrdump output, and identify a suitable backup
Shutdown the CRS stack on all nodes in the cluster
Restore the OCR backup (as privileged user) using
'ocrconfig -restore '
It should be noted that Customers upgrading or installing Oracle Clusterware 10.2.0.1 and applying the 10.2.0.3 patchset or any patchset which has the fix for this bug before installing the RDBMS software will not encounter this problem.
For example consider a customer on 9208 who is planning to upgrade to 10.2.0.4.
If they install Oracle Clusterware 10.2.0.1 base release and apply the 10.2.0.4 patchset before installing the RDBMS software then they will not encounter this bug.
However if they install Oracle Clusterware 10.2.0.1 base release and install the 10.2.0.1 RDBMS release then they may encounter this problem.
--------------------------------------------------------------------------------
Help us improve our service. Please email us your comments for this document. .
阅读(1286) | 评论(0) | 转发(0) |
