Last updated on MAY 18, 2017
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 12.1 to 12.2]
Information in this document applies to any platform.
On an upgraded Grid Infrastructure environment(184.108.40.206) from 220.127.116.11 or newly installed cluster in 18.104.22.168, the output of “ocrconfig –showbackuploc” command truncates the last sub directory. For example, the OCR backups are stored in /u01/app/22.214.171.124/grid/cdata/dba-cl3:
But, we see this truncated output with a missing last subdirectory (dba-cl3, in this case):
The Oracle Cluster Registry backup location is [/u01/app/126.96.36.199/grid/cdata/]
While,on one 12.1 cluster, when we set the OCR backup location manually, we see the FULL path:
ocrconfig -backuploc /u01/app/188.8.131.52/grid/cdata/DBA-CL1
The Oracle Cluster Registry backup location is [/u01/app/184.108.40.206/grid/cdata/DBA-CL1]
The output from “ocrconfig –showbackuploc” is not consistent.
But at the same time,ocrconfig –local -showbackuploc’ shows the FULL (correct) path of the OLR backup location everywhere, for example:
ocrconfig -local -showbackuploc
The Oracle Local Registry backup location is [/u01/app/220.127.116.11/grid/cdata/btdu21]
Basically, on all the grid infrastructure (new or upgraded) shows OCR backup location truncated, except for the one on which we run “orconfig –backuploc”; this one shows a full path.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms