IBM Support

IT34697: DB2BATCH FAILS TO CAPTURE MONITORING STATISTICS FOR REMOTE INSTANCES IN A KERBEROS ENVIRONMENT

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • In a kerberos environment where no userid and password is used
    for remote connections, "db2batch -mms" without the "-a"
    parameter fails to issue snapshots on remote instances. An error
    message "CLI error in capturing monitoring statistics" is
    returned.
    
    Here are example messages including the error message:
    
    cat $HOME/my-sql
    
    select count(*) from syscat.tables ;
    
    --#SET SNAPSHOT agent_id;
    
    
    db2batch -d sample -f $HOME/my-sql -mss agent_id
    
    * Timestamp: Tue Oct 06 2020 11:36:39 EDT
    ---------------------------------------------
    
    * SQL Statement Number 1:
    
    
    select count(*) from syscat.tables ;
    
    1
    -----------
    479
    
    *** SQLERRP=SQLJCMN SQL1032N No start database manager command
    was issued. SQLSTATE=57019
    *** CLI error in capturing monitoring statistics
    * Summary Table:
    
    Type Number Repetitions Total Time (s) Min Time (s) Max Time (s)
    Arithmetic Mean Geometric Mean Row(s) Fetched Row(s) Output
    --------- ----------- ----------- -------------- --------------
    -------------- --------------- -------------- --------------
    -------------
    
    * Total Entries: 0
    * Total Time: 0.000000 seconds
    * Minimum Time: 0.000000 seconds
    * Maximum Time: 0.000000 seconds
    * Arithmetic Mean Time: 0.000000 seconds
    * Geometric Mean Time: 0.000000 seconds
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users using Kerberos with db2batch                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 6 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT34697

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-27

  • Closed date

    2021-03-15

  • Last modified date

    2021-03-15

  • 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

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1"}]

Document Information

Modified date:
16 March 2021