Skip to content

Using RMAN Catalog in Data Guard Architecture (4/4) - Configure RMAN

  • by
Using RMAN Catalog in Data Guard Architecture (3/4) - After a Switchover
You can register only once with the same DBID and see both the primary and standby databases are managed under the catalog. For the same reason, you can configure RMAN just only once under the catalog and see both databases are resynchronized and applied with the same configuration.
  1. Show the original RMAN configuration.
  2. [oracle@primary01 ~]$ rman catalog catowner/password@smalldb target sys/password@primdb1
    ...
    connected to target database: COMPDB (DBID=841830157)
    connected to recovery catalog database

    RMAN> show all;

    RMAN configuration parameters for database with db_unique_name PRIMDB are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    ...

    Our goal is to modify RETENTION POLICY. The above setting is the default one.
  3. Modify RMAN configuration and show all.
  4. RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 32 DAYS;

    new RMAN configuration parameters:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 32 DAYS;
    new RMAN configuration parameters are successfully stored
    starting full resync of recovery catalog
    full resync complete

    RMAN> show all;

    RMAN configuration parameters for database with db_unique_name PRIMDB are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 32 DAYS;
    ...

    You have noticed that we have changed RETENTION POLICY to recovery window of 32 days.
  5. Show configuration before the catalog resynchronizes with the standby database.
  6. [oracle@standby01 ~]$ rman target /
    ...
    connected to target database: COMPDB (DBID=841830157, not open)

    RMAN> show all;

    using target database control file instead of recovery catalog
    RMAN configuration parameters for database with db_unique_name STANDB are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    ...

    Since the catalog have not resynchronized with the standby database, RETENTION POLICY is still the default setting.
  7. Resynchronize with the standby database and show configuration.
  8. [oracle@primary01 ~]$ rman catalog catowner/password@smalldb target sys/password@standb1
    ...
    connected to target database: COMPDB (DBID=841830157, not open)
    connected to recovery catalog database

    RMAN> show all;

    RMAN configuration parameters for database with db_unique_name STANDB are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 32 DAYS;
    ...

    New configuration is resynchronized with the catalog.
  9. Show configuration after the catalog resynchronizes with the standby database.
  10. [oracle@standby01 ~]$ rman target /
    ...
    connected to target database: COMPDB (DBID=841830157, not open)

    RMAN> show all;

    RMAN configuration parameters for database with db_unique_name STANDB are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 32 DAYS;
    ...

    Now, RMAN configuration is resynchronized and reposited in the controlfile of the standby database.

Go Back to Overview Page -Using RMAN Catalog in Data Guard Architecture (0/4) - An Overview

Leave a Reply

Your email address will not be published.