IBM Support

IT03514: ASSERT FAILED ROWALTER: PTOCOPYVC: COLLEN (X) > MAX_VC_LEN (Y) FOLLOWED BY ASSERT FAILED PHYSICAL_SCAN: DECOMPRESS_ROW

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

  • If using compression on a table with varchars, and then doing an
    in place alter of the table, it's possible if readers are
    querying the table using committed read last committed while the
    table is being updated that the above assertion failures are
    possible for the sessions reading the table.
    
    The stack for the 2 assertions (for the rowalter):
    
    affail_interface
    rowalter
    rsseqscan_read
    fmseqscan_read
    readseq_batch
    gettupl
    scan_next
    next_row
    get_first_row_from_producer
    group_open
    prepselect
    open_cursor
    sql_open
    sq_open
    sqmain
    
    For the decompress row:
    
    affail_interface
    rsseqscan_read
    fmseqscan_read
    readseq_batch
    gettupl
    scan_next
    next_row
    get_first_row_from_producer
    group_open
    prepselect
    open_cursor
    sql_open
    sq_open
    sqmain
    
    Again for this to occur, the table being queried needs to be
    using compression, contain varchars, and have some in place
    alter being performed on it which would alter the rows size.
    Then the users querying the table need to be using committed
    read last committed isolation level.
    
    If the table is not using compression you can see the 2
    following types of assertion failures instead:
    
    13:23:07  Assert Failed: physical_scan: corrupted rowid = 1ce01,
    partnum = 100102
    
    or
    
    08:00:52  Assert Failed: construct_row: deleted rowid = 41c,
    partnum = 100102
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * users using last committed in 12.10                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Update to IDS-12.10.xC5                                      *
    ****************************************************************
    

Problem conclusion

  • Problem Fixed In IDS-12.10.xC5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT03514

  • Reported component name

    INFORMIX SERVER

  • Reported component ID

    5725A3900

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-31

  • Closed date

    2015-10-16

  • Last modified date

    2015-10-16

  • 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

    INFORMIX SERVER

  • Fixed component ID

    5725A3900

Applicable component levels

  • RA10 PSN

       UP

  • RA10 PSY

       UP

  • RB10 PSN

       UP

  • RB10 PSY

       UP

  • RB50 PSN

       UP

  • RB50 PSY

       UP

  • RB70 PSN

       UP

  • RB70 PSY

       UP

  • RC10 PSN

       UP

  • RC10 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"C10","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
16 October 2015