Perhaps this is normal behavior and I'm just ignorant of some aspect of ADSM's internals, but I've discovered something which looks rather odd. What follows is an administrative client session captur
Since ADSM data base behavior has been brought up... take a gander at one of mine! Why do I have 80% free yet only a max reduction of 0.4% I only have 5 nodes registered here and only keep the act lo
If I remember correctly, the reduce command requires the space to be available at the end of the database. Your database could be fragmented (did you used to have lots more data/nodes backed up?) and
Author: "Bushman, Christopher M" <cbushman AT AMP DOT COM>
Date: Tue, 5 Jan 1999 15:16:50 -0500
I believe that there was a post concerning this topic awhile ago. I seem to remember that in order to "reclaim" all that free database space, you need to perform the dsmserv dumpdb and dsmserv loaddb
Author: Dwight Cook [mailto:decook AT AMOCO DOT COM]
Date: Sun, 04 Oct 2015 17:48:51 -0500
Since ADSM data base behavior has been brought up... take a gander at one of mine! Why do I have 80% free yet only a max reduction of 0.4% I only have 5 nodes registered here and only keep the act lo
Fragmentation would explain it. Reduction/expansion are in terms of whole, unused megabytes whereas utilization is measured in measly pages. Richard Sims, BU
Complex ADSM SQL queries do require that the database have 4MB reducible space to run. This space is required for some temporary tables required while performing complex operations. APAR IX76147 was