Mark,
as others already said, these utilities (DSMSERV UNLOADDB, DUMPDB,
LOADDB and AUDITDB) in fact ARE documented and always have been
(Appendix A in the 3.7 and 4.1, appendix D in the 3.1 admin ref.).
They are poorly documented though, e.g. not saying anything about
the required time, and not
Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail
-Original Message-
From: John Naylor [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 26, 2001 9:18 AM
To: [EMAIL PROTECTED]
Subject: Re: Reducing/compressing the database
Mark,
I agree with you that the bene
MAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSEG)
Subject: Re: Reducing/compressing the database
"Thomas A. La Porte" wrote:
> Is anybody else a little bit distressed that Tivoli's TSM
> administrator needs to seek this advice from the list, rather
> than from the devel
I have to agree.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Mark Stapleton
Sent: Thursday, April 26, 2001 12:19 AM
To: [EMAIL PROTECTED]
Subject: Re: Reducing/compressing the database
"Thomas A. La Porte" wrote:
> Is anybody
"Thomas A. La Porte" wrote:
> Is anybody else a little bit distressed that Tivoli's TSM
> administrator needs to seek this advice from the list, rather
> than from the developers of the product?
I think I've read just about enough whining in this thread about how
Tivoli 'distresses' people by not
. April 2001 08:30
An: [EMAIL PROTECTED]
Betreff: Reducing/compressing the database
TSM v3.7.3
I have read alot on this list about reducing the database because my
situation is pretty bad. We have a 103 gig database that was 97% used! I
finally was permitted to fix the outrageous retention setti
This reminds me of the tech support story where a guy is trying getting
errors on a server he is working on, and the errors say to have the
SysAdmin run a chkdsk/f (yes, it's been a while). He calls the helpdesk,
who tell him, "Have the SysAdmin run chkdsk/f." So he bitches and
complains about h
heheheh, take a look
-Original Message-
From: Thomas A. La Porte [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 23, 2001 3:42 PM
To: [EMAIL PROTECTED]
Subject: Re: Reducing/compressing the database
Is anybody else a little bit distressed that Tivoli's TSM
administrator needs to
> From: Thomas A. La Porte [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 23, 2001 6:42 PM
> Is anybody else a little bit distressed that Tivoli's TSM
> administrator needs to seek this advice from the list, rather
> than from the developers of the product?
No, not really. Tivoli is large enou
Is anybody else a little bit distressed that Tivoli's TSM
administrator needs to seek this advice from the list, rather
than from the developers of the product?
This is an issue that has been one that has generated much
discussion on and off with regards to the benefits and costs of
attempting to
AIL PROTECTED]>@VM.MARIST.EDU> on 04/22/2001 01:30:10 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Reducing/compressing the database
TSM v3.7.
>So, will defragging the database really improve my restore times?
>Seems pointless otherwise.
Shawn - One of those issues... Tivoli provided the barely-documented
unload-reload db reorg procedure, but at the same time has
published no information anywhere about TSM database internals an
TSM v3.7.3
I have read alot on this list about reducing the database because my
situation is pretty bad. We have a 103 gig database that was 97% used! I
finally was permitted to fix the outrageous retention settings, and got it
down to 50% utilization, but the Maximum Reduction value is still 0
13 matches
Mail list logo
