Backing Up Oracle - Computing at Cornell
Backing Up Oracle - Computing at Cornell
Backing Up Oracle - Computing at Cornell
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
The value for errorlogname will either be dsierror.log or a p<strong>at</strong>h and<br />
dsierror.log. For UNIX the <strong>Oracle</strong> user performing the backup must have write<br />
access to the directory and p<strong>at</strong>h of the errorlogname.<br />
The ds_dir value corresponds to the DSM_DIR environment variable. For<br />
UNIX this value also determines from which directory the dsm.sys file will be<br />
read. Most TSM install<strong>at</strong>ions have a dsm.sys in the .../tivoli/tsm/ba/bin and<br />
the .../tivoli/tsm/api/bin directories. When m<strong>at</strong>ching the servername value in<br />
the dsm.opt file with the corresponding servername in the dsm.sys, use the<br />
ds_dir value to determine which dsm.sys is being used.<br />
B.1.4 RC 137 authentic<strong>at</strong>ion failure, incorrect password<br />
The following are necessary consider<strong>at</strong>ions for Windows and UNIX systems.<br />
B.1.4.1 Windows<br />
The most common cause is th<strong>at</strong> passwordaccess gener<strong>at</strong>e. is not specified.<br />
Another cause is th<strong>at</strong> you are not specifying the correct password, or your<br />
nodename is wrong. To upd<strong>at</strong>e the password on the TSM server, run the<br />
command upd<strong>at</strong>e node nodename password. Replace nodename and password<br />
with the appropri<strong>at</strong>e values. Use the administr<strong>at</strong>ive client in console mode to<br />
verify which node is trying to access the TSM server.<br />
B.1.4.2 UNIX<br />
The most common cause is th<strong>at</strong> you are not using the correct dsm.opt and<br />
dsm.sys. Use the config trace or the orcagent.log trace to try and isol<strong>at</strong>e the<br />
problem. These files and how to cre<strong>at</strong>e them are discussed elsewhere in this<br />
appendix. You must have passwordaccess prompt specified. Another cause<br />
could be th<strong>at</strong> you are not specifying the correct password, or your nodename<br />
is wrong. To upd<strong>at</strong>e the password on the TSM server, run the command<br />
upd<strong>at</strong>e node nodename password. Replace nodename and password with the<br />
appropri<strong>at</strong>e values. Use the administr<strong>at</strong>ive client in console mode to verify<br />
which node is trying to access the TSM server.<br />
B.2 Things to check on the TSM server<br />
This section covers various things you need tocheck on the TSM server.<br />
B.2.1 Specifying commtimeout in the dsmserv.opt<br />
If an <strong>Oracle</strong> d<strong>at</strong>abase has a lot of empty blocks (d<strong>at</strong>abase has very little<br />
d<strong>at</strong>a), a commtimeout error may be witnessed during the backup. This<br />
commtimeout error will cause the entire <strong>Oracle</strong> backup to fail.<br />
202 <strong>Backing</strong> <strong>Up</strong> <strong>Oracle</strong> using Tivoli Storage Management
Change language