IBM Support

IY89415: DB2REORG INPLACE PAUSE/STOP SHOWS WRONG REASON CODE 11 AND DB2PDSHOWS WRONG STATUS IF THERE IS A LOCK ON TABLE

 

APAR status

  • Closed as program error.

Error description

  • db2reorg does not show reason code 10 when a inplace stop or
    pause has been issued and we issue another one if there is a
    lock on the table:
    
     10 PAUSE or STOP has already been issued. The specified action
    is asynchronous and may not be effective immediately.
    
    db2pd shows an status of "started" and there is no way to know
    what has been issued or what is been progressing unless we have
    the right reason code:
    
    
    Reproduction following the steps:
    1. Issue an inplace reorg and pause it.
    2. Lock a row on the table
    3. Resume inplace reorg , it will show as "started" in db2pd
    -reorgs
    4. Issue a stop reorg
    db2pd -reorgs still shows reorg "started"
    
    5. Issue another stop:
    you get
    SQL2219N The specified INPLACE table reorganization action on
    table
    "DB2INST3.TEST_REORG" is not allowed on one or more nodes.
    Reason code:
    "11".
    11 There is no table reorganization to PAUSE or STOP.
    
    Would expect reason code "10"
    

Local fix

  • No Workaround
    

Problem summary

  • Users affected: ALL
    PROBLEM DESCRIPTION: DB2REORG INPLACE PAUSE/STOP SHOWS WRONG
    REASON CODE 11 AND DB2PD SHOWS WRONG STATUS IF THERE IS A LOCK
    ON TABLE
    PROBLEM SUMMARY:
    db2reorg does not show reason code 10 when a inplace stop or
    pause has been issued and we issue another one if there is a
    lock on the table:
    
     10 PAUSE or STOP has already been issued. The specified action
    is asynchronous and may not be effective immediately.
    
    db2pd shows an status of "started" and there is no way to know
    what has been issued or what is been progressing unless we have
    the right reason code:
    
    
    Reproduction following the steps:
    1. Issue an inplace reorg and pause it.
    2. Lock a row on the table
    3. Resume inplace reorg , it will show as "started" in db2pd
    -reorgs
    4. Issue a stop reorg
    db2pd -reorgs still shows reorg "started"
    
    5. Issue another stop:
    you get
    SQL2219N The specified INPLACE table reorganization action on
    table
    "DB2INST3.TEST_REORG" is not allowed on one or more nodes.
    Reason code:
    "11".
    11 There is no table reorganization to PAUSE or STOP.
    
    Would expect reason code "10"
    

Problem conclusion

  • First fixed in DB2 UDB Version 8.2, FixPak 15
    

Temporary fix

Comments

APAR Information

  • APAR number

    IY89415

  • Reported component name

    DB2 UDB PREM SU

  • Reported component ID

    5724I9800

  • Reported release

    820

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2006-09-14

  • Closed date

    2007-09-27

  • Last modified date

    2023-07-25

  • 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 UDB ESE HP-

  • Fixed component ID

    5765F4103

Applicable component levels

[{"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":"820","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
25 July 2023