11g ASM Single Instance DBCA error prcr-1006 crs-0259 prcr-1071

11g ASM dbca error prcr-1006 crs-0259 prcr-1071


When creating a single instance DB using ASM mode, it appears when running DBCA
PRCR-1006 : Failed to add resource ora.orcl.db for orcl
PRCR-1071 : Failed to register or update resource ora.orcl.db
PRCR-1001 : Resource ora.orcl.db does not exist


After viewing the DBCA log, I found the following error.

[oracle@dga01 orcl]$ tail -30000 trace.log | grep PRCR

[Thread-138] [ 2013-03-19 14:15:51.520 CST ]
[HASIDBRegistrationStep.executeImpl:253]
 Exception while registering with HAS
PRCR-1006 : Failed to add resource ora.orcl.db for orcl
PRCR-1071 : Failed to register or update resource ora.orcl.db
PRCR-1001 : Resource ora.orcl.db does not exist


Oracle said this is a bug as follows

Bug 11886915 : CRS-0259 WHEN REGISTERING THE DATABASE WITH ORACLE RESTART
 
Bug attribute
 
Type B - Defect has been fixed in the product version
Severity 2 - Severe Loss of Service Product Version 11.2.0.2
Status 33 - Suspended, Req‘d Info not Avail Platform 226 - Linux x86-64
Creation time 2011-3-18 Platform version ORACLE LINUX 5
Updated 2011-10-3 Basic Bug N/A
Database version 11.2.0.2 Impact platform Generic
Product Source Oracle

 
Product Line Oracle Database Products Series Oracle Database
Zone Oracle Database Products 5 - Oracle Database - Enterprise Edition

Hdr: 11886915 11.2.0.2 PCW 11.2.0.2 CRS PRODID-5 PORTID-226
Abstract: CRS-0259 WHEN REGISTERING THE DATABASE WITH ORACLE RESTART
 
*** 03/18/11 07:51 am ***
 
PROBLEM:
--------
Oracle Restart Environment, using separate Database Oracle Homes, each owned
By a different OS user.
 
A database cannot be registered with Oracle Restart when the OS user used to
Install the database software was created after the last restart of the
Oracle Restart Environment.
 
There must be at least 1 database from a different Oracle Home/OS owner
Already registered with the Oracle Restart.
 
The database can be registered only after OHASD is restarted.
 
DIAGNOSTIC ANALYSIS:
--------------------
Srvctl error:
 
PRCR-1006 : Failed to add resource ora.elin.db for null
PRCR-1071 : Failed to register or update resource ora.elin.db
CRS-0259: Owner of the resource does not belong to the group.
 
WORKAROUND:
-----------
After restarting the grid infrastructure the second db can be added.
However, this causes downtime for the already existing databases, which is
Not acceptable by the customer
 
RELATED BUGS:
-------------
Bug 10337212
Bug 10118593
Bug 11063852
 
REPRODUCIBILITY:
----------------
Can be reproduced as follows on CT env:
- install grid infrastructure for single node (oracle restart) 11.2.0.2 using
a separate OS user (grid) on linux 64 bit.
- install the oracle enterprise db software using a separate OS user
(oracle1), create a new db in this Oracle Home and register this db with
Oracle restart (happens automatically when using dbca).
- Install the oracle enterprise db software using a new OS user (os user did
Not exists since the last grid infrastructure restart) and create a new db in
This Oracle Home.
At this point dbca will complain that the db can not be registered with
Oracle restart and further installation (db console) will fail. Manual
Registration attempts using srvctl will also fail.
- Restart the ohas (crsctl stop has / crsctl start has). This will also
Restart all db already registered with Oracle restart
- Manual register the second created database using "srvctl add database"
Will now work.
- When now creating a third Oracle Home using a new OS user, the db
Registration will again fail.
 


The solution is as follows, first restart the has service with the grid user.

[grid@dga01 ~]$ crsctl stop has
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘dga01’
CRS-2673: Attempting to stop ‘ora.LISTENER.lsnr‘ on ‘dga01’
CRS-2673: Attempting to stop ‘ora.DATA.dg‘ on ‘dga01’
CRS-2673: Attempting to stop ‘ora.OCR.dg‘ on ‘dga01’
CRS-2677: Stop of ‘ora.DATA.dg‘ on ‘dga01’ succeeded
CRS-2677: Stop of ‘ora.LISTENER.lsnr’ on ‘dga01’ succeeded
CRS-2677: Stop of ‘ora.OCR.dg‘ on ‘dga01’ succeeded
CRS-2673: Attempting to stop ‘ora.asm‘ on ‘dga01’
CRS-2677: Stop of ‘ora.asm‘ on ‘dga01’ succeeded
CRS-2673: Attempting to stop ‘ora.cssd‘ on ‘dga01’
CRS-2677: Stop of ‘ora.cssd‘ on ‘dga01’ succeeded
CRS-2673: Attempting to stop ‘ora.evmd‘ on ‘dga01’
CRS-2677: Stop of ‘ora.evmd‘ on ‘dga01’ succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘dga01’ has completed
CRS-4133: Oracle High Availability Services has been stopped.

[grid@dga01 ~]$ crsctl start has
CRS-4123: Oracle High Availability Services has been started.


[root@dga01 ~]# su - oracle
Re-register the database with srvctl

[oracle@dga01 ~]$ srvctl add database -d orcl -o /u01/app/oracle/product/11.2/db_1


After executing the above command, dbca is normal.

This article is from the "O Record" blog, so be sure to keep this source http://evils798.blog.51cto.com/8983296/1420948