Oracle rman LAN-free to virtual tape timeout issue

2006-11-08 Thread Robben Leaf
The setup: TSM servers are ver 5.3.2.0, running on AIX. The situation in
question involves one TSM server instance that the client backs up to, and
a TSM server instance acting as a library manager for a virtual tape
library.

The client (ver 5.3.2.0) is LAN-free, and doing an rman backup of an Oracle
database. The session starts and is proxied normally to the library
manager, the tape gets mounted, and the catalog compilation starts.

15 minutes and a few seconds later (that's just over 900 seconds) - and
it's always this long, but it's also always the same time each day, 4:15 AM
- the proxied session that's holding the tape drive open gets severed
(ANR0480W) from the TSM backup server. A few minutes later, the catalog
compilation finishes and the client tries to start backing up files, but
can't because there isn't a tape available; the backup fails.

The commtimeout parameter on both of the TSM servers is 16,400 seconds; on
the storage agent it's 14,400. The idletimeout parameter on the servers and
the storage agent is 720 minutes. The throughputtimethreshold on the
storage agent is 270 minutes. There aren't any timeout-type parameters set
in the stanza for this node in the dsm.sys file.

Am I missing some timeout parameter that has a default of 15 minutes? Could
rman be timing something out?

Any ideas?

Robben Leaf


--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==


Re: Oracle rman LAN-free to virtual tape timeout issue

2006-11-08 Thread Mike Hedden
Robben,
Have you looked at RESOURCETIMEOUT?

RESOURCETIMEOUT Specifies how long the server waits for a resource before 
canceling the pending acquisition of a resource. Note: For proper management of 
shared library resources, consider setting the RESOURCETIMEOUT option at the 
same time limit for all servers in a shared configuration. In the case of error 
recovery, Tivoli Storage Manager always defers to the longest time limit.



 From: Robben Leaf [EMAIL PROTECTED]
 Date: 2006/11/08 Wed PM 12:02:10 EST
 To: ADSM-L@VM.MARIST.EDU
 Subject: Oracle rman LAN-free to virtual tape timeout issue

 The setup: TSM servers are ver 5.3.2.0, running on AIX. The situation in
 question involves one TSM server instance that the client backs up to, and
 a TSM server instance acting as a library manager for a virtual tape
 library.

 The client (ver 5.3.2.0) is LAN-free, and doing an rman backup of an Oracle
 database. The session starts and is proxied normally to the library
 manager, the tape gets mounted, and the catalog compilation starts.

 15 minutes and a few seconds later (that's just over 900 seconds) - and
 it's always this long, but it's also always the same time each day, 4:15 AM
 - the proxied session that's holding the tape drive open gets severed
 (ANR0480W) from the TSM backup server. A few minutes later, the catalog
 compilation finishes and the client tries to start backing up files, but
 can't because there isn't a tape available; the backup fails.

 The commtimeout parameter on both of the TSM servers is 16,400 seconds; on
 the storage agent it's 14,400. The idletimeout parameter on the servers and
 the storage agent is 720 minutes. The throughputtimethreshold on the
 storage agent is 270 minutes. There aren't any timeout-type parameters set
 in the stanza for this node in the dsm.sys file.

 Am I missing some timeout parameter that has a default of 15 minutes? Could
 rman be timing something out?

 Any ideas?

 Robben Leaf


 --
 Electronic Privacy Notice. This e-mail, and any attachments, contains 
 information that is, or may be, covered by electronic communications privacy 
 laws, and is also confidential and proprietary in nature. If you are not the 
 intended recipient, please be advised that you are legally prohibited from 
 retaining, using, copying, distributing, or otherwise disclosing this 
 information in any manner. Instead, please reply to the sender that you have 
 received this communication in error, and then immediately delete it. Thank 
 you in advance for your cooperation.
 ==