Perform a "q stat" and what are these options set at
              Activity Log Retention Period: 7 Day(s)
          Activity Summary Retention Period: 30 Day(s)
this data is kept in the adsm data base and if you are keeping a lot of
activity log that could clutter your DB
Now your current max pct util is 97.1 %  you can use "reset dbmaxu" to reset
that to the current util. which I see is only 22.9 which really has me
wondering ???

and just because an archive job abended, doesn't mean all the data already
archived just goes away so I don't see why your db is only 22.9%
currently...???

I'd reset the maxu and double check the message and make sure it wasn't
something like the log filling and not the DB.

Dwight
> ----------
> From:         Tereza Higa[SMTP:thiga AT GECITS.COM DOT BR]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Tuesday, April 25, 2000 6:08 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Database doubts
>
> I've been trying to make an archive. It has a lot of small files (about
> 3,927,791 files).
> Unfortunately, after 10 hours of archive, the ADSM database (8G) become
> full and the
> archive fail. Anyone knows what I'm doing wrong?
> Thanks a lot,
>
> ADSM V.3.1..40
>
> adsm> q db f=d
>
>           Available Space (MB): 8,108
>         Assigned Capacity (MB): 8,108
>         Maximum Extension (MB): 0
>         Maximum Reduction (MB): 0
>              Page Size (bytes): 4,096
>             Total Usable Pages: 2,075,648
>                     Used Pages: 474,681
>                       Pct Util: 22.9
>                  Max. Pct Util: 97.1
>               Physical Volumes: 5
>              Buffer Pool Pages: 1,536
>          Total Buffer Requests: 8,392,771
>                 Cache Hit Pct.: 93.61
>                Cache Wait Pct.: 0.00
>            Backup in Progress?: No
>     Type of Backup In Progress:
>   Incrementals Since Last Full: 0
> Changed Since Last Backup (MB): 432.95
>             Percentage Changed: 23.35
> Last Complete Backup Date/Time: 04/24/2000 05:00:26
>