ADSM-L

Re: UNLOAD/RELOAD DB

2003-04-09 09:54:41
Subject: Re: UNLOAD/RELOAD DB
From: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 9 Apr 2003 15:54:02 +0200
Hi Joni!
Please send us the output form the command q db f=d so we can calculate if
your database indeed is heavily fragmented.
I haven't done a unload/load myself but I read some stories in this list: it
can be a rather lengthy process
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines

-----Original Message-----
From: Joni Moyer [mailto:joni.moyer AT HIGHMARK DOT COM]
Sent: Wednesday, April 09, 2003 14:22
To: ADSM-L AT VM.MARIST DOT EDU
Subject: UNLOAD/RELOAD DB


Hello All!

I was talking to TSM support yesterday about several issues concerning
expiration and the tsm database in my environment.  I am on 4.1.5 on os/390
2.10 and I have a db that is 60GB with 83% utilized.  It was suggested to
try to unloaddb and reload it, but I have been receiving mixed
feelings/messages from many users and co-workers.  If anyone has done this
process, what are the pros/cons?   Does this help with DB growth and
performance?  I would appreciate any opinions or suggestions you may have!
Thank you in advance!

Joni Moyer
Systems Programmer
joni.moyer AT highmark DOT com
(717)975-8338


**********************************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
**********************************************************************

<Prev in Thread] Current Thread [Next in Thread>