Active Statistics Guard

Earlier versions of standby databases have limitations as they can be used either for a recovery purpose or for a read-only purpose without recovery. From 11gR1 onwards, introduced more features, and standby databases can now work in recovery even in an open status. While recovery is in progress, real-time data can be accessible to the users just as production data is. Real time query can be used if Active Data Guard option has been purchased. Apart from that, some additional benefits of Active Data Guard are as follows:

·         You can use applications on Active Data Guard and the additional processing from the production can be reduced so that both primary and standby databases can be utilized.

Using a snapshot standby folder

The snapshot concept was introduced from the Version, which allows the use of a physical standby database in the read-write mode for a short period of time. You can convert a physical standby to a snapshot standby by using either traditional Plus or using the Data Guard broker and grid control at any time. Even if you convert it to a snapshot standby, it will still receive data continuously from the production database archive, so that in the next conversion from a snapshot to a physical standby it will be used for recovery. In case you have performed recovery at any point in time, the new incarnation will be started. Even though a new incarnation has started, the snapshot standby database will still continue accepting redo from the primary database. If your standby database is clustered and has more than one node, then shut down all the auxiliary RAC instances of the standby prior to performing a snapshot. Note that you should not put a standby database in the snapshot mode for a long time; it results

Time for action – Active Data Guard with PeopleSoft

PeopleSoft with Active Data Guard require DB links because they will update the processes' tables using DB links so that remote synonyms are required to give access to the standby system. But a very detailed analysis is required if you consider implementing Active Data Guard. Perform the following steps to implement Active Data Guard with PeopleSoft:

1.     Create a standby database and enable Active Data Guard.

2.     Add a new database service for accessing Active Data Guard on the primary database in case there is any maintenance on the standby server.

3.     Confirm that Oracle Net Services is configured between the Active Guard database and the application servers; also ensure that the Oracle net configuration points to the database service instead of a specific instance and includes both the primary and standby listeners, so that PeopleSoft can connect to any of the services that are not started or running also.