IBM Support

IT44270: IBM MQ MFT database logger fails to connect to DB2 with SQL30082N (reason 3) if it can't access the credentials file

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

  • An IBM MQ Managed File Transfer (MFT) database logger has been
    configured to connect to DB2 using credential information stored
    in an MQ MFT credentials file (MQMFTCredentials.xml). When the
    logger is started, it reports the following errors in it's event
    log (output0.log) even though the password needed to connect to
    the database is stored in the credentials file:
    
    [30/07/2023 10:20:59:108 GMT] 00000001 Logger  E  BFGDB0049E:
    The database logger failed to connect to the database due to an
    authorization error. The error reported by the database is:
    [jcc][4038][12241][4.32.45] T2LUW exception: SQL30082N  Security
    processing failed with reason "3" ("PASSWORD MISSING").
    SQLSTATE=08001 ERRORCODE=-30082, SQLSTATE=08001
    [30/07/2023 10:20:59:108 GMT] 00000001 Logger  E  BFGDB0005E: A
    serious error has occurred, and the logger will stop. Messages
    in progress will be rolled back to the queue manager. See the
    preceding log entry for details.
    [30/07/2023 10:20:59:139 GMT] 00000001 Logger  E  BFGDB0073E:
    The logger has ended abnormally with return code 70.
    

Local fix

  • Look to review the permission on the file pointed to by the
    logger property "wmqfte.database.credentials.file".
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of MQ Managed File Transfer (MFT), who
    have a Database Logger that connects to DB2.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Credential information for MQ Managed File Transfer (MFT)
    Database Loggers can be stored in an MQ MFT credentials file
    (MQMFTCredentials.xml).
    
    If a logger had been configured to use the information in a
    credentials file when connecting to DB2, and the file
    permissions on that file had not been configured correctly, then
    the logger would continually stop and restart, and write the
    following error messages to its event log (output0.log):
    
    BFGDB0049E: The database logger failed to connect to the
    database due to an authorization error. The error reported by
    the database is: [jcc][4038][12241][4.32.45] T2LUW exception:
    SQL30082N  Security processing failed with reason "3" ("PASSWORD
    MISSING").  SQLSTATE=08001 ERRORCODE=-30082, SQLSTATE=08001
    BFGDB0005E: A serious error has occurred, and the logger will
    stop. Messages in progress will be rolled back to the queue
    manager. See the preceding log entry for details.
    BFGDB0073E: The logger has ended abnormally with return code 70.
    

Problem conclusion

  • To resolve this issue, MQ Managed File Transfer (MFT) database
    loggers have been updated so that:
    
    - If they have been configured to use credential information
    stored in an MQ MFT credentials file when connecting to DB2
    - And the credentials file does not have the correct file
    permissions
    
    then they will shut down and report the following error messages
    in their event log (output0,log):
    
    BFGDB0066E: The logger encountered a problem accessing its
    credentials file and will stop. Reported error: BFGPR0074E: The
    security permissions defined for credentials file '<credentials
    file>' do not meet the minimum requirements for a file of this
    type. Reported problem: <Further details about the issue>
    BFGDB0005E: A serious error has occurred, and the logger will
    stop. Messages in progress will be rolled back to the queue
    manager. See the preceding log entry for details.
    BFGDB0076E: The logger has ended abnormally with return code 78.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.3 LTS   9.3.0.15
    v9.x CD    9.3.5
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT44270

  • Reported component name

    MQ BASE V9.3

  • Reported component ID

    5724H7291

  • Reported release

    930

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-08-01

  • Closed date

    2023-10-05

  • Last modified date

    2023-10-05

  • 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

    MQ BASE V9.3

  • Fixed component ID

    5724H7291

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.3","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
06 October 2023