IBM Support

IT28446: DB2 SERVER GOT CRASHED IN CIEUTIL!CIE::CTEERROR::MAKEDIAGNOSTICMESSAGE

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

  • Db2 server got crashed with a stack as below - A trap stack from
    Windows:
    
    000000d9`a784f550 00007ff8`4053d6f4 msvcr110!invoke_watson+0x17
    000000d9`a784f580 00007ff8`4053d711
    msvcr110!invalid_parameter+0x64
    000000d9`a784f5c0 00007ff8`40523ede
    msvcr110!invalid_parameter_noinfo+0x19
    000000d9`a784f600 00007ff8`405040ae msvcr110!output_s_l+0x802
    000000d9`a784f910 00007ff8`40504201
    msvcr110!vsnprintf_helper+0x92
    000000d9`a784f980 00007ff8`4050411d msvcr110!vsnprintf_s_l+0xdd
    000000d9`a784f9c0 00007ff8`3ebdb628 msvcr110!vsnprintf_s+0x19
    000000d9`a784fa00 00007ff8`3ebc5419 db2sys64!ossVsnprintf+0x28
    000000d9`a784fa50 00007ff8`3ebab3b9
    db2sys64!pdLogInternal+0x2e69
    000000d9`a7850d60 00007ff8`3ebab5f4 db2sys64!pdLogVPrintf+0x109
    000000d9`a7850e20 00007ff8`3ca07b97 db2sys64!pdLogPrintf+0x34
    000000d9`a7850e70 00007ff8`3ca0408e
    cieutil!cie::CteError::makeDiagnosticMessage+0xd37
    000000d9`a7852fb0 00007ff8`3ca0804a
    cieutil!cie::CteError::setSearchSystemError+0x10e
    000000d9`a7853110 00007ff8`2d560183
    cieutil!cie::CteError::setSearchSystemError+0x17a
    000000d9`a78531d0 00007ff8`405362d0
    cieudfe!cie::CieSearchableTvf::search+0x3d3
    000000d9`a7853260 00007ff8`4052de0d
    msvcr110!CallSettingFrame+0x20
    000000d9`a7853290 00007ff8`48982ff3
    msvcr110!_CxxCallCatchBlock+0xf5
    000000d9`a7853360 00007ff8`2d55fe8d
    ntdll!RcConsolidateFrames+0x3
    000000d9`a7876970 00007ff8`2d549fdf
    cieudfe!cie::CieSearchableTvf::search+0xdd
    000000d9`a7876a00 00007ff8`2d543aa3
    cieudfe!CieTextSearchTF+0x5af
    000000d9`a7878ed0 00007ff8`3eab781e
    cieudfe!CieTextSearchTF_extern+0x343
    000000d9`a787b230 00007ff8`3eb65f18
    db2sys64!sqloInvokeFnArgs+0x6f8e
    000000d9`a787d260 00007ff8`32fe837d db2sys64!sqloInvokeUDF+0x318
    000000d9`a787d400 00007ff8`32fe7332
    db2engn!sqlriInvokerTrusted+0xf4d
    000000d9`a787e240 00007ff8`32fe0b7d
    db2engn!sqlriInvokeInvoker+0x1412
    000000d9`a787e8a0 00007ff8`3314c6ac db2engn!sqlriutf+0x1cd
    000000d9`a787e920 00007ff8`32ff9b03 db2engn!sqlri_tfopn+0xdc
    000000d9`a787e9d0 00007ff8`331b7d06 db2engn!sqlriopn+0x393
    000000d9`a787ebf0 00007ff8`332362db db2engn!sqlrita+0x7b6
    000000d9`a787ed30 00007ff8`3305412e db2engn!sqlriNljnPiped+0x23b
    
    Due to APAR IT27122, Db2 silently disappears without any FODC
    folder.  The user may need to setup ADPlus in -crash mode so an
    user dump could be collected to find the trap stack.
    
    In the windows Event log we see the crash:
    
    <EventData><Data><string>db2syscs.exe</string>;
    <string> 10.5.900.618 </string>;
    <string> 59bc333c </string>;
    <string> MSVCR110.dll </string>;
    <string> 11.0.50727.1 </string>;
    <string> 5011a017 </string>;
    <string> c0000409     </string>;
    <string> 000000000006d75f </string>;
    <string> 654 </string>;
    <string> 01d45c4075e8a020 </string>;
    <string> D:\IBM\SQLLIB\bin\db2syscs.exe  </string>;
    <string> C:\Windows\SYSTEM32\MSVCR110.dll </string>;
    <string> 308c8bee-f21a-11e8-80d4-005056a51f7c </string>;
    
    Exception 0xc0000409 is STATUS_STACK_BUFFER_OVERRUN.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * The user running Db2 Text Search.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 v11.1.4.6 or later versions.                  *
    ****************************************************************
    

Problem conclusion

  • The problem is firstly fixed on  Db2 v11.1.4.6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT28446

  • 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

    2019-03-13

  • Closed date

    2021-03-21

  • Last modified date

    2021-03-21

  • APAR is sysrouted FROM one or more of the following:

    IT28246

  • 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:
22 March 2021