IT02221: REPLICATE NODE MAY FAIL WITH ANR0102E ERROR 1202 INSERTING ROW IN TABLE "REPLICATED.OBJECTS".

6.3.6.000-TIV-TSMRPT-AGENT-Linux
6.3.6.000-TIV-TSMRPT-AGENT-AIX
6.3.6.000-TIV-TSMRPT-AIX
6.3.6.000-TIV-TSMRPT-AGENT-Windows
6.3.6.000-TIV-TSMRPT-Linuxx86
6.3.6.000-TIV-TSMRPT-Linuxx86_64
6.3.6.000-TIV-TSMRPT-WindowsI32
6.3.6.000-TIV-TSMRPT-WindowsX64
6.3.6.000-TIV-TSMAC-WindowsX64
6.3.6.000-TIV-TSMAC-WindowsI32
6.3.6.000-TIV-TSMAC-SolarisSPARC
6.3.6.000-TIV-TSMAC-Linuxx86
6.3.6.000-TIV-TSMAC-Linuxs390x
6.3.6.000-TIV-TSMAC-AIX
6.3.6.000-TIV-TSMALL-SolarisSPARC
6.3.6.000-TIV-TSMALL-WindowsX64
6.3.6.000-TIV-TSMSTA-WindowsI32
6.3.6.000-TIV-TSMALL-HP-UX
6.3.6.000-TIV-TSMALL-Linuxppc64
6.3.6.000-TIV-TSMALL-AIX
6.3.6.000-TIV-TSMALL-Linuxs390x
6.3.6.000-TIV-TSMALL-Linuxx86_64
IBM Tivoli Storage Manager (TSM) server V7.1.1.x interim fix downloads
IBM Tivoli Storage Manager V6.3 Fix Pack 6 (6.3.6.000) Server Downloads

APAR status

• Closed as program error.

Error description

• A key collision may occur when multiple source servers are
  replicating filespaces with grouped data to the same target
  server.
  The following error will be seen on the Target Server:
  ANR0102E imrepl.c(3566): Error 1202 inserting row in table
  "Replicated.Objects".
  The following error will be seen on the Source Server:
  ANR1893E Process #### for Replicate Node completed with a
  completion state of FAILURE.
  Tivoli Storage Manager Versions Affected: 6.3,7.1
  Customer/L2 Diagnostics:
  Initial Impact: High
  Additional Keywords: repl src fails tsm
  

Local fix

• On the Target server issue run the following as the instance
  owner:
  db2 connect to tsmdb1
  db2 set schema tsmdb1
  db2 "select nodename, nodeid from nodes"
  Find the nodeid for the failing node and replace it for <NODEID>
  in the following:
  db2 "delete from inflight_replgroups where tgt_groupid in
  (select objid from replicated_objects where nodeid=<NODEID>)"
  Then issue the following from DSMADMC:
  1.) Issue the following command on the target replication
  server:
  REMOVE REPLNODE node_name
  Important note: Make sure the REMOVE REPLNODE completes before
  performing the next steps.
  Depending on the amount of replicated data, the REMOVE REPLNODE
  can take additional time to
  complete.
  2.) Issue the following command on the target replication
  server:
  UPDATE NODE node_name REPLSTATE=ENABLED REPLMODE=SYNCREC
  Note: Make sure the command completes successfully.
  Use QUERY NODE node_name FORMAT=DETAIL to confirm the REPLMODE
  and
  REPLSTATE is correct.
  3.) Issue the following command on the source replication
  server:
  REMOVE REPLNODE node_name
  Note: Make sure the REMOVE REPLNODE completes before
  performing the next steps.
  Depending on the amount of replicated data, the REMOVE REPLNODE
  can take additional time to
  complete.
  4.) Issue the following command on the source replication
  server:
  UPDATE NODE node_name REPLSTATE=ENABLED REPLMODE=SYNCSEND
  Note: Make sure the command completes successfully.
  Use QUERY NODE node_name FORMAT=DETAIL to confirm the REPLMODE
  and
  REPLSTATE is correct.
  5.) At this point, you can replicate the affected node by
  issuing the following command on the source replication server:
  REPLICATE NODE node_name
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager server users running node         *
  * replication..                                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available.  This problem is          *
  * currently projected to be fixed in levels 6.3.6, 7.1.1.200,  *
  * and 7.1.3.  Note that this is subject to change at the       *
  * discretion of IBM.                                           *
  ****************************************************************
  

Problem conclusion

• The problem was fixed.
  Affected Platforms: AIX, HP-UX, Solaris, Linux, and Windows.
  

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

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP