Loading...

Configuring an Oracle ASM Instance

Configure an Oracle ASM instance.

Before You Begin

  • Configure an ASM instance on the CommCell Console in addition to an RDBMS instance.
  • Make sure that the kfed utility is located in the <Oracle ASM Home>/bin directory. If the kfed utility does not exist, then build the kfed utility:

    cd <Oracle ASM Home>/rdbms/lib
    make –f ins_rdbms.mk ikfed

  • Ensure that the ASM disk string is not empty.

    Note: If the ASM disk string is empty, the snapshot backup operations may fail. The default value is a NULL string, which allows the ASM instance to discover all the disks in the operating system's default path to which the ASM instance has read and write access.

  • Discover the Oracle instance

Procedure

  1. From the CommCell Browser, expand Client Computers > client.
  2. Right-click Oracle, point to All Tasks and then click New Instance (ORACLE SID).

    The Creating New Instance dialog box appears.

  3. On the General tab:
    1. In the Instance (ORACLE SID) box, enter the instance name.
    2. In the User Account box, enter the login credentials to access the Oracle client.
    3. In the ORACLE HOME box, enter the Oracle application install path.
    4. In the Storage Policy used for the data of default subclient list, select a storage policy name.
  4. On the Details tab, determine how you want to connect to Oracle.

    Option

    Configuration

    Oracle Wallet Auto Login

    You can use this option when you have configured the Secure External Password Store (Oracle Wallet) feature that stores password credentials, and you want to use those credentials during the data protection operations. For more information on the Secure External Password Store, go to the Oracle documentation website, Secure External Password Store.

    1. Select the Oracle Wallet Auto Login check box.
    2. Enter the Oracle Service Name in the Connect String third box.

      Note: If you provide the user name and password, the software ignores the Oracle Wallet feature.

    Use the Oracle Connect String

    Enter the Connect String to connect to the Oracle database.

    1. Enter the database user name in the Connect String first box.
    2. Enter the database user password in the Connect String second box.
    3. In the Confirm Password dialog box, re-enter the password, and click OK.
    4. Enter the Oracle service name in the Connect String third box.

      For example, in the following:

      sysdba/<password>@orcl

      sysdba is the database user id

      <password> is the database user id password

      orcl is the Oracle service name

    Use the Oracle Catalog Connect String

    Select the Use Connect String check box and in the Connect String box enter the Oracle connect string credentials.

    Note: If you want to use an account other than 'sys', you must grant the SYSDBA or SYSBACKUP (in Oracle version 12 or higher) privilege to the user account.

    Enter the Catalog Connect String to connect to the Oracle database.

    1. Enter the database user name in the Connect String first box.
    2. Enter the database user password in the Connect String second box.
    3. In the Confirm Password dialog box, re-enter the password, and click OK.
    4. Enter the Oracle service name in the Connect String third box.

      For example, in the following:

      sysdba/<password>@orcl

      sysdba is the database user id

      <password> is the database user id password

      orcl is the Oracle service name

  5. In the Automatic Backup of Control Files list, select Configure On to include the control file in all backups for this instance.

    Note: You can override this option to have the feature on the subclient level. For more information, see Enabling Automatic Backups of the Oracle Control File at the Subclient Level.

  6. Select the Disable Backup Aging check box to disable the Oracle CROSSCHECK and, then click OK to close the warning message.
  7. On the Storage Device tab, enter storage policy information:
    • In the Storage Policy used for user command backup of data list, select a storage policy.
    • In the Storage Policy used for all Archive Log backups list, select a storage policy name.
  8. Click OK to close the Creating New Instance dialog box.
  9. On the Oracle database host, edit the oratab file and add an entry for the added instance.

What to Do Next

  1. Create a corresponding RDBMS instance for the Oracle client.

    You can create subclients for the regular RDBMS instance and perform IntelliSnap backup jobs. When you create the subclient for IntelliSnap operations, you must manually refresh the database. The software automatically selects and makes the Use RMAN for backup copy option on the subclient unavailable.

  2. If the ASM disks are from a persistent snap engine, then you need to disable the snap integrity. For more information, see Disabling Verification of Datafiles during IntelliSnap Backup.

Last modified: 8/2/2019 1:44:43 PM