Short of having access to CMVC and traces, I doubt I could say exactly why.
But when a person adds 9GB(8G + 1G) to a database and it still has problems,
I wouldn't be a happy camper.  I'm sure someone in San Jose SSD can explain
this one.  It's a runaway malloc() or fopen()/fprintf()!

Sure, it's more than reasonable to say you need more space.  But that's what
ADSM is there for, to take up space...:-)

ADSML

ADSM + AIX = "Add some aches"
              (ADSM)   (AIX)

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Richard Sims
> Sent: Sunday, August 29, 1999 7:11 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Space reqs on LOADDB
>
>
> >Looks like there's some kind of problem with either the LOADDB mechanism
> >or the structural integrity of the ADSM DB you're reloading.
> >
> >I'd attempt and EXPORT SERVER command of all data to have a clean
> >preservation
> >of what's in the ADSM DB.  DBBackups could work, but the structure could
> >prevent those from restoring properly.  Also chekc the following...
>
> Please don't guess.  Check the archives, at www.adsm.org, wherein the
> December 1, 1998 posting by developer David Bohm describes why a LOADDB
> takes more space.
>     Richard Sims, BU
>