28 GB database, AIX 4.3.3, TSM Server 4.2.1.9: UNLOADDB took about 9 hours, LOADDB took about 3 hours. Database shrunk by 30%.
-----Original Message----- From: Christo Heuer [mailto:[EMAIL PROTECTED]] Sent: Monday, January 21, 2002 4:16 AM To: [EMAIL PROTECTED] Subject: Re: How long does a UNLOADDB take??? Hi Niklas, Our OS/390 4.1 Tsm server (38Gig DB), took about two hours to unload but we cancelled the loaddb after about 26 hours. Not too sure why the unload took 2 hours (171 million entries unloaded) - I expected the loaddb to also be in that region. Reverted to restoring the db to the backup we took just before we started the unloaddb process. Decided to give this a miss - silently hoping we'll move to AIX instead. Cheers Christo ============================================================================ ========== Hello We tried to do a unloaddb this weekend to reorganise our database. It ran fine for 2 hours but then it seemed to stop after 157 million entries. ANR4013I UNLOADDB: Dumped 157654872 database entries (cumulative). But after this nothing happens, we could see I/O activity in MVS for the task. After 6 hours we cancelled the job. I've read on the ADSM list about unload times over 20 hours, is this a normal time? q db Available Assigned Maximum Maximum Page Total Used Pct Max. Space Capacity Extension Reduction Size Usable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util ---------------------------------------------------------------------------- ------------------------------------------------------- 44,868 44,868 0 6,216 4,096 11,486,208 9,737,492 84.8 84.8 TSM 4.2.0 running on OS/390 MVH Niklas Lundstr�m F�reningssparbanken IT 08-5859 5164 ______________________________________________ "The information contained in this communication is confidential and may be legally privileged. It is intended solely for the use of the individual or entity to whom it is addressed and others authorised to receive it. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking action in reliance of the contents of this information is strictly prohibited and may be unlawful. Absa is neither liable for the proper, complete transmission of the information contained in this communication, any delay in its receipt or that the mail is virus-free." --------------------------------------- The information contained in this e-mail message, and any attachment thereto, is confidential and may not be disclosed without our express permission. If you are not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution or copying of this message, or any attachment thereto, in whole or in part, is strictly prohibited. If you have received this message in error, please immediately notify us by telephone, fax or e-mail and delete the message and all of its attachments. Thank you. Every effort is made to keep our network free from viruses. You should, however, review this e-mail message, as well as any attachment thereto, for viruses. We take no responsibility and have no liability for any computer virus which may be transferred via this e-mail message.
