Configuring Run As account credentials for an Oracle database

You must configure Run As account credentials that are used to perform data protection operations on Oracle databases.

Before you begin

If you set up Run As credentials for individual resource groups and the user name does not have full admin privileges, the user name must at least have resource group and backup privileges.

About this task

If you have enabled an Oracle database authentication, a red lock icon is shown in the resources view. You must configure database Run As credentials to be able to protect the database or add it to the resource group to perform data protection operations.

Note: If you specify incorrect credentials while creating a Run As account, an error message is displayed. You must click Cancel, and then retry.

Steps

In the left navigation pane, click Resources, and then select the appropriate plug-in from the list.
In the Resources page, select Database from the View list.
Click , and select the host name and the database type to filter the resources. You can then click to close the filter pane.
Select the database, and then click Database Settings > Configure Database.
In the Configure database settings section, from the Use existing Run As drop-down list, select the Run As account that should be used to perform data protection jobs on the Oracle database.
You can also create a Run As credential by clicking .
Note: The database port number is automatically populated.
In the Configure ASM settings section, from the Use existing Run As drop-down list, select the Run As account that should be used to perform data protection jobs on the ASM instance.
You can also create a Run As credential by clicking .
Note: The ASM instance port number is automatically populated.
In the Configure RMAN catalog settings section, from the Use existing Run As drop-down list, select the Run As account that should be used to perform data protection jobs on the Oracle Recovery Manager (RMAN) catalog database.
You can also create a Run As credential by clicking .

In the TNSName field, enter the Transparent Network Substrate (TNS) file name that will be used by the SnapCenter Server to communicate with the database.
In the Preferred RAC Nodes field, specify the Real Application Cluster (RAC) nodes preferred for backup.
The preferred nodes might be one or all cluster nodes where the RAC database instances are present. The backup operation is triggered only on these preferred nodes in the order of preference.

In RAC One Node, only one node is listed in the preferred nodes, and this preferred node is the node where the database is currently hosted.
After failover or relocation of RAC One Node database, refreshing of resources in the SnapCenter Resources page will remove the host from the Preferred RAC Nodes list where the database was earlier hosted. The RAC node where the database is relocated will be listed in RAC Nodes and will need to be manually configured as the preferred RAC node.
Click OK.