ADSM-L

IMPORT-Problem ADSM Server 3113

1998-09-03 18:12:21
Subject: IMPORT-Problem ADSM Server 3113
From: Colin Dawson <redhead AT US.IBM DOT COM>
Date: Thu, 3 Sep 1998 18:12:21 -0400
Howdy,
     There was an error in the import processing relating to a
return code at the point that the import processing is doing
file storage.

     The error message to expect is:

ANR9999D xibf.c(1161): Unknown result code (23) from bfCreate.

Specifically, a space reservation request against a disk storage
pool fails which causes this return code to be issued.  At the point
that the disk storage reservation occurs, it is not possible to
reclaim space used by cached files in the disk pool (if the storage
pool has cache=yes set).  So, the return code is issued and
unfortunately, the import fails because it can not import the
required file.

This problem has already been identified and has been fixed and
will be available in the next ptf.  This fix is NOT in the adsm 3115
ptf level.  It will be in the ptf following 3115.

     The options at this point are the following:

1) Wait for the ptf to become available and then perform the import.
2) Contact your IBM service representative and specifically the
ADSM service group.  They should be able to:
   - Track the problem with a pmr.
   - Identify the ptf that the fix will be in once
     the ptf is available.
   - Open an apar to document the problem.
3) The problem is specific to not having enough space in the
DISK storage pool the data is being imported to.  Possible circumventions
would be to
   a) Increase the size of the disk pool (This may just delay the
      point at which the error is seen.)
   b) Make the disk pool unavailable so that the import
      is done to a sequential media storage pool.  This would require
      the disk storage pool to have a NEXT= parameter set pointing to
      a storage pool using sequential media and to issue the command

      'UPDATE STGPOOL X ACCESS=UNAVAILABLE' or
      'UPDATE STGPOOL X ACCESS=READONLY'

      Please note that at the point that the storage pool is not
      access=readwrite, other processing (client backup, etc)
      that use this storage pool will not be able to write to this
      storagepool.

I do not have the official ptf number at this point - these are being
created as part of the preparation for this next ptf and they are
not yet available.
-------------------------------------------
Colin Dawson
Colin Dawson
ADSM Server Development
<Prev in Thread] Current Thread [Next in Thread>
  • IMPORT-Problem ADSM Server 3113, Colin Dawson <=