Thanks for the heads up. We don't do dedup so that should not be an issue
for us. Some of our databases are way bigger than yours (>300GB). We will
keep an eye out for high DB activity.

-------------
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html
On Oct 30, 2013 2:36 PM, "Colwell, William F." <bcolwell AT draper DOT com> 
wrote:

> Hi Zoltan,
>
> when I went to 6.3.4.0 from 6.3.somewhere-lower, an index reorg started in
> all my servers.
> The reorg was of a big table involved in dedup.  It caused the active log
> to fill up and all the servers crashed more than once.
>
> I opened a pmr;  IBM was aware of the problem, see
> http://www-01.ibm.com/support/docview.wss?uid=swg1IC91190
>
> To fix it, I had to max out the active log at 128GB, and stop all the
> other big
> log generators like expiration, reclaim, migration, id dup.  Then the
> reorg had
> enough log to finish.
>
> When it was all done, there was a side benefit.  These indexes had gotten
> really big.
> After the reorg there was a lot of freespace in the db.  For example -
>
> tsm: xxxx>q db f=d
>
>                     Database Name: TSMDB1
> ...
>                       Total Pages: 49,053,700
>                      Usable Pages: 49,053,500
>                        Used Pages: 22,947,116
>                        Free Pages: 26,106,384
>
> Good luck!
>
> Bill Colwell
> Draper Lab
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Zoltan Forray
> Sent: Wednesday, October 30, 2013 10:30 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: V6.2.5 to V6.3.4.200 Linux Server Upgrade
>
> Just checking for any issues/gotchas in performing these upgrades.  I want
> to get all my servers up to the latest.
>
> From what I found in books online, this should be a simple 1-upload and
> install base 6.3.4 (from Passport), 2-install 6.3.4.200 patch,
>  3-re-activate licenses.    None of the mess of upgrading from 6.1 to 6.3.
>  Of course, I will backup the DB, devconfig, volhist.
>
> Am I missing anything?  Anyone else do this on Linux?  Any war-stories?
>
> --
> *Zoltan Forray*
> TSM Software & Hardware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html
>