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.
orcagent.log<br />
This file is cre<strong>at</strong>ed by specifying DSMO_DEBUG=49 when alloc<strong>at</strong>ing<br />
channels for RMAN commands. This is one of the most useful files to<br />
gener<strong>at</strong>e for troubleshooting purposes. An example of cre<strong>at</strong>ing and<br />
reading this file was given in Section 9.6, “Verify a TDP for <strong>Oracle</strong> for<br />
Windows RMAN backup” on page 133.<br />
readme file<br />
The readme files contain inform<strong>at</strong>ion th<strong>at</strong> has not made it into the product<br />
manual. There is often inform<strong>at</strong>ion in the readme th<strong>at</strong> will help<br />
troubleshoot known problems. The readme files can be found in the<br />
install<strong>at</strong>ion package or in the install directory.<br />
dsoerror.log<br />
This file is only on Windows and is cre<strong>at</strong>ed if <strong>Oracle</strong> encounters a problem<br />
loading the TDP for <strong>Oracle</strong> orasbt.dll file. TDP for <strong>Oracle</strong> backups will not<br />
work if this file is cre<strong>at</strong>ed when starting the <strong>Oracle</strong> d<strong>at</strong>abase service. The<br />
readme for TDP for <strong>Oracle</strong> describes this in gre<strong>at</strong>er detail.<br />
B.5 Inconsistencies between <strong>Oracle</strong> RMAN and TSM<br />
RMAN is utilized to remove backup objects th<strong>at</strong> were saved on the TSM<br />
server with the Tivoli D<strong>at</strong>a Protection for <strong>Oracle</strong>. When performing these<br />
backup deletions, it is very important to ensure th<strong>at</strong> the same environment<br />
variables are used for the deletion as were specified for the backups. If the<br />
same TDP environment variables are not specified, the backup item will be<br />
removed from the RMAN c<strong>at</strong>alog, but will most likely remain on the TSM<br />
server in an active st<strong>at</strong>e. If they backup objects are not marked for deletion on<br />
the TSM server, they will remain in an active st<strong>at</strong>e and will never be expired<br />
and continue to use TSM storage space.<br />
It is very important to verify th<strong>at</strong> the deletion script being used list the<br />
environment variables in the ENV PARMs correctly (including the case<br />
sensitivity of the node name). Also check th<strong>at</strong> the variable for the DSMI_LOG<br />
should only be a directory (the file name will be dsierror.log) and this directory<br />
must exist and have writable rights by the <strong>Oracle</strong> user doing the<br />
backup/deletion. This dsierror.log will possibly contain some error messages<br />
if there was a problem encountered during the deletion process.<br />
Whenever <strong>Oracle</strong> RMAN performs a backup of a d<strong>at</strong>abase or archivelog,<br />
RMAN writes an entry into the controlfile or recovery c<strong>at</strong>alog. This happens<br />
whether you use TDP for <strong>Oracle</strong> or not. RMAN requires this entry for<br />
restores. When TDP for <strong>Oracle</strong> is used, there is an entry for the backup piece<br />
in the TSM server and in RMAN.<br />
Appendix B. Troubleshooting 205
Change language