> On a Test-System I testet Disaster Recovery with  ADSM 3.1.2 Server for
> OS/390 Rel 2.4
>
> -The Tests are done with a copy of our production ADSM-DB of 6GB used at
> 65%.
>
> -HW IBM 9672 R24 and HDS 7700E Disks (Raid 5 with cache and everything
> on)
>
> -ADSM can use and uses one whole processor, so CPU is not an impact.
>
> -The Region(MEMORY) is set to 300MB
>
> 1. /DUMPDB took about 30 Minutes. This is ok.
>
> 2. /FORAMT 1 Log 3 DB-Files took 1.5 Minutes. This is ok.
>
> 3. /LOADDB takes hours!!! My first attept was canceled after 8 hours!!
>    T H I S   I S   N O T   O K   A T   A L L!!!

even worse in Heidelberg: we tried to dump and restore our ADSM database
to get out of the TBUNDO096 condition (IX80786). Step 1 and 2 were similar,
step 3 aborted after about 15 hours with the following error messages:

ANR4019E Load processing failed - insufficient database space.
ANR4020E LOADDB: Batch database insert failed.
ANR4037I LOADDB: 2682 Megabytes   copied.

The database was large enough, indeed:

ANR0200I Recovery log assigned capacity is 4292 megabytes.
ANR0201I Database assigned capacity is 12876 megabytes.

We opened PMR50960.

Regards, Rolf

------------------------------------------------------------------------
Rolf Bogus                   email: Rolf.Bogus AT URZ.Uni-Heidelberg DOT DE
Rolf Bogus                   email: Rolf.Bogus AT URZ.Uni-Heidelberg DOT DE
Universitaetsrechenzentrum
Im Neuenheimer Feld 293      phone: +49 (6221) 54 4507
D 69120 Heidelberg           fax:   +49 (6221) 54 5581
---------------------------------------------------------------------------
=========================================================================