Hi
Check by q option if you have all reorg related options enabled (in 6.3.5
some are disabled by default).
Then if they are on you can simply track progress of reorg process by
checking actlog for those messages:
ANR0293I,ANR0294I – table reorg status reorg
ANR0317I,ANR0318I – index reorg status reorg
ANR0336I,ANR0337I – db2 runstats process status
e.g.
q act msg="0293" begind=-15 endd=today
and so on...
Then, after each reorg, you will get some free pages which you can realse
to system by db2 alter tablespace reduce commands.
Good luck.
Krzysztof
2015-11-18 13:32 GMT+01:00 Rhodes, Richard L. <rrhodes AT firstenergycorp DOT
com>:
> Thanks!
>
> What is weird is that there doesn't seem to be anything to release.
> TSM is reporting that it has only 12,944 free blocks.
>
> After deleting 12% of the files (65m) and expiration completing,
> we were expecting the free blocks to be in the millions.
>
> I don't need the space back, I just want to know that TSM/DB2
> will reuse the space. Instead, overall db size just keeps
> increasing!!! As you can see below, the db keeps
> growing some number of MB per day.
>
> (from a q db)
> tsm FileSysMB UsedMB FreeMB date
> tsm8 1126400 700615 425785 201501
> tsm8 1126400 700709 425691 201502
> tsm8 1126400 701544 424856 201503
> tsm8 1126400 701675 424725 201504
> tsm8 1126400 701669 424731 201505
> tsm8 1126400 701669 424731 201506
> tsm8 1126400 701669 424731 201507
> tsm8 1126400 701676 424724 201508 <= 65m files gone
> tsm8 1126400 701678 424722 201509
> tsm8 1126400 701678 424722 201510
> tsm8 1126400 701742 424658 201511
> tsm8 1126400 701804 424596 201512
> tsm8 1126400 701797 424603 201513
> tsm8 1126400 701797 424603 201514
> tsm8 1126400 702151 424249 201515
> tsm8 1126400 702149 424251 201516
> tsm8 1126400 702185 424215 201517
> tsm8 1126400 702248 424152 201518
>
> (from occupancy)
> date #FilesInDb DbGB
> 11/01/2015 504786214 701785
> 11/08/2015 436723183 701676 <= -65m files gone!
> 11/17/2015 436456172 702185
>
>
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Loon, EJ van (ITOPT3) - KLM
> Sent: Tuesday, November 17, 2015 11:00 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Does a DB2 db ever shrink?
>
> Hi Rick!
> Here is the procedure to release space to the operating system on a 6.3
> server:
>
> http://www-01.ibm.com/support/docview.wss?uid=swg21452146#Release_spaceDB297
> Kind regards,
> Eric van Loon
> AF/KLM Storage Engineering
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Rhodes, Richard L.
> Sent: dinsdag 17 november 2015 16:55
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Does a DB2 db ever shrink?
>
> Hi,
>
> On one of our TSM v6.3.5 databases we deleted two nodes which totaled 65m
> files. After doing this we haven't seen any shrinkage in the database size.
>
> date #FilesInDb DbGB
> 11/01/2015 504786214 701785
> 11/08/2015 436723183 701676 <= -65m files gone!
> 11/17/2015 436456172 702185
>
> The free db2 blocks (today) is 12,944.
>
> By deleting the two nodes we dropped the number files by 65m files. But
> the database itself hasn't changed in size (filesystem size) or free blocks
> inside the db. The db2 is set to auto-reorg (the default).
>
> Q) Why wouldn't our db2 db shrink, or, have gobs of free db2 blocks?
>
>
> Thanks
>
> Rick
>
>
> -----------------------------------------
>
> The information contained in this message is intended only for the
> personal and confidential use of the recipient(s) named above. If the
> reader of this message is not the intended recipient or an agent
> responsible for delivering it to the intended recipient, you are hereby
> notified that you have received this document in error and that any review,
> dissemination, distribution, or copying of this message is strictly
> prohibited. If you have received this communication in error, please notify
> us immediately, and delete the original message.
> ********************************************************
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee only. If
> you are not the addressee, you are notified that no part of the e-mail or
> any attachment may be disclosed, copied or distributed, and that any other
> action related to this e-mail or attachment is strictly prohibited, and may
> be unlawful. If you have received this e-mail by error, please notify the
> sender immediately by return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
> ********************************************************
>
>
>
> -----------------------------------------
>
> The information contained in this message is intended only for the
> personal and confidential use of the recipient(s) named above. If the
> reader of this message is not the intended recipient or an agent
> responsible for delivering it to the intended recipient, you are hereby
> notified that you have received this document in error and that any review,
> dissemination, distribution, or copying of this message is strictly
> prohibited. If you have received this communication in error, please notify
> us immediately, and delete the original message.
>
|
