Multiple Errors in the TSM ACTLOG for TSM DB

[rallingham]

Has anyone seen this type of error showing up in the actlog? I have looked around and found a few things but nothing specific. I just upgraded a small shop to TSMV6.2.3 and I see the following errors almost all day long:

03/05/2014 08:38:03 ANR0162W Supplemental database diagnostic information:
-2219: :2 (54534d4442312e44465f4d49475242495446494c4-
553ff32).
03/05/2014 08:38:03 ANR9999D_0485338544 DoReorg(tbreorg.c:2760) Thread<36>:
Reorg(TblResume )(flags 0x100000) for
"TSMDB1"."DF_MIGRBITFILES" failed with result code -2219.
03/05/2014 08:38:03 ANR9999D Thread<36> issued message 9999 from:
03/05/2014 08:43:03 ANR0162W Supplemental database diagnostic information:
-2219: :2 (54534d4442312e44465f4d49475242495446494c4-
553ff32).
03/05/2014 08:43:03 ANR9999D_0485338544 DoReorg(tbreorg.c:2760) Thread<36>:
Reorg(TblResume )(flags 0x100000) for
"TSMDB1"."DF_MIGRBITFILES" failed with result code -2219.
03/05/2014 08:43:03 ANR9999D Thread<36> issued message 9999 from:
03/05/2014 08:48:03 ANR0162W Supplemental database diagnostic information:
-2219: :2 (54534d4442312e44465f4d49475242495446494c4-
553ff32).

Any thoughts?

 

[moon-buddy]

Did you update from 6.1.5 or later (6.1.5.x)?

Not 100% sure about this but I think the resolution to your issue is to update to 6.3.4. What I remember is that there is DB2 issue that is resolved at 6.3.3 or later.

 

[rallingham]

That was my thought initially. I have found a few things out there, but we cannot upgrade further. The customer is small and the windows box this is on is Win2003. TSMV6.3 is not supported for this box and there is no way they will be able to upgrade until sometime next year, when the lease expires on their current equipment. I upgraded them from V5.5.5 so that they would have support, but it looks like it is not a great way to go. Perhaps a ticket with IBM is in order. I have found this link: http://www-01.ibm.com/support/docview.wss?uid=swg21634521 regarding the issue, but it is not all that clear to me. Does the TSM server need to be down to run this procedure or can it be up or what?

 

[moon-buddy]

The TSM server must be UP. I did this a while back on a 6.1.5.10 system before I moved to 6.3.3.

 

[rallingham]

Thanks for the info. I have moved almost all my customers to V6.3.4.300 and a couple to V7.1, but this customer just doesn't have budget to move to a bigger machine. I will give this a try.

 

[jlthibaud]

Hi dear all,

I'm running several instances at v6.3.4.300, and I still see these error messages coming every 5 min.
07.07.2015 10:56:34 ANR0162W Supplemental database diagnostic information: -2219: :2
07.07.2015 10:56:34 ANR0162W Supplemental database diagnostic information: -2219: :11

And it started just after DB2 reorg started for table DF_MIGRBITFILES

10:49:54 ora : q act begind=07/01/2015 endd=07/07/2015 begint=09:49:35 endt=10:49:35 search=bitfile or=All
Date/Time Message
-------------------- ----------------------------------------------------------
07/05/2015 01:20:14 ANR0293I Reorganization for table DF_MIGRBITFILES started.
07/05/2015 04:10:58 ANR1880W Server transaction was canceled because of a conflicting lock on table DF_MIGRBITFILES. (SESSION: 7438149, PROCESS: 21694)
07/05/2015 04:10:58 ANR0106E bfaggrut.c(3724): Unexpected error 1014 fetching row in table "BF.Aggregated.Bitfiles". (SESSION: 7438149, PROCESS: 21694)
07/05/2015 05:26:38 ANR1880W Server transaction was canceled because of a conflicting lock on table DF_MIGRBITFILES. (SESSION: 7459401, PROCESS: 21731)
07/05/2015 05:26:38 ANR0106E bfaggrut.c(3724): Unexpected error 1014 fetching row in table "BF.Aggregated.Bitfiles". (SESSION: 7459401, PROCESS: 21731)
07/05/2015 05:37:53 ANR1880W Server transaction was canceled because of a conflicting lock on table DF_MIGRBITFILES. (SESSION: 7458560, PROCESS: 21723)
07/05/2015 05:37:53 ANR0106E dfrtrv.c(1057): Unexpected error 1014 fetching row in table "DF.Bitfiles". (SESSION: 7458560, PROCESS: 21723)
Does anyone know when this issue will be fixed ?
Or, workaround would be to schedule manually DB2 reorg or disable reorg ?

Thanks in advance for your replies.