IBM Support

IT32475: REPAIR OBJECTVERSIONS" CAN CAUSE PINNED LOG, EXCESSIVE MEMORY USAGE AND AFFECT OTHER OPERATIONS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • APAR IT25325 introduced a new command called "repair
    objectversions" in server versions 8.1.9 and higher.
    This "repair objectversions" command is also run automatically
    by the server on a weekly basis and will be seen starting with:
    
    "Process 4 for REPAIR OBJECTVERSIONS (AUTOMATIC) started in the
    BACKGROUND"
    
    amd can be seen by 'query process' as "repair objectversions
    (automatic)"
    
    When the process runs it can cause a pinned log or can use
    excessive memory, and it can also affect other operations on the
    server,
    as it runs a transaction that will run for excessive duration.
    
    Examples of messages caused by "repair objectversions" running:
    
    
    ANR0171I imbkins.c(7546): Error detected on 50:5,  database in
    evaluation mode. (PROCESS: 4)
    ANR0162W Supplemental database diagnostic information:
     -1:40003:-1224 ([IBM][CLI Driver] SQL1224N The database
     manager is not able to accept new requests, has  terminated all
    requests in progress, or has terminated
     the specified request because of an error or a forced
     interrupt. SQLSTATE=55032). (PROCESS: 4)
    ANR0157W Database operation UPDATE for table
     Backup.Objects failed with result code 4522 and tracking ID:
    12589a040. (PROCESS: 4)"
    
    Process 4 was:
    ANR0984I Process 4 for REPAIR OBJECTVERSIONS (AUTOMATIC)
     started in the BACKGROUND at xx:xx:xx (PROCESS: 4)
    
    and db2diag.log reported MAX_LOG error
    
    FUNCTION: DB2 UDB, data protection services,
    SQLP_TENTRY::sqlpReserveLogSpace, probe:560
    MESSAGE :  "*LOCAL.rip900.200309083525" and application id
    "RIP900 " executing
             under authentication id "90" will be forced off of the
    database for
             violating database configuration parameter MAX_LOG
    (current value
             ""). The unit of work will be rolled back.
    
    Also has been seen:
    
    ANR0163E tbnsql.c(773): Database insufficient memory  detected
    on 44:1.
    
    with db2diag.log reporting:
    
    FUNCTION: DB2 UDB, SQO Memory Management,
    sqloMemLogPoolConditions, probe:910
    DATA #1 : <preformatted>
    LocalOOM FODC Event being generated due to Out of Memory error
    
    
    In dsmffdc.log has been seen following for expiration:
    
    [03-11-2020 13:09:33.035][ FFDC_GENERAL_SERVER_ERROR ]:
    (imdmgr.c:5181) Error 1020 getting GetFsDecommInfo for nodeId
    488, fsId 4
    
    Only run "repair objectversions" command when necessary due to
    IT25325
    
    
    IBM Spectrum Protect versions affected:
    IBM Spectrum Protect Sever 8.1.9.x and higher on all supported
    platforms
    
    Initial Impact: Medium
    
    | MDVREGR 8.1.9.0-TIV_5698MSV |
    
    Additional Keywords: TSM "Spectrum Protect" TS003454175 &#160;
    IT25325 repair pinned log memory error
    

Local fix

  • Run either:
    
    SETOPT DisableAUTORepairObjectVersions YES
    
    Or
    Add to dsmserv.opt
    
    DisableAutoRepairObjectVersions
    
    and restart server
    
    
    to disable "repair objectversions" running automatically.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IBM Spectrum Protect server users.                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See error description.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in level 8.1.10. Note that this is     *
    * subject to change at the discretion of IBM.                  *
    ****************************************************************
    

Problem conclusion

  • This problem was fixed.
    Affected platforms for reported release:  AIX, Linux, and
    Windows.
    Platforms fixed:  AIX, Linux, and Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT32475

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    81A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-07

  • Closed date

    2020-04-09

  • Last modified date

    2020-04-09

  • 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

  • R81A PSY

       UP

  • R81L PSY

       UP

  • R81W PSY

       UP

[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"81A"}]

Document Information

Modified date:
26 August 2021