Configuring highly available single-instance databases on Linux or UNIX
Before you can back up high availability Oracle single-instance database configurations, you must run the
si_config script and register a corresponding virtual client with the Avamar server.
Steps
Log in as root to any of the Oracle cluster nodes where the single-instance database has been configured.
Change to the
/usr/local/avamar/bin :
Run the
si_config command:
./si_config -d database_name -r resource -p 28004 -h /u01/app/11.2.0/grid -v shared_directory -n "node_names "
where:
database_name is the name of the single-instance database.
resource is the resource which controls the failover of the single-instance database (for example, ora.dbsi1.db).
shared_directory is a shared directory (for example,
/cluster_share/ ).
node_names is a space-separated list of the names of the nodes on which the single-instance database is configured.
Example command line:
./si_config -d DBSI1 -r ora.dbsi1.db -p 28004 -h /u01/app/11.2.0/grid -v /cluster_share/dbsi1 -n "bu-lin-earth bu-lin-mars"
NOTE: Run the
si_config command on one node only.
The script will prompt you for the client name.
Enter the client name or press
Enter to accept the default selection:
Enter the client name for database_name [Client_name ]
If
ssh autologin is not set up for the root user, you will be prompted to enter the root password for each remote node:
root@node_name 's password: Enter the root password for each node when prompted.
This will allow configuration on all other nodes.