IBM Support

IT06923: DIFFERENT NUMBER OF FILES ON SOURCE AND TARGET SERVER (AS SEEN IN Q REPLNODE) DUE TO DUPLICATE OBJECTS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Replicated objects which were backed up to a source server at a
    level below 6.3.0 or were imported to a source server
    (regardless of the version used) may be duplicated upon
    replication node synchronization.
    
    The difference can be noticed issuing command ?query replnode?.
    For example:
    Node Name Type Filespace Name FSID  Files on Replication  Files
    on
                                        Server     Server (1) Server
    (1)
    ---------------     ----     ---------------     ----
    ----------
    TSMS1    Bkup     /           5     31,529    TSMS2       43,637
    TSMS1    Bkup     /home       14    62,845    TSMS2       89,876
    TSMS1    Bkup     /home/cores 20    233       TSMS2       264
    
    
    
    Customer/L2 Diagnostics:
    Run the following commands to identify duplicate objects,
    replacing $nodeid by the nodeid of the replication node.
    
    The nodeid can be found with this command:
    
    db2 "select nodeid from nodes where nodename='$nodename'"
    
    then run:
    
    db2 "select fsid,hl,ll,insdate,count(*) as count from
    tsmdb1.backup_objects where nodeid=$nodeid group by
    fsid,hl,ll,insdate having count(*)>1"
    
    db2 "select fsid,hl,ll,insdate,count(*) as count from
    tsmdb1.archive_objects where nodeid=$nodeid group by
    fsid,hl,ll,insdate having count(*)>1"
    
    db2 "select fsid,extobjid,insdate,count(*) as count from
    tsmdb1.spaceman_objects where nodeid=$nodeid group by
    fsid,extobjid,insdate having count(*)>1"
    
    Suppose this output is generated by the first select statement.
    
    
    
    
    
    FSID        HL                                          LL
    INSDATE                    COUNT
    ----------- -------------------------------------------
    -------------------------------------------
    -------------------------- -----------
             2 x'44FE682039AB247806612143FC28190023457621'
    x'722B28449201BE7832947659E2837A625B26438C'
    2014-12-14-09.10.14.000000           4
    
    Issue the following DB2 statement using the values output by the
    previous select (fsid, hl and ll for backup_objects or
    archive_objects, fsid and extobjid for spaceman_objects).
    
    db2 "select objid,insdate,gmtinsdate from tsmdb1.backup_objects
    where nodeid=$nodeid and fsid=2 and
    hl=x'44FE682039AB247806612143FC28190023457621' and
    ll=x'722B28449201BE7832947659E2837A625B26438C'"
    
    OBJID        INSDATE                    GMTINSDATE
    ------------ --------------------------
    --------------------------
     7734382921 2014-09-14-09.10.14.000000
    2014-09-14-17.10.14.000000
     9934879275 2014-09-14-09.10.14.000000
    2014-09-14-16.10.14.000000
     9832447883 2014-09-14-09.10.14.000000
    2014-09-14-16.10.14.000000
     8324576858 2014-09-14-09.10.14.000000
    2014-09-14-16.10.14.000000
    
    If, as shown above, the INSDATE values match but the GMTINSDATE
    values differ by an hour, this APAR applies.
    
    
    Tivoli Storage Manager Versions Affected: All Tivoli Storage
    Manager Server 6.3.x  and 7.1.x
    
    
    Initial Impact: low
    
    Additional Keywords: Replication duplicated object import
    replnode
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Tivoli Storage Manager server users of 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 and 7.1.3. Note that   *
    * this is subject to change at the discretion of IBM.          *
    ****************************************************************
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IT06923

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-02-05

  • Closed date

    2015-06-08

  • Last modified date

    2015-06-08

  • 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



Document information

More support for: Tivoli Storage Manager

Software version: 63L

Reference #: IT06923

Modified date: 08 June 2015