Thursday, April 17, 2008

OCRCONFIG -export/import

oracle:oinstall or oracle:dba is the owner of the ocr disks.

#>ocrconfig -showbackup

node131     2008/04/17 16:22:14     /mnt/app/oracle/crs/cdata/crs

node131     2008/04/17 12:22:13     /mnt/app/oracle/crs/cdata/crs

hpoce131     2008/04/17 08:22:13     /mnt/app/oracle/crs/cdata/crs

node131     2008/04/16 05:09:37     /mnt/app/oracle/crs/cdata/crs

node132     2008/04/10 01:18:40     /mnt/app/oracle/crs/cdata/crs

In addition to using the automatically created OCR backup files, you should also export the OCR contents before and after making significant configuration changes. Do this by using the ocrconfig -export command. This enables you to restore the OCR if your configuration changes cause errors. For example, if you have unresolvable configuration problems, or if you are unable to restart your clusterware, restore your configuration using platform-specific procedures.

#>ocrconfig -export ocr_original
#>ls ocr*
ocr_backup            ocr_original <<         ocrdump_xxx.xml
ocr_backup_2          ocrdump_123           ocrdump_text


For each node:

crs_stop -c node123


#>crsctl stop crs -- from any of the nodes


ocrconfig -import ocr_original <<

No comments:

Post a Comment