Manually adding an Oracle database instance to the repository
New instances the instance discovery system finds on the clients are automatically added to the repository. However, you may need to add an instance manually. For example, you do not want to wait for the discovery service to discover the new instance.
Note:
If necessary, contact the Oracle database administrator for the correct set of credentials. The DBA can also manually add the instance if the DBA is not willing or allowed to share the credentials with the backup administrator. The DBA can manually add the instance using the nboraadm command on the client. The Oracle database user is required to have a certain level of credentials. The Oracle database user must have SYSBACKUP or SYSDBA privileges (based on version of Oracle).
To manually add an Oracle database instance to the repository
- In the NetBackup Administration Console, in the left pane, expand NetBackup Management > Applications > Oracle.
- Click All Instances. All instances in the repository are listed in the right pane.
- Right-click All Instances and select New instance to display the following:
- Fill in the Instance Name, Host, and ORACLE_HOME parameters. Click Help to display descriptions of these parameters. For example:
- (Conditional) Use the Override Default TNS_ADMIN Path if you need to override the default network administration directory on the client system. Enter the fully qualified path for the network administration directory on this host. Click Help to display a description of the parameter. Example of the parameter:
- Click Provide Credentials.
- In the Register Instance dialog box, click Use Instance Credentials.
- Enter the OS Credentials. You may have to contact the Oracle DBA for the correct credentials.
- In the Authentication area, you can optionally click Oracle Authentication to enter specific Oracle credentials. You can also click Use Oracle RMAN Recovery Catalog to enter credentials for the RMAN recovery catalog. Then click OK.
The system tries to validate the credentials, report its findings, and return you to the Change Instance dialog box. Validation can fail for the following reasons:
If the host name is invalid, the following message appears
Could not validate credentials. Failed to connect to client: <client> (40).
If the host name is correct but you cannot connect to the host because the host is down, the following message appears:
The validation operation timed out waiting for a respond from the client (46)
If the host name is correct, but username-password is invalid, the following message appears:
Validation of operating system user/password failed for client: <client> (41).
The error message includes the generated status code which appears in parentheses at the end of the message. The following is an example of an error pop-up window:
Click OK to save the credentials, or you can click Cancel and re-enter the credentials. If you save the credentials that caused the error, the instance is saved in the repository. You can edit the instance at a later time to correct the validation issue.
Click OK in the Change Instance dialog box.
You have added the instance to the repository and registered the instance with credentials.
