Hello Heinz,
This problem is probably a defect of informix. It looks similar to what is described in the APAR below.
Commonly, Informix 12.10.xC4 and below are in use and last commited function is enabled.
In this state, AF occurs when an alter operation is performed on a compressed or uncompressed table.
IT04586: ASSERT FAILED: PHYSICAL_SCAN: DECOMPRESS_ROW, SOURCE = 0XXXXXXXX X, TARGET = 0XXXXXXXXX WHEN USELASTCOMMITTED "ALL" , COMPRESSION
https://www-01.ibm.com/support/docview.wss?uid=swg1IT04586IT03514: ASSERT FAILED ROWALTER: PTOCOPYVC: COLLEN (X) > MAX_VC_LEN (Y) FOLLOWED BY ASSERT FAILED PHYSICAL_SCAN: DECOMPRESS_ROW
https://www-01.ibm.com/support/docview.wss?uid=swg1IT03514If possible, I would recommend Informix to apply patch 12.10.xC5 or higher.
In this case, of course, it is recommended to ask IBM to open the case.
If that's hard to do, you might need to migrate your data to a new table.
------------------------------
SangGyu Jeong
Software Engineer
Infrasoft
Seoul Korea, Republic of
------------------------------
Original Message:
Sent: Fri February 07, 2020 07:35 AM
From: Heinz Weitkamp
Subject: IBM Informix Dynamic Server Version 12.10.UC4W1
Hi there,
operating system:
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 4We occasionally have the following problem with a database:
02/07/20 11:51:44 rowalter: PTOCOPYVC: collen (0xb4) > max_vc_len (0x33) (cmpoff: 0x22, uncmpoff 0x22
02/07/20 11:51:44 Assert Failed: physical_scan: decompress_row, source = 0x53c48174, target = 0x5a019018
02/07/20 11:51:44 IBM Informix Dynamic Server Version 12.10.UC4W1
02/07/20 11:51:44 Who: Session(3430799, jbosscod@srvms1appserver.intern.westfleisch.de,-1, 0x577c7c50)
Thread(3435541, sqlexec, 4eb69b58, 8)
File: rsseqscan.c Line: 1237
02/07/20 11:51:44 Results: Record not read
02/07/20 11:51:44 Action: Please notify IBM Informix Techical Support.
02/07/20 11:51:44 stack trace for pid 14419 written to /opt/informix/tmp/af.6ffd4129
02/07/20 11:51:44 See Also: /opt/informix/tmp/af.6ffd4129
02/07/20 11:51:48 uncompress_row: Column data length exceeds the maximum length
02/07/20 11:51:48 physical_scan: decompress_row, source = 0x53c48174, target = 0x5a019018
Not always, but the error message also caused the database to crash.
Does anyone have any experience with it.Thanks in advance for hintsGreeting
Heinz
------------------------------
Heinz Weitkamp
------------------------------
#Informix