Hi Steve

For system copies, we set commtimeout to 1 hr for every 100 g/b of data base
datafiles.  Dependant on your disk, this may need to be higher.

How long does it taking db2 to create the datafiles?  (The user should be
able to tell you this)
Datafiles (db2 containers) are created in parallel per tablespace, so
creating multiple containers per tablespace and spreading them over max
disks will aid creation performance (and of course general db performance
too)

Unfortunately these containers can not be created during the actual restore
(to my knowledge).  They must exist in advance for db2 to restore the data
into.

We leave the commtimeout set permanently high.  We also set IdleTimeOut to
120

Best regards
Troy Tudor



-----Original Message-----
From: Steve Harris [mailto:Steve_Harris AT HEALTH.QLD.GOV DOT AU]
Sent: 12 May 2003 02:03
To: ADSM-L AT VM.MARIST DOT EDU
Subject: DB2 restore and commtimeout


Hi All,

I recently inherited a SAP/R3 db2 system and merged the old TSM on which it
had been running with my usual TSM instance.
This uses native DB2/TSM interface to do the backup, not the TSM for R3
agent.

The users are trying to clone their production Database using what DB2 terms
a "redirected restore".  DB2 creates a session with TSM which mounts a tape
and a small amount of data is pulled from it.  DB2 then formats the database
containers and finally starts to restore the data.

On the old system commtimeout was set at 30000 seconds.  This meant that the
restore would hold the tape drive - without using it - for the three hours
it needs to format its 300GB of space.  I figured that if I set commtimeout
to something more reasonable, TSM would time out and free the drive and then
re-establish the session and continue when data was actually needed.

I was wrong.  The session times out, DB2 formats the containers and then the
restore fails with a -50 return code - Session lost.

Questions.

Is this normal DB2 behavior?
Is there any DB2 parameter to get around this? - a method of restoring and
formatting at the same time would be nice.
What are the consequences on the rest of the system of setting commtimeout
so high?

AIX 5.1 RML03 on client and server
DB2 is v 7.1.2.60
TSM client is 5.1.5.0
TSM Server is 4.2.3.3

TIA

Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia




**********************************************************************
This e-mail, including any attachments sent with it, is confidential
and for the sole use of the intended recipient(s). This confidentiality
is not waived or lost if you receive it and you are not the intended
recipient(s), or if it is transmitted/ received in error.

Any unauthorised use, alteration, disclosure, distribution or review
of this e-mail is prohibited.  It may be subject to a statutory duty of
confidentiality if it relates to health service matters.

If you are not the intended recipient(s), or if you have received this
e-mail in error, you are asked to immediately notify the sender by
telephone or by return e-mail.  You should also delete this e-mail
message and destroy any hard copies produced.
**********************************************************************