home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC11 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

Informix - Problem description

Problem IT03514 Status: Closed

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

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem 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
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* users using last committed in 12.10                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IDS-12.10.xC5                                      * 
****************************************************************
Local Fix:
Solution
Problem Fixed In IDS-12.10.xC5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
31.07.2014
16.10.2015
16.10.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
12.10.xC4.W1 FixList
12.10.xC5 FixList
12.10.xC5.W1 FixList