Sunday, July 9, 2017

Registration of an 11.2 database fails against a 12.1 CRS stack

I encountered a problem while registering an 11gR2(11.2.0.3) standby database against a 12.1 CRS stack home. See the add database command and the failure afterwards.

$ srvctl add database -d prod01 -o /prd/prod01/product/11.2.0/db_1  -p '+PROD01_DATA/prod01/spfileprod01.ora' -r PHYSICAL_STANDBY -s MOUNT -y AUTOMATIC -t IMMEDIATE -a 'PROD01_DATA,PROD01_FRA,PROD01_REDO'

PRCR-1006 : Failed to add resource ora.prod01.db for prod01
PRCD-1184 : Failed to upgrade configuration of database type to version 11.2.0.3.0
PRCR-1071 : Failed to register or update resource type ora.database.type
CRS-0245:  User doesn't have enough privilege to perform the operation


I was surprised to see this problem and luckily there is an MOS support note on this issue that is well documented with a workaround or patch that can be applied.

The workaround to the issue is run the following after setting your environment to the 12.1 CRS home.

$ crsctl modify type ora.database.type -attr  "ATTRIBUTE=TYPE_VERSION,DEFAULT_VALUE=3.2" "-unsupported"
$ crsctl modify type ora.service.type -attr "ATTRIBUTE=TYPE_VERSION,DEFAULT_VALUE=2.2" "-unsupported"


A one-off patch also exists and the fix is included in 11.2.0.3.4 GI PSU onwards.

Patch 13460353: REGISTRATION OF 11.2.0.3 DATABASE FAILS AGAINST 12.1 CRS STACK

No comments:

Post a Comment