Changing FRA on Data Guard
edited Jul 7, 2013 8:59PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 3 commentsAnswered
Hi,
We had an issue where the flash recovery area of DG becomes full (+flash) e started raising "archive hung" errors on alert.log of five data guard instances that was configured +flash as db_recovery_file_dest (archive area). To restore DG instances from this issue we changed the FRA of DG instances (there was no rroom to increase the +flash - disk group full) from +flash to +data (where there was enough free space). I didn't find any note saying that it is a wrong practice. All instances are using catalog database to backup archived log files. Anyone could give any comments about
We had an issue where the flash recovery area of DG becomes full (+flash) e started raising "archive hung" errors on alert.log of five data guard instances that was configured +flash as db_recovery_file_dest (archive area). To restore DG instances from this issue we changed the FRA of DG instances (there was no rroom to increase the +flash - disk group full) from +flash to +data (where there was enough free space). I didn't find any note saying that it is a wrong practice. All instances are using catalog database to backup archived log files. Anyone could give any comments about
0