Oracle 11g Database shutdown causes the crsd process of 10g Database to restart

Oracle 11g Database shutdown causes the crsd process of 10g Database to restart

The customer has an Oracle 10 Gb RAC environment. Due to an occasional demand, a database of 11 GB needs to be temporarily started. When we mount the software and datafile volumes of 11 GB, the database of 11 GB can be started normally, but when the database of 11 GB is shut down, the crsd process of 10 Gb is restarted.

In the 10 Gb crsd log, you can see:

11:35:35. 827: [OCRAPI] [267] procr_open_key: Invalid keyname [CRS. CUR.]. Component too big.
2011-10-16 11:35:35. 827: [CRSOCR] [267] OCR api procr_open_key failed for key CRS. CUR .. OCR error code = 8 OCR error msg: PROC-8: Cannot perform cluster registry operation because one of the parameters is invalid.
11:35:35. 828: [CRSOCR] [267] [PANIC] Failed to open key: CRS. CUR. (File: caaocr. cpp, line: 358)
11:35:35. 828: [CRSD] [267] [PANIC] CRSD Exiting. OCR Failed
11:35:35. 828: [CRSD] [267] Done.

The problem is not very serious. After 2 minutes, crsd automatically restarts and returns to normal. During this period, the external services of the database are not affected.

Cause:

This is caused by Bug: 13263017-11GR2 database shutdown causing the 10G CRS TO PANIC
 
From 11.2 onwards, database is designed to talk to local CRSD to reset y its state changes. This change is incompatible with 10g CRSD causing the 10g CRSD to panic.

Solution:

The bug has not been fixed yet, but the workaround is available:
Set "_ policy_crs = FALSE" in pfile or spfile for 11gR2 database and restart the instance.
 
This shoshould avoid pre-11gR2 CRSD panic.

Reference: 11gR2 Single Instance Database Shutdown Cause Pre-11gR2 CRSD Panic (Doc ID 1491095.1)