Chinaunix首页 | 论坛 | 博客
  • 博客访问: 2152918
  • 博文数量: 157
  • 博客积分: 10047
  • 博客等级: 上将
  • 技术积分: 6757
  • 用 户 组: 普通用户
  • 注册时间: 2005-05-19 11:38
文章分类

全部博文(157)

文章存档

2011年(16)

2010年(50)

2009年(42)

2008年(49)

我的朋友

分类: Oracle

2009-07-13 13:21:08

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. . 
阅读(1854) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~