Data Guard / Far Sync Best Practice - control protection levels
I have just came across a meta parameter called DB_ULTRA_SAFE that sets the values for all of mentioned parameters in Far Sync Best Practice Recommendations (for Oracle 12.1).
When DB_ULTRA_SAFE=DATA_ONLY
• DB_BLOCK_CHECKING => MEDIUM.
• DB_LOST_WRITE_PROTECT => TYPICAL.
• DB_BLOCK_CHECKSUM => FULL.
When DB_ULTRA_SAFE=DATA_AND_INDEX
• DB_BLOCK_CHECKING => FULL.
• DB_LOST_WRITE_PROTECT => TYPICAL.
• DB_BLOCK_CHECKSUM => FULL.
When DB_ULTRA_SAFE=OFF
• When any of DB_BLOCK_CHECKING, DB_BLOCK_CHECKSUM, or DB_LOST_WRITE_PROTECT are explicitly set, no changes are made.
When DB_ULTRA_SAFE=DATA_ONLY
• DB_BLOCK_CHECKING => MEDIUM.
• DB_LOST_WRITE_PROTECT => TYPICAL.
• DB_BLOCK_CHECKSUM => FULL.
When DB_ULTRA_SAFE=DATA_AND_INDEX
• DB_BLOCK_CHECKING => FULL.
• DB_LOST_WRITE_PROTECT => TYPICAL.
• DB_BLOCK_CHECKSUM => FULL.
When DB_ULTRA_SAFE=OFF
• When any of DB_BLOCK_CHECKING, DB_BLOCK_CHECKSUM, or DB_LOST_WRITE_PROTECT are explicitly set, no changes are made.
Comments
Post a Comment