Re: DUMPDB tablespace
1998-06-02 20:01:45
Hi Dave,
Believe it or not, you have a small database; our largest DB is 21GB and
93% utilised (we are about to throw another 8GB at it). There have been
comments on this in the past that a LOADDB will take approximately 7
times the DUMPDB time. With a 1.8GB database I would expect the DUMPDB
to not take any more than 3-4 hours so a DUMPDB followed by a LOADDB
might take around 24-30 hours.
Trevor
------------------------------------------------------------------------
------------------------------------------------
------------------------------------------------
Trevor Foley
Trevor Foley
Bankers Trust Australia Limited
Phone: 61-2-9259 3944 Fax: 61-2-9259 2659
-----Original Message-----
From: Sanders, David [SMTP:DSanders AT INTERNAL.MASSMUTUAL DOT COM]
Sent: Wednesday, June 03, 1998 4:33 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: DUMPDB tablespace
Currently I have a MVS-server based DB that is "mildly" broken.
There
is an indication that a table "AS.Volume.Assignment" can't have
a row
deleted. ANR1040E message.
The suggestion is to do a "DUMPDB" with the table parm to
restrict the
unload of that table only, and then reload back. With a 1.8G
DB, I have
a concern that this may take a -LONG- time?? Since this is V2,
we know
that the potential for 2-3 days doing the full DUMPDB, LOADDB
and
AUDITDB is there. I can then assume that doing only the table
is less
than 3 days?? Yikes, not very comforting!!!!
Has anyone done this and could you estimate a time for me?
Also, if I
start to do the table dump, can I cancel non-destructively or am
I
committed?? Thanks
Dave Sanders
Sr. Technical Consultant
DSanders AT massmutual DOT com
1295 State St, E060, Springfield, MA 01111
413-744-5095
MassMutual / The Blue Chip Company
|
|
|