Gretchen, et al.

We have been working with IBM level 2 support on this same problem.
We discovered it while trying to delete a SYSTEM OBJECT filespace,
but the problem first appears during the SYSTEM OBJECT backups.

We currently have 3 errors recurring nightly:

tsm: ITS>q act begind=-1 se=.c(
05/26/2003 20:02:57     ANR0104E imbkins.c(3632): Error 2 deleting row from
table "Expiring.Objects".
05/26/2003 20:37:47     ANR0104E imbkins.c(3632): Error 2 deleting row from
table "Expiring.Objects".
05/26/2003 21:20:04     ANR0104E imbkins.c(3632): Error 2 deleting row from
table "Expiring.Objects".
05/27/2003 13:38:28     ANR2017I Administrator OWEN issued command: QUERY
ACTLOG begind=-1 se=.c(

tsm: ITS>q act begind=-1 se=ANR0530W
05/26/2003 20:02:57     ANR0530W Transaction failed for session 16941 for node
XXXXX (WinNT) - internal server error detected.
05/26/2003 20:37:47     ANR0530W Transaction failed for session 17040 for node
XXXXX (WinNT) - internal server error detected.
05/26/2003 21:20:04     ANR0530W Transaction failed for session 17623 for node
TTTTT (WinNT) - internal server error detected.
05/27/2003 13:44:00     ANR2017I Administrator OWEN issued command: QUERY
ACTLOG begind=-1 se=ANR0530W

Node XXXXX is WinNT 5.00 (Win2K) running TSM client v4.1.2.12.
Node TTTTT is WinNT 5.00 (Win2K) running TSM client v5.1.5.15.

These nodes and two others similar to TTTTT already have OLDSYS-XX
(renamed SYSTEM OBJECT) filespaces that can not be deleted without
manually recreating missing bitfile object IDs for one or more objects.

The first time around, IBM level-2 support directed me through the
following iterative manual process:  [*5 filespaces * 3-7 missing BFOs]

       try to delete the OLDSYS* filepsace
       loop: while delete filespace fails w/ missing BFO for object#
       show invo 0 object#     [typically found]
       show bfo 0 object#      [not found; caused del fi failure]
       manually add table row, populate all the fields, check it, etc.
       try to delete the OLDSYS* filespace
       end loop

Here's hoping that IBM will develop a "cleanup" for...
or simply automate the fixing of... missing Expiring.Object BFOs.

I forwarded Gretchen's and Henk's emails to IBM level-2 support.

Run these queries to see if this problem lurks on your TSM service:

       Query ACTlog BEGINDay=-1 SEarch=.c(
       Query ACTlog BEGINDay=-1 SEarch=ANR0530W

Good luck!  [Here's hoping this is the last of SYSTEM OBJECT problems.]
--
Jim.Owen AT Yale DOT Edu   (203.432.6693)

Gretchen L. Thiele wrote:

I've been plagued by a few problems when deleting accounts. So far,
it seems like Win2K or WinXP clients (SYSTEM OBJECTs are involved
again!) are prone to this error:

05/27/2003 09:00:56  ANR2017I Administrator XXXXXX issued command:
DELETE
FILESPACE ZZZZZZ *
05/27/2003 09:00:56  ANR0984I Process 185 for DELETE FILESPACE started
in the
BACKGROUND at 09:00:56.
05/27/2003 09:00:56  ANR0800I DELETE FILESPACE * (fsId=6) for node
ZZZZZZ started as process 185.
05/27/2003 09:00:56  ANR0802I DELETE FILESPACE * (fsId=6)
(backup/archive data)
for node ZZZZZZ started.
05/27/2003 09:00:57  ANR0104E imutil.c(7761): Error 2 deleting row from
table
"Expiring.Objects".
05/27/2003 09:00:57  ANR9999D imfsdel.c(1872): ThreadId<25> Error 19
deleting
group leader 0 176658713.

I've tried a number of things - renaming the filespace, moving the node
data and then
auditing the tape, deleting the filespace specifically - but it's
really a database
'corruption' and can only be fixed by an audit (per support).

Gretchen Thiele
Princeton University