HOW TO
1. How can you control when an archive log can be deleted in the standby database?
In Oracle 11g, you can control it by using the log_auto_delete initialization parameter.
The log_auto_delete parameter must be coupled with the log_auto_del_retention_target parameter to specify the number of minutes an archive log is maintained until it is purged.
Default is 24 hours. For archivelog retention to be effective, the log_auto_delete parameter must be set to true.
2. In a logical Standby Data Guard configuration, how can you tell the dbms_scheduler to only run jobs in the primary database?
Logical standby now provides support for DBMS_SCHEDULER. It is capable of running jobs in both primary and logical standby databases. You can use the DBMS_SCHEDULER.SET_ATTRIBUTE procedure to set the database_role. You can specify that the jobs can run only when operating in that particular database role.
3. If you have a low-bandwidth WAN network, what can you do to improve the data guard configuration in a GAP detected situation?
It can be enabled using the compression parameter.
Compression becomes enabled only when a gap exists and the standby database needs to catch up to the primary database.
alter system set log_archive_dest_1='SERVICE=DBA11GDR COMPRESSION=ENABLE';
4. If you wanted to upgrade your current 10g physical standby data guard configuration to 11g, can you upgrade the standby to 11g first then upgrade the primary ?
Yes, in Oracle 11g, you can temporarily convert the physical standby database to a logical standby database to perform a rolling upgrade. When you issue the convert command you need to keep the identity: alter database recover logical standby keep identity;