Backing Up Oracle - Computing at Cornell
Backing Up Oracle - Computing at Cornell
Backing Up Oracle - Computing at Cornell
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
B.4 List of logfiles<br />
A key thing to remember is th<strong>at</strong> TSM is just a storage repository for RMAN<br />
backups. RMAN is responsible for cre<strong>at</strong>ing all the backup objects and the<br />
archivelogs. TDP for <strong>Oracle</strong> is responsible for taking wh<strong>at</strong> RMAN gives and<br />
passing th<strong>at</strong> on to the TSM server. TSM server is responsible for storing the<br />
backup objects and the archivelogs, and then retrieving them when asked. If<br />
RMAN cre<strong>at</strong>es a corrupt backup object or corrupt archivelog, TSM will store it<br />
and retrieve it as corrupt. As TSM is not necessary to do an RMAN backup,<br />
you can elimin<strong>at</strong>e TSM as a problem by cre<strong>at</strong>ing an RMAN backup on a local<br />
file system. If RMAN fails cre<strong>at</strong>ing a backup to disk, then it will probably also<br />
fail using TDP for <strong>Oracle</strong>. In this situ<strong>at</strong>ion, you would then check the <strong>Oracle</strong><br />
setup.<br />
Another useful way to isol<strong>at</strong>e a problem is to compare a failing machine with a<br />
working one. Then you can see wh<strong>at</strong> is the same and wh<strong>at</strong> is different. Are<br />
they using the same API level, TDP for <strong>Oracle</strong> level, <strong>Oracle</strong> level and fixpack,<br />
TSM server? Do the nodes belong to the same domain and have the same<br />
settings? Wh<strong>at</strong> are the client options file differences between the failing and<br />
the working machine?<br />
Try to use as many of the defaults as possible. Using environment variables<br />
when not required increases the likelihood of configur<strong>at</strong>ion errors.<br />
The following is a collection of logfiles from which to get valuable inform<strong>at</strong>ion<br />
for problem determin<strong>at</strong>ion:<br />
dsierror.log<br />
The file reside in the directory specified by the DSMI_LOG environment<br />
variable. It contains the most valuable inform<strong>at</strong>ion for problem<br />
determin<strong>at</strong>ion for our purpose. Each entry may refer to a TSM API error<br />
number. A description of those errors can be found in Appendix D, “API<br />
Return Codes”, in the book: Tivoli Storage Manager: Using the Applic<strong>at</strong>ion<br />
Program Interface, SH26-4123.<br />
dsmsched.log<br />
By default, TSM stores the schedule log inform<strong>at</strong>ion in a file named<br />
dsmsched.log. The default name can be overwritten by specifying the<br />
SCHEDLOGNMAME option in the client option files.<br />
sbtio.log<br />
This file is cre<strong>at</strong>ed by <strong>Oracle</strong> and normally resides in the udump directory<br />
of the d<strong>at</strong>abase instance.<br />
204 <strong>Backing</strong> <strong>Up</strong> <strong>Oracle</strong> using Tivoli Storage Management