Re: ANR9999D and ANR0197E
2003-02-13 11:06:27
Steven,
I am os390 TSM 4.2.2, but I think this problem extends to AIX 4.2.2 as well
When I queried it with IBM, they referred me to APAR PQ61001 and suggested I
needed to audit the
database to resolve. as you can imagine I wasn't very happy to do that, well I
read the apar and replied
I have looked at APAR PQ61001 and the inference there is that there is
no impact on the database and hence no need for database audit.
Both my errors refer to scratch tapes added to TSM before any entries
written to the tapes. Therefore it would appear logical that there
wouldnot yet be any database entries for them and so we do appear to
have the unnecessary check mentioned in APAR PQ61001
In a production TSM a database audit of a 20gb database is not a thing
to undertake lightly because of the downtime.
I can just see myself explaining to management that we need to make TSM
unavailable for a day because we have upgraded the code
The gist of the IBM response was :-
John may choose to simply ignore the messages for now as the check on
the volume should not be being made.
If the problem persists after 4.2.3 or higher is installed then he
would need to consider the Audit.
Well I am yet to install 4,2.3 after some months, and nothing nasty has happened
yet
apart from those annoying messages.
I just wish that IBM tested the code better.
Hope this helps,
John
"Conko, Steven" <sconko AT adt DOT com> on 02/13/2003 03:47:28 PM
Please respond to "ADSM: Dist Stor Manager" <adsm-l AT vm.marist DOT edu>
To: adsm-l AT vm.marist DOT edu
cc: (bcc: John Naylor/HAV/SSE)
Subject: ANR9999D and ANR0197E
sorry... i tried to search for this but i cant seem to get connected to
adsm.org. any idea what is happening with these errors?
TSM V4.2.2 running on AIX 4.3.3 ML10 connected to 3494 Library with 3590
Tape drives
we have seen this error before... this time happens to be during a backup
stgp....
02/13/03 09:58:05 ANR8337I 3590 volume J00521 mounted in drive D1
(/dev/rmt6).
02/13/03 09:58:05 ANR1340I Scratch volume J00521 is now defined in
storage
pool COPY_POOL_01.
02/13/03 09:59:36 ANR0195W Attempting to remove extraneous database
entries
for volume J00521.
02/13/03 09:59:36 ANR9999D asalloc.c(663): ThreadId<61> Volume J00521
being
accessed remotely - ending repair attempt.
02/13/03 09:59:36 ANR0197E Removal of extraneous database entries for
volume
J00521 failed due to contention with other server
processes or activities.
02/13/03 09:59:36 ANR0195W Attempting to remove extraneous database
entries
for volume J00521.
02/13/03 09:59:36 ANR9999D asalloc.c(663): ThreadId<62> Volume J00521
being
accessed remotely - ending repair attempt.
now it seems okay....
q vol j00521 f=d
Volume Name: J00521
Storage Pool Name: COPY_POOL_01
Device Class Name: 3590CLASS
Estimated Capacity (MB): 46,575.5
Pct Util: 100.0
Volume Status: Filling
Access: Read/Write
Pct. Reclaimable Space: 0.0
Scratch Volume?: Yes
In Error State?: No
Number of Writable Sides: 1
Number of Times Mounted: 1
Write Pass Number: 1
Approx. Date Last Written: 02/13/03 10:45:48
Approx. Date Last Read: 02/13/03 10:01:11
Date Became Pending:
Number of Write Errors: 0
Number of Read Errors: 0
Volume Location:
Last Update by (administrator):
Last Update Date/Time: 02/13/03 09:58:05
**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.
Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**********************************************************************
|
|
|