3com database adapter module for networker nsr-ora v3.2 User Manual
System Administrator’s Guide
U42252-J-Z915-1-76
Installation and Configuration
Configuration
lation directory). This file contains SQL commands, which are executed each
time sqldba or svrmgrl is called. There should be no SQL commands here which
could lead to error messages of the form (ORA-xxxx) when sqldba or svrmgrl is
called: NSR-ORA would notice these error messages when sqldba or svrmgrl is
called and might draw false conclusions from them about the state of the data-
base.
time sqldba or svrmgrl is called. There should be no SQL commands here which
could lead to error messages of the form (ORA-xxxx) when sqldba or svrmgrl is
called: NSR-ORA would notice these error messages when sqldba or svrmgrl is
called and might draw false conclusions from them about the state of the data-
base.
Please note that with ORACLE Version 9.x the svrmgrl command is no longer
supported. Instead of this NSR-ORA uses the sqldba command by default.
supported. Instead of this NSR-ORA uses the sqldba command by default.
4.3.3
Configuring NSR-ORA
The following steps refer to the NetWorker client on which the ORACLE
database and NSR-ORA are installed. For the first-time configuration of NSR-
ORA or when changing to a more recent version, you can use the interactive
tool configure_nsrora, which is located in the directory $NSR_INST/oracle/config. If
you have several databases (several ORACLE instances) on your computer,
you will have to call configure_nsrora once for each database (for each
ORACLE_SID
database and NSR-ORA are installed. For the first-time configuration of NSR-
ORA or when changing to a more recent version, you can use the interactive
tool configure_nsrora, which is located in the directory $NSR_INST/oracle/config. If
you have several databases (several ORACLE instances) on your computer,
you will have to call configure_nsrora once for each database (for each
ORACLE_SID
).
If you call configure_nsrora after changing to a different version, it will adopt the
settings from the corresponding old files dbo${ORACLE_SID}.init as defaults.
The tablespaces recorded in the directories monday to sunday will also be taken
over and displayed, and the parameters given in the file
shell_variables_for_${ORACLE_SID}
settings from the corresponding old files dbo${ORACLE_SID}.init as defaults.
The tablespaces recorded in the directories monday to sunday will also be taken
over and displayed, and the parameters given in the file
shell_variables_for_${ORACLE_SID}
will be used for the new version.
The tool first asks you for the name of the ORACLE instance (ORACLE_SID), the
owner of the ORACLE software (ORACLE_OWNER), the owner’s group
(ORACLE_GROUP), the path to the ORACLE software (ORACLE_HOME). If
these variables are already defined as shell variables and exported, they will be
offered to the user as the default setting. Then configure_nsrora creates the
configuration directory /nsr/oracle/${ORACLE_SID} as well as the directory
/nsr/oracle/etc
owner of the ORACLE software (ORACLE_OWNER), the owner’s group
(ORACLE_GROUP), the path to the ORACLE software (ORACLE_HOME). If
these variables are already defined as shell variables and exported, they will be
offered to the user as the default setting. Then configure_nsrora creates the
configuration directory /nsr/oracle/${ORACLE_SID} as well as the directory
/nsr/oracle/etc
. If the directory /nsr does not exist on a NetWorker client (this
directory always exists on NetWorker servers) it will be created during instal-
lation. But you can also create /nsr yourself before the installation (e.g. if you
want to use links).
lation. But you can also create /nsr yourself before the installation (e.g. if you
want to use links).
The file all_ORACLE_SIDs is created in the directory /nsr/oracle/etc and the
ORACLE_SID
ORACLE_SID
is saved there. This file will be accessed if the archiving monitor
daemons are automatically started up again following a boot of your NetWorker
client for all ORACLE instances (i.e. for all ORACLE_SIDs).
client for all ORACLE instances (i.e. for all ORACLE_SIDs).