IBM Support

LI73753: RESTARTED LOAD MAY CRASH THE INSTANCE ON SQLUKILLUSEREXIT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A Load which previously failed on the Build phase and gets
    restarted, might crash the instance if we cancel it after having
    run it again with restart option.
    
    The stack will show the following functions:
    
    0 ossDumpStackTrace
    1 OSSTrapFile::dump
    2 sqlo_trce
    3 sqloEDUCodeTrapHandler
    4 __invoke_dynamic_linker__
    5 SQLO_SLATCH_CAS64::getIdentity
    6 sqluKillUserExit
    7 sqlulTerminate
    8 sqlulPrcErr
    9 sqlulFRMResponse
    10 sqlulPollMsg
    11 sqluvload
    12 call_sqluvload
    13 sqluLoadPartition
    14 sqlu_register_table_load
    15 sqluvtld_route_in
    16 sqlesrvr
    17 sqleMappingFnServer
    18 sqlerKnownProcedure
    19 sqlerCallDL
    20 sqljs_ddm_excsqlstt
    21 sqljsParseRdbAccessed
    22 sqljsParse
    23 sqljsSqlam
    24 sqljsDriveRequests
    25 sqljsDrdaAsInnerDriver
    26 sqljsDrdaAsDriver
    27 sqeAgent::RunEDU
    28 sqzEDUObj::EDUDriver
    29 sqlzRunEDU
    30 sqloEDUEntry
    31 pthread_cond_timedwait@@GLIBC_2.3.2
    32 clone
    
    To reproduce:
    
    1.
    Connect to db sample (target db)
    db2 "declare c cursor database ITR2 user db2inst3 using db2inst3
    for select * from core.job"
    db2 "load from c of cursor replace into core.job cpu_parallelism
    1"
    
    Control C this Load as we get in Build Phase.
    
    2.
    db2 "declare c cursor database ITR2 user db2inst3 using db2inst3
    for select * from core.job"
    db2 "load from c of cursor restart into core.job cpu_parallelism
    1"
    
    
    and now a Control C on this restarted load will crash the server
    

Local fix

  • N/A
    

Problem summary

  • USER AFFECTED: ALL
    PROBLEM DESCRIPTION:RESTARTED LOAD MAY CRASH THE INSTANCE ON
    SQLUKILLUSEREXIT
    PROBLEM SUMMARY:
    ERROR DESCRIPTION:
    A Load which previously failed on the Build phase and gets
    restarted, might crash the instance if we cancel it after having
    run it again with restart option.
    
    The stack will show the following functions:
    
    0 ossDumpStackTrace
    1 OSSTrapFile::dump
    2 sqlo_trce
    3 sqloEDUCodeTrapHandler
    4 __invoke_dynamic_linker
    5 SQLO_SLATCH_CAS64::getIdentity
    6 sqluKillUserExit
    7 sqlulTerminate
    8 sqlulPrcErr
    9 sqlulFRMResponse
    10 sqlulPollMsg
    11 sqluvload
    12 call_sqluvload
    13 sqluLoadPartition
    14 sqlu_register_table_load
    15 sqluvtld_route_in
    16 sqlesrvr
    17 sqleMappingFnServer
    18 sqlerKnownProcedure
    19 sqlerCallDL
    20 sqljs_ddm_excsqlstt
    21 sqljsParseRdbAccessed
    22 sqljsParse
    23 sqljsSqlam
    24 sqljsDriveRequests
    25 sqljsDrdaAsInnerDriver
    26 sqljsDrdaAsDriver
    27 sqeAgent::RunEDU
    28 sqzEDUObj::EDUDriver
    29 sqlzRunEDU
    30 sqloEDUEntry
    31 pthread_cond_timedwait@@GLIBC_2.3.2
    32 clone
    
    To reproduce:
    
    1.
    Connect to db sample (target db)
    db2 "declare c cursor database ITR2 user db2inst3 using db2inst3
    for select * from core.job"
    db2 "load from c of cursor replace into core.job cpu_parallelism
    1"
    
    Control C this Load as we get in Build Phase.
    
    2.
    db2 "declare c cursor database ITR2 user db2inst3 using db2inst3
    for select * from core.job"
    db2 "load from c of cursor restart into core.job cpu_parallelism
    1"
    
    
    and now a Control C on this restarted load will crash the server
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.1, FixPak 7
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI73753

  • Reported component name

    DB2 UDB WSE LIN

  • Reported component ID

    5765F3504

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-09-08

  • Closed date

    2009-04-17

  • Last modified date

    2009-04-17

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

    LI73752

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

Fix information

  • Fixed component name

    DB2 UDB WSE LIN

  • Fixed component ID

    5765F3504

Applicable component levels

  • R910 PSY

       UP

  • R950 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 October 2021