Joerg,

We experienced this problem a number of months ago and opened an ETR with
IBM on it.  I never did get a good explanation or resolution as to why it
was happening.  It occurred on at least 3 separate occasions.  We had
plenty of scratch volumes defined in the secondary pool, yet we received
the same messages you did.  Unfortunately, I can't find the details of the
ETR record.

I supplied IBM with a lot of detailed information on our storage pools,
management classes, etc, but nothing pointed to why we would have this
problem.  The problem disappeared as mysteriously as it appeared and has
not returned.

I would suggest opening a problem with IBM and let them look at your
specific environment.

Best of luck,
Pete

To:       ADSM-L @ VM.MARIST.EDU
cc:        (bcc: Peter F Carranti)
From:     passenberg @ LIDO.NET
Date:     04-21-97 03:31:43 AM GMT
Subject:  Migrations doesnt't work: ANR1025W, but why ?




Hello together,

we have the following problem:

The migration from our Storage-Pools (DISK's)
to the defined next storagepools LIDOPOOL (EXABYTE-Tapelibrary)
doesn't work, cause ADSM says:

 "ANR1025W Migration process 239 terminated for storage pool
  BACKUPPOOL - insufficient space in subordinate storage pool"

But a query say that there sould be anothe space.

Storage     Device     Estimated  %Util   %Migr   High    Low   Next
Pool Name   Class Name  Capacity                  Mig%   Mig%   Storage
                            (MB)                                 Pool
--------   ----------  ---------  -----   -----   ----   ----   ---------
BACKUPPOOL  DISK        2,000.0    99.7    99.7     85     55   LIDOPOOL
BACKUPPOOL  DISK        2,000.0    99.7    99.7     85     55   LIDOPOOL
LIDOPOOL    LIDOCLASS  46,728.9    48.1   100.0     98     90


So, any hint's and Tips ?

by and thanks, Joerg