GI rootupgrade.sh srvctl upgrade model fails: CRS-2532: OCR write failed for 'ora.ioserver.type' (Doc ID 2193674.1)

Last updated on OCTOBER 20, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

Symptoms

Upgrading from 11.2.0.4 to 12.1.0.2, rootupgrade.sh fails on node1:

PRCR-1071 : Failed to register or update resource type ora.chad.type
CRS-2618: Cannot change data type INT of existing attribute CHECK_INTERVAL to type STRING.
CRS-2618: Cannot change data type INT of existing attribute RESTART_ATTEMPTS to type STRING.
CRS-2618: Cannot change data type INT of existing attribute START_TIMEOUT to type STRING.
CRS-2618: Cannot change data type INT of existing attribute STOP_TIMEOUT to type STRING.
CRS-2532: OCR write failed for 'ora.chad.type'

Died at /oraclegrid/product/grid12102/crs/install/crsupgrade.pm line 4119.

root script log

2016-09-17 10:44:32: Got CRS softwareversion for u060easd12a: 12.1.0.2.0
2016-09-17 10:44:32: The software version on u060easd12a is 12.1.0.2.0
2016-09-17 10:44:32: Invoking "/oraclegrid/product/grid12102/bin/srvctl upgrade model -s 11.2.0.4.0 -d 12.1.0.2.0 -p first"
2016-09-17 10:44:32: trace file=/oraclegrid/product/grid12102/cfgtoollogs/crsconfig/srvmcfg2.log
2016-09-17 10:44:32: Executing /oraclegrid/product/grid12102/bin/srvctl upgrade model -s 11.2.0.4.0 -d 12.1.0.2.0 -p first
2016-09-17 10:44:32: Executing cmd: /oraclegrid/product/grid12102/bin/srvctl upgrade model -s 11.2.0.4.0 -d 12.1.0.2.0 -p first
2016-09-17 10:44:49: Command output:
> PRCR-1071 : Failed to register or update resource type ora.ioserver.type
> CRS-2618: Cannot change data type INT of existing attribute CHECK_INTERVAL to type STRING.
> CRS-2618: Cannot change data type INT of existing attribute RESTART_ATTEMPTS to type STRING.
> CRS-2618: Cannot change data type INT of existing attribute START_TIMEOUT to type STRING.
> CRS-2618: Cannot change data type INT of existing attribute STOP_TIMEOUT to type STRING.
> CRS-2532: OCR write failed for 'ora.ioserver.type'
>End Command output

crsd.trc

2016-09-17 10:44:49.064: [ CRSPE][11824]{1:16546:532} Processing PE command id=354. Description: [Register Type : : 117330e50]
2016-09-17 10:44:49.078: [ CRSPE][11824]{1:16546:532} DM flushing its state to repository.ri_seed = 765, config version = 344
2016-09-17 10:44:49.084: [ CRSOCR][11310]{1:16546:532} Multi Write Batch processing...
2016-09-17 10:44:49.229: [ OCRUTL][11310]u_allocm: metactx [116e5650], ptr returned is NULL, size to lmmcalloc [280]
2016-09-17 10:44:49.229: [ OCRUTL][11310]u_allocm: metactx [116e5650], ptr returned is NULL, size to lmmcalloc [280]
2016-09-17 10:44:49.229: [ OCRRAW][11310]prcreatei: could not allocate memory 3
2016-09-17 10:44:49.231: [ OCRRAW][11310]rrecover_helper:3: recovery required for disk[+RAC_DATA,0]
2016-09-17 10:44:49.246: [ OCRAPI][11310]a_batch_execute: Backend batch exec failed [12]
2016-09-17 10:44:49.246: [ OCRAPI][11310]a_batch_execute: Failed to execute batch. Return [12]
2016-09-17 10:44:49.247: [ CRSOCR][11310]{1:16546:532} Multi Write Batch done.
2016-09-17 10:44:49.248: [ CRSD][11824]{1:16546:532} {1:16546:532} Created alert : (:CRSPE00142:) : Failed to register resource ora.ioserver.type
2016-09-17 10:44:49.250: [ CRSPE][11824]{1:16546:532} PE Command [ Register Type : ora.ioserver.type : 117330e50 ] has completed
2016-09-17 10:44:49.250: [ CRSPE][11824]{1:16546:532} UI Command [Register Type : ora.ioserver.type : 117330e50] is replying to sender.
2016-09-17 10:45:01.042: [UiServer][12338] CS(117330e50)set Properties ( oragrid,1173a6270)
2016-09-17 10:45:01.053: [UiServer][12081]{2:34016:23201} Sending message to PE. ctx= 117332670, Client PID: 6750422
2016-09-17 10:45:01.054: [ CRSPE][11824]{2:34016:23201} Processing PE command id=23176. Description: [Stat Resource : 117373ab0]
2016-09-17 10:45:01.056: [ CRSPE][11824]{2:34016:23201} Expression Filter : ((NAME == ora.scan2.vip) AND (LAST_SERVER == u060easd12b))
2016-09-17 10:45:01.069: [UiServer][12081]{2:34016:23201} Done for ctx=117332670

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms