24.12.2012 Views

Backing Up Oracle - Computing at Cornell

Backing Up Oracle - Computing at Cornell

Backing Up Oracle - Computing at Cornell

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The problem is th<strong>at</strong> during the <strong>Oracle</strong> backup, a session is opened with the<br />

TSM server and the backup transaction is started. After d<strong>at</strong>a th<strong>at</strong> exists in the<br />

<strong>Oracle</strong> file is sent to the TSM server, the backup then goes into a loop<br />

skipping the empty space in the d<strong>at</strong>abase file (Null values). If there is a lot of<br />

empty space, the TSM server can time-out and close the session before<br />

RMAN can give the TDP client any additional d<strong>at</strong>a to send or finish the<br />

transaction.<br />

This issue is normally witnessed if the value for commtimeout on the TSM<br />

server is set to a low value (such as the default of 60 seconds). It is<br />

suggested to set the commtimeout value to 600-1200 seconds when working<br />

with d<strong>at</strong>abase backups. This value is set in the dsmserv.opt file for the TSM<br />

server and requires the TSM server to be restarted to take effect.<br />

COMMTIMEOUT 600<br />

B.2.2 Administr<strong>at</strong>ive client queries<br />

If you are encountering errors, there are some things th<strong>at</strong> you should check<br />

on the TSM server using the administr<strong>at</strong>ive client and the query command.<br />

Run the command query node nodename f=d replacing nodename with the<br />

nodename th<strong>at</strong> is used to back up <strong>Oracle</strong>. The value for Backup Deleted<br />

Allowed should be set to YES. The value for Maximum Mount Points Allowed<br />

should be equal to or less than the number of drives on the TSM server. The<br />

value for Locked? should be set to NO. The value for Policy Domain Name<br />

should be checked to make sure it belongs to the correct domain. This value<br />

determines wh<strong>at</strong> management classes are available to the node for managing<br />

the <strong>Oracle</strong> backups.<br />

Using the value of Policy Domain Name, you can run some queries to see if<br />

the correct management classes for the <strong>Oracle</strong> backups are available. The<br />

command query mgmtclass active will show which is the DEFAULT<br />

management class for the node. The command query copygroup <br />

active will tell you wh<strong>at</strong> the retention settings are for the management<br />

classes.<br />

B.3 Isol<strong>at</strong>ing the problem<br />

When troubleshooting, you must try to isol<strong>at</strong>e the cause of the problem. The<br />

four main areas in which to try to isol<strong>at</strong>e the problem are: <strong>Oracle</strong> RMAN, TDP<br />

for <strong>Oracle</strong>, TSM API, and TSM Server.<br />

Appendix B. Troubleshooting 203

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!