IT45739: ANR1652E MAY OCCUR AFTER REMOVE REPLNODE AND UPDATE NODE REPLSTATE=ENABLED.

8.2.2.000-IBM-SPSRV-Linuxx86_64
8.2.2.000-IBM-SPSRV-WindowsX64
8.2.2.000-IBM-SPSRV-AIX
8.2.2.000-IBM-SPSRV-Linuxppc64le
8.2.2.000-IBM-SPSRV-Linuxs390x

APAR status

• Closed as program error.

Error description

• ANR1652E may occur after step 8 of the following scenario.
  
  1. Set DISSIMILARPOLICIES ON
  2. Start replication stgrule
  3. HALT the source server in the middle of stgrule running.
  
  4. Do REMOVE REPLNODE on the source.
  5. Do new backup and expiration by the source policy several
  times on the source.
  6. Wait Number of Extents Eligible for Deletion: 0 on the
  source.
  7. Re-enable replication by UPDATE NODE node REPLSTATE=ENABLED
  8. Run replication stgrule again.
  
  After step 3, you may see thousands of state=3 chunks in the
  SD_UNRESOLVED_CHUNKS table in the target server.  The use of
  REMOVE REPLNODE at step 4 is unexpected from the viewpoint of
  current design. There may remain a lot of unresolved extents. As
  result, ANR1652E may appear at the end of replication stgrule
  after step 8, like below:
  ANR1652E Replication failed. Total number of unresolved extents
  is xx,xxx,xxx.
  
  FORCERECONCILE in replication has nothing to do with unresolved
  extents, so that an extension of REMOVE REPLNODE may be the
  solution of this scenario.
  
  IBM Spectrum Protect Versions Affected:
  IBM Storage Protect Servers 8.1.13 and later versions on all
  supported platforms.
  
  Additional Keywords:
  
  TS015225903 Storage Protect REPLICATION STGRULE
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All IBM Storage Protect server users.                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Apply fixing level when available. This problem is currently
  projected to be fixed in level 8.2.2.
  Note that this is subject to change at the discretion of IBM.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels