Backing Up Oracle - Computing at Cornell

5.1.4 Registering with the TSM server
For our database server, we decided to use different TSM node names. Each
node name is bound by its domain name and policy name to an appropriate
management class.
The nodenames we are using in our dsm.sys file are listed in Table 3.
Table 3. Nodes and servers
Nodename Server name Purpose
sol_e brazil_ba Generic backup/archive clients
sol_oracle sol_oracle TDP for Oracle
sol_db2 brazil-db2 DB2 backups and log archives
See 4.8, “Node considerations” on page 52, for more details about the setup
used.
5.1.5 Initialize the password
TDP for Oracle ships a program, aobpswd, to simulate the TSM function
PASSWORDACCESS=GENERATE. This eliminates the need to enter a
password manually, allowing RMAN to establish a session with the TSM
Server without prompting each time for a password. The aobpswd program
encrypts the TSM password and stores it in a secure file located with the
DSMO_PSWDPATH environment variable. The password is then passed to
the TSM API to the TSM server without user intervention.
To initialize the TDP for Oracle password, perform the following steps as root
user:
1. Export DSMO_NODE=sol_oracle.
2. Export DSMI_CONFIG=/opt/tivoli/tsm/api/bin/dsm.opt.
3. Export DSMI_LOG=$PWD.
4. Set PASSWORDACCESS PROMPT in the options file (dsm.sys).
5. Start the aobpswd program.
a. Enter the current node password.
b. You are prompted for a new password. If you just press the Enter key,
the password will not be changed.
Successful execution of the aobpswd program generates a password file
named TDPO. in your default installation directory.
66 Backing Up Oracle using Tivoli Storage Management