Mark,

I have been working on exactly this issue, and have been in contact with
IBM.  Apparently, the DUMPDB process decompresses the data base records and
LOADDB does not compress then when they are loaded.  I ran several tests
with small data bases (100,000) objects and had consistent results of 10X
expansion of data.

Looking at your output, it looks like your case isn't quite that bad.  You
dumped 12404627 records, then loaded 8978241 into 1892 Mb.  So you need to
extend the database to (12404627/8978241)*1892 Mb, which is approximately
2614 Mb.  You were using 87.9% of 1544 Mb, so the expansion is around 92%
or 2X.

Since this operation does take hours, I would suggest a couple hundred
extra Mb.

Good Luck!

Ajax Dempsey


At 12:52 PM 10/30/98 -0800, Mapes, Mark wrote:
>Hello,
>
>I am trying to move my ADSM Server from one box, a rs/6000 570 to a 59h, via
>the DUMPDB/LOADDB DSMSERV utilities.
>The software is AIX 4.2.1 with the latest fixes for Y2k.  ADSM is 3.1.2.
>Currently, on the 570 I have a database as reported by the "q db" command as
>follows:
>
>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
>--------- -------- --------- --------- ------- --------- --------- -----
>-----
>    2,016    1,544       472       184   4,096   395,264   347,369  87.9
>87.9
>
>The output of the DUMPDB command is as follows:
>
>ANR4031I DUMPDB: Copied 335671 database pages.
>ANR4033I DUMPDB: Copied 6 bit vectors.
>ANR4034I DUMPDB: Encountered 0 bad database pages.
>ANR4036I DUMPDB: Copied 12404627 database entries.
>ANR4037I DUMPDB: 806 Megabytes   copied.
>ANR4001I DUMPDB: Database dump process completed.
>
>The output of the DSMSERV LOADDB command at startup states:
>
>ANR0900I Processing options file /usr/lpp/adsmserv/bin/dsmserv.opt.
>ANR0990I ADSM server restart-recovery in progress.
>ANR0200I Recovery log assigned capacity is 196 megabytes.
>ANR0201I Database assigned capacity is 1852 megabytes.
>ANR0306I Recovery log volume mount in progress.
>ANR0353I Recovery log analysis pass in progress.
>ANR0354I Recovery log redo pass in progress.
>ANR0355I Recovery log undo pass in progress.
>ANR0352I Transaction recovery complete.
>ANR4003I LOADDB: Database load process started.
>
>
>But, after several hours it abends with the following messages:
>
>ANR4039I LOADDB: Loaded 8976000 database entries (cumulative).
>ANR4039I LOADDB: Loaded 8977000 database entries (cumulative).
>ANR4039I LOADDB: Loaded 8978000 database entries (cumulative).
>ANR4019E : Load processing failed - insufficient database space.
>ANR4020E LOADDB: Batch database insert failed.
>ANR1364I Input volume DSMDB3 closed.
>ANR8468I 8MM volume DSMDB3 dismounted from drive 8MMDR (/dev/mt0) in library
>8MMLIB.
>ANR4032I LOADDB: Copied 233824 database records.
>ANR4033I LOADDB: Copied 6 bit vectors.
>ANR4035I LOADDB: Encountered 0 bad database records.
>ANR4036I LOADDB: Copied 8978241 database entries.
>ANR4037I LOADDB: 559 Megabytes   copied.
>ANR4005I LOADDB: Database load process terminated due to error (-5).
>
>
>It seems to me that I should have plenty of space.  Am I wrong?  Can anybody
>out there fix this?  Help!  Please!!!
>
>Mark Mapes
>PG&E
>
>