I went thru the same process a few months back.  For a 6.2 GB ADSM
database on 3090-500J running MVS/ESA 4.3, the partial database reload
as described in APAR II08975 took about 7 hours to complete.  The reload
does give you progress messages but they're not very predictable or
consistent so you can't go by that.

Tim Pittson
tpittson AT himail.hcc DOT com

>----------
>From:  David Ong[SMTP:david AT BABYONG.NSC DOT COM]
>Sent:  Thursday, September 26, 1996 1:55 PM
>To:    Multiple recipients of list ADSM-L
>Subject:       Re: (Fwd) Reduction of Database
>
>Hi,
>
>I will be doing a DUMP DB & LOAD DB this weekend as documented in APAR
>II08975
>to fix database problems encountered after migrating from version 1 to
>version
>2. My database is approx. 2gb. Based on your experience, am I looking at
>about
>20 hours also to reload the db? Can you please let me know what platform your
>server is running on and also if there were any other complications that
>causes
>your reload to take 20 hours? Does the reload give any progress indication
>such
>as xxxx pages loaded?
>