We DBAs would have think of it at-least once whenever we come across RAC 11gr2.
Here are my consolidations in this regards.
GPNP failed -
Whenever GPnP profile is not present, it is automatically copied from existing nodes by GPnPd as pending.xml .
Whenever, profile is updated, it is automatically renamed to profile.xml.
profile.xml file is created automatically even if other nodes are down.
OLR failed -
running instance would not be impact but it would unable to start after reboot.
OLR can be import from backup (backup created at installation/upgrade times /or ocrconfig –local –manualbackup taken)
Voting Disk failed -
Node evictions. Can be restore (from automatic backed up OCR or replace with new one as it only has network/disk ping data within).
OCR failed -
cluster resources will not run. can be import from backup.
if accidentally deleted then run deleteroot.sh (All nodes),rootdeinstall.sh (master node), root.sh (master node), add other resources manually.
ASM Disk group/ASM Disk - failed
ASM disk having OCR/Voting disk/ datafiles , database will crash.
in all other cases, database would keep running with non-availability of data for affected data files.
ASM disk group (as its logical entity), Meta data can be restore using md_backup/md_restore.
Whereas ASM disk could be create manually and its data can be restore using RMAN database backup.
Please add your inputs so that it can assist others.
if any queries, kindly feel free to buzz me here.
(Source - internet)
(Note - Purpose is to assemble widely distributed information over internet , at one place in simple language for learning purpose)
Source : Linkedin Article
No comments:
Post a Comment