Re: Data base
Have a look for "temporary" files being generated in a backed-up file
system with distinct machine-generated names eg including timestamps or
process numbers. These may need to be corralled into a different
management class with a reduced retention. Each one will take 600 bytes of
Use Q OCC and look for an unreasonably large number of files as a first
step, then maybe the dsmsched.log for the suspect node.
AIX/ADSM etc etc Guy
The Wesley Hospital, Brisbane Australia
"Gies, Joanne" <joanne.gies AT CONNEXT DOT COM>@VM.MARIST.EDU> on 16/05/2000
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Data base
Have 7020 mb of assigned space on DB. Have used 85% and before I add
volume, does anyone have any ideas why this usage is not decreasing
we are backing up much less, and deleted a ton of filespaces and nodes.
Would extending or reducing DB's help. Can I compress the DB?
This email message has been swept by
MIMESweeper at The Wesley Hospital - Australia