Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

PowerProtect Data Manager 19.12 Oracle RMAN User Guide

PDF

Enable the use of an existing asset in a modified environment

When the Oracle environment is modified, you can follow the procedures in this topic to continue using an existing asset from an existing protection policy with PowerProtect Data Manager.

When you change the SID of the stand-alone database or the database name of the RAC database of an Oracle asset, the asset is treated as a new Oracle asset. If the asset is not automatically added to the protection policy using a protection rule, you must modify the protection policy. However, you have the option to continue to protect the original Oracle asset, even after changing the SID of the stand-alone database or the database name of the RAC database.

You can continue using an existing asset that was configured in the current version of PowerProtect Data Manager even after changing the SID of the stand-alone database or the database name of the RAC database. To continue using the existing asset, you must provide the previous SID of the stand-alone database or the database name of the RAC database in a configuration file, as described in the following procedures.

Enable the use of an existing asset when the SID is changed

For example, the DBID of the database is 1630741966, and the SID will be changed from orcl1 (previous SID) to orcl2 (new SID).

Complete the following steps to enable the continued use of the existing asset when the SID is changed:

  1. Before you change the SID value, specify the new SID value in the parameter setting EXCLUDE_SID=<new_SID> in the configuration file $RMAN_AGENT_HOME/config/rman_agent.cfg.

    For example, add the following parameter setting in the configuration file:

    EXCLUDE_SID=orcl2

  2. Create a new configuration file, $RMAN_AGENT_HOME/settings/rename.config, which will contain the current DBID and both previous and new SID values.

  3. Edit the rename.config file, and add the following two lines in the file:

    [<DBID>:<new_SID>]

    PREVIOUS_SID=<previous_SID>

    For example:

    [1630741966:orcl2]

    PREVIOUS_SID=orcl1

  4. Set the rename.config file access permissions to 666, as with the following command: 

    chmod 666 rename.config
  5. Ensure that the SID value of the database is changed to the new value.
  6. Delete the parameter setting EXCLUDE_SID=<new_SID> in the configuration file $RMAN_AGENT_HOME/config/rman_agent.cfg.

Enable the use of an existing asset when the database name is changed

For example, the DBID of the database is 1630741966, and the database name will be changed from orcl1 (previous database name) to orcl2 (new database name).

Complete the following steps to enable the continued use of the existing asset when the database name is changed:

  1. Before you change the database name, specify the SID of the database in the parameter setting EXCLUDE_SID=<SID_value> in the configuration file $RMAN_AGENT_HOME/config/rman_agent.cfg on all nodes in the RAC environment.

  2. Create a new configuration file, $RMAN_AGENT_HOME/settings/rename.config, which will contain the current DBID and both previous and new database names.

  3. Edit the rename.config file, and add the following two lines in the file:

    [<DBID>:<new_database_name>]

    PREVIOUS_DBNAME=<previous_database_name>

    For example:

    [1630741966:orcl2]

    PREVIOUS_DBNAME=orcl1

  4. Set the rename.config file access permissions to 666, as with the following command: 

    chmod 666 rename.config
  5. Ensure that the database name is changed to the new name.
  6. Delete the parameter setting EXCLUDE_SID=<SID_value> in the configuration file $RMAN_AGENT_HOME/config/rman_agent.cfg on all nodes in the RAC environment.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\