ADSM-L

Re: Problem deleting filespace SYSTEM OBJECT

2002-09-20 07:35:51
Subject: Re: Problem deleting filespace SYSTEM OBJECT
From: Joel Fuhrman <joelf AT CAC.WASHINGTON DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 20 Sep 2002 02:53:11 -0700
Yes I have this problem.  The reason I needed to delete the system objects
was because they were not being deleted by EXPIRE INVENTORY and they were
consuming 30% of my database space.

My suggestion to all TSM admins is to do a
   QUERY OCCUPANCY * "SYSTEM OBJECT"
to verify that you do not have excessive copies.

On 5.1.1.4, I did the CLEANUP BACKUPGROUP and I still could not delete the
system objects.  I reran the cleanup command numerous times and each time it
reported inspecting and deleting fewer objects than the previous run.  The
number was still in the 2000 range when I gave up and installed 5.1.1.6.
On this level, expiration still failed to delete the system objects but I
could manually delete most of them.  As of now I have 6 servers where I can
not delete the system objects. I have an open PMR.

On Thu, 19 Sep 2002, Gerhard Rentschler wrote:

> Hello,
> I ran into the following problem with TSM 5.1.1.4 on AIX 4.3.3.
> Using the command
> del filespace rus_zsdsinz 'SYSTEM OBJECT'
> I get the following messages in the activity log:
> 09/18/02 16:20:33     ANR0984I Process 452 for DELETE FILESPACE started in
> the
>                        BACKGROUND at 16:20:33.
> 09/18/02 16:20:33     ANR0800I DELETE FILESPACE * (fsId=4) for node
> RUS_ZSDSINZ
>                        started as process 452.
> 09/18/02 16:20:33     ANR0802I DELETE FILESPACE * (fsId=4) (backup/archive
> data)
>                        for node RUS_ZSDSINZ started.
> 09/18/02 16:20:34     ANR9999D imfsdel.c(1860): ThreadId<84> Error 1123
> deleting
>                        group leader 0 585684848.
> 09/18/02 16:20:34     ANR0985I Process 452 for DELETE FILESPACE running in
> the
>                        BACKGROUND completed with completion state FAILURE at
>                        16:20:34.
> I opened a PMR. Level 1 suggested to run the command "cleanup backupgroup"
> and retry the delete filespace command. It didn't help. The next advice was
> to upgrade to TSM 5.1.1.6 and retry the cleanup backupgroup and del
> filespace. The next thing to do would be a dsmserv auditdb. However, this
> would take a lot of time with my 55 GB database.
>
> Has anyone else seen this? Level 1 told me that he found only one similar
> problem.
> Best regards
> Gerhard
> ---
> Gerhard Rentschler            email:g.rentschler AT rus.uni-stuttgart DOT de
> Regional Computing Center     tel.   ++49/711/685 5806
> University of Stuttgart       fax:   ++49/711/682357
> Allmandring 30a
> D 70550
> Stuttgart
> Germany
>

<Prev in Thread] Current Thread [Next in Thread>