Just a couple of updates on this
1. MIGRATION of DISKPOOL --> TAPEPOOL fails with
ANR0102E asalloc.c(####): Error 1 inserting row in table
AS.Segments" error
2. MOVE DATA DISKPOOL TAPEPOOL also fails with
ANR0102E asalloc.c(####): Error 1 inserting row in table
AS.Segments" error
3. BACKUP STGPOOL DISKPOOL COPYPOOL works (no errors, 100% moved)
4. MOVE DATA DISKPOOL ALT-TAPEPOOL works (no errors, 100% moved)
5. MIGRATION of DISKPOOL --> ALT-TAPEPOOL works (no errors, 100% moved)
6. RECLAIM TAPEPOOL fails with
ANR0102E asalloc.c(####): Error 1 inserting row in table
AS.Segments" error
7. AUDIT VOLUME succeeds on all DISKPOOL volumes (0 errors)
It's beginning to look like there's a problem with TAPEPOOL entries in the
DB. Anyway, we're operating ok with #5 as our current workaround for
this, so the crisis is over for now, but comments on similar experiences
and possible solutions are still welcome.
One respondent mentioned that there was an APAR on this - if anyone knows
the APAR#, please let me know.
RSVP........thanks
Kent Monthei
GlaxoSmithKline
----- Forwarded by Kent J Monthei/CIS/PHRD/SB_PLC on 04-Nov-2002 16:45
-----
Kent J Monthei
01-Nov-2002 10:27
To: ADSM-L
cc:
Subject: URGENT - ANR0102E asalloc.c(####): Error 1 inserting row in
table
"AS.Segments" during Migration / what is table 'AS.Segments' ??
Solaris 2.6 / TSM 4.1.2 (I know..........we're upgrading to Solaris 8 ,
TSM 5.1 very soon!)
DB - 50GB, PctUtil 78%
Log - 4GB, LogMode=Normal, PctUtil=1%
DISKPOOL - 138GB, PctUtil 87%, PctMigr 39% (currently)
We're getting migration process failures. We start 4 migration processes
at a time, but lately only the first 2 run to completion successfully. The
others fail almost imediately after starting, with this error-pair:
ANR0102E asalloc.c(####): Error 1 inserting row in table "AS.Segments".
ANR1032W Migration process ### terminated for storage pool
DISKPOOL - internal server error detected.
For failed processes, MigrationProcesses=4,MigrationDelay=0 settings cause
the server to immediately start new migration processes, which also fail
with the same error. This fail/restart cycle continues until the original
two Migration processes finally finish, eventually leaving nothing left to
migrate, and the cycle finally stops.
Until today, we could avoid this by reducing the DISKPOOL
MigrationProcesses setting to 2 or 1. However, this morning all migration processes
reported the error. None ran to successful completion and we had to intervene.
At this point, we cannot migrate date from this pool & need some expert
advice a.s.a.p.
Where's the problem, and how can I fix it to break this cycle?
-rsvp, thanks
Kent Monthei
GlaxoSmithKline
