So far, my experience with 6.1.2 has not been very promising. Shortly after upgrading my 6.1.1.1 test server to 6.1.2, it issued these error message:
8/12/2009 2:00:53 PM ANR0101E bfdedup.c(7965): Error 11 opening table "BF.Dereferenced.Chunks". 8/12/2009 2:01:01 PM ANR0130E dbieval.c(825): Server LOG space exhausted. 8/12/2009 2:01:01 PM ANR0106E admattrm.c(389): Unexpected error 5 fetching row in table "Global.Attributes". 8/12/2009 2:01:01 PM ANR9999D_2049388560 admCheckServerDate(admstart.c:3263) Thread<92>: admCheckServerDate: RC 41 managing attribute LAST_NOTED_DATE (triedInsert False). 8/12/2009 2:01:01 PM ANR9999D Thread<92> issued message 9999 from: 8/12/2009 2:01:01 PM ANR9999D Thread<92> 0x0000000000bee072 OutDiagToCons+0x0x142 8/12/2009 2:01:01 PM ANR9999D Thread<92> 0x0000000000bf0bf4 outDiagfExt+0x0x194 8/12/2009 2:01:01 PM ANR9999D Thread<92> 0x000000000051d104 admCheckServerDate+0x0x564 8/12/2009 2:01:01 PM ANR9999D Thread<92> 0x000000000051d2c5 AdmServerMonitorThread+0x0x115 8/12/2009 2:01:01 PM ANR9999D Thread<92> 0x0000000000c5df0b StartThread+0x0x7b 8/12/2009 2:01:01 PM ANR9999D Thread<92> 0x000000336b206367 *UNKNOWN* 8/12/2009 2:01:01 PM ANR9999D Thread<92> 0x000000336a6d30ad *UNKNOWN* 8/12/2009 2:01:01 PM ANR9999D_1426152102 AdmServerMonitorThread(admstart.c:3869) Thread<92>: An error was encountered in checking the system date. 8/12/2009 2:01:01 PM ANR9999D Thread<92> issued message 9999 from: 8/12/2009 2:01:01 PM ANR9999D Thread<92> 0x0000000000bee072 OutDiagToCons+0x0x142 8/12/2009 2:01:01 PM ANR9999D Thread<92> 0x0000000000bf0bf4 outDiagfExt+0x0x194 8/12/2009 2:01:01 PM ANR9999D Thread<92> 0x000000000051d321 AdmServerMonitorThread+0x0x171 8/12/2009 2:01:01 PM ANR9999D Thread<92> 0x0000000000c5df0b StartThread+0x0x7b 8/12/2009 2:01:01 PM ANR9999D Thread<92> 0x000000336b206367 *UNKNOWN* 8/12/2009 2:01:01 PM ANR9999D Thread<92> 0x000000336a6d30ad *UNKNOWN* 8/12/2009 2:01:04 PM ANR0130E dbieval.c(825): Server LOG space exhausted. 8/12/2009 2:01:04 PM ANR0106E bfshred.c(3854): Unexpected error 5 fetching row in table "BF.Shred.Bitfiles". 8/12/2009 2:01:04 PM ANR0101E bfdedup.c(7965): Error 11 opening table "BF.Dereferenced.Chunks". 8/12/2009 2:01:15 PM ANR0101E bfdedup.c(7965): Error 11 opening table "BF.Dereferenced.Chunks". 8/12/2009 2:01:27 PM ANR0101E bfdedup.c(7965): Error 11 opening table "BF.Dereferenced.Chunks". Then it started repeatedly spewing the last error message, over and over and over until it went down. 8/12/2009 3:18:57 PM ANR0101E bfdedup.c(8437): Error 11 opening table "BF.Queued.Chunks". 8/12/2009 3:18:57 PM ANR0171I dbieval.c(812): Error detected on 0:8, database in evaluation mode. 8/12/2009 3:18:58 PM ANR0101E bfdedup.c(8437): Error 11 opening table "BF.Queued.Chunks". 8/12/2009 3:18:58 PM ANR0171I dbieval.c(812): Error detected on 0:8, database in evaluation mode. 8/12/2009 3:18:59 PM ANR0101E bfdedup.c(8437): Error 11 opening table "BF.Queued.Chunks". 8/12/2009 3:18:59 PM ANR0171I dbieval.c(812): Error detected on 0:8, database in evaluation mode. 8/12/2009 3:19:01 PM ANR0101E bfdedup.c(8437): Error 11 opening table "BF.Queued.Chunks". 8/12/2009 3:19:01 PM ANR0171I dbieval.c(812): Error detected on 0:8, database in evaluation mode. 8/12/2009 3:19:02 PM ANR0101E bfdedup.c(8437): Error 11 opening table "BF.Queued.Chunks". 8/12/2009 3:19:02 PM ANR0171I dbieval.c(812): Error detected on 0:8, database in evaluation mode. 8/12/2009 3:19:03 PM ANR0101E bfdedup.c(8437): Error 11 opening table "BF.Queued.Chunks". 8/12/2009 3:19:03 PM ANR0171I dbieval.c(812): Error detected on 0:8, database in evaluation mode. 8/12/2009 3:19:05 PM ANR0101E bfdedup.c(8437): Error 11 opening table "BF.Queued.Chunks". 8/12/2009 3:19:05 PM ANR0171I dbieval.c(812): Error detected on 0:8, database in evaluation mode. 8/12/2009 3:19:06 PM ANR0101E bfdedup.c(8437): Error 11 opening table "BF.Queued.Chunks". 8/12/2009 3:19:06 PM ANR0171I dbieval.c(812): Error detected on 0:8, database in evaluation mode. 8/12/2009 3:19:06 PM ANR0101E bfdedup.c(7965): Error 11 opening table "BF.Dereferenced.Chunks". I ran at least 2-full DB backups before I had to kill it and restart it. I don't know why the logs keep filling up. This server is doing absolutely nothing except for 3-full DB backups, daily. Is there something I should have done for/after the upgrade to 6.1.2? I ran through the standard installation process without any problems. From: Colin Dawson <[email protected]> To: [email protected] Date: 08/12/2009 12:09 PM Subject: Re: [ADSM-L] V6.1.2.0 server has arrived Sent by: "ADSM: Dist Stor Manager" <[email protected]> Hi All, The README's for server fix-pack 6.1.2.0 are delayed by a few days... We expect they will be available on Friday 8/14. Thanks, Colin ----------------------------------------------------- Colin Dawson TSM Server Development [email protected] From: Zoltan Forray/AC/VCU <[email protected]> To: [email protected] Date: 08/12/2009 06:48 AM Subject: Re: [ADSM-L] V6.1.2.0 server has arrived Sent by: "ADSM: Dist Stor Manager" <[email protected]> Yeah, some readme's would be nice. I guess they will get around to posting the page, soon. I just installed it and the README.html file that appears points to pages that don't exist. From: Timothy Hughes <[email protected]> To: [email protected] Date: 08/12/2009 07:53 AM Subject: Re: [ADSM-L] V6.1.2.0 server has arrived Sent by: "ADSM: Dist Stor Manager" <[email protected]> Are Backup Sets enabled? I can't find any readme information regards Zoltan Forray/AC/VCU wrote: >In case folks haven't noticed................... > >Look under the "Maintenance" folder on the FTP site >service.boulder.ibm.com, i.e. >/storage/tivoli-storage-management/maintenance/server/v6r1/Linux/6.1.2.0 > >Here's hoping we can finally start to use V6.1 as a production server. > >
