ids dump
Posted in 2014
Topics: SQL Development & Query Writing, Error Codes & Troubleshooting, Logging & Checkpoints, Cloud, Docker & Containers, Versions, Editions & End-of-Life
Folks,
IDS11.50 FC8, RHEL 6.
What do you think of the following types of dump?
Thanks
Frank
[informix@franklin tmp]$ more af.2b238de3
10:30:59
10:30:59 IBM Informix Dynamic Server Version 11.50.FC8 Software Serial
Number AAA#B000000
10:30:59 Assert Failed: read_record: decompress_row, source =
0x0xb97d56f4, target = 0x0xc57350a8
10:30:59 Who: Session(133, bwishner@franklin, -1, 0xc2391848)
Thread(10043, sqlexec, c2358c88, 8)
File: rsread.c Line: 3637
10:30:59 Results: Record not read
10:30:59 Action: Please notify IBM Informix Technical Support.
10:30:59 Raw hex dump of stack located in /tmp/af.2b238de3.rawstk
10:30:59 Stack for thread: 10043 sqlexec
base: 0x00000000c6aa2000
len: 69632
pc: 0x00000000010c91d7
tos: 0x00000000c6aaf410
state: running
vp: 8
0x00000000010c91d7 (oninit) afstack
0x00000000010cb12c (oninit) afhandler
0x00000000010cb9e4 (oninit) affail_interface
0x0000000000b14dee (oninit) read_record
0x0000000000b1c37a (oninit) rsread
0x00000000011136d1 (oninit) fmread
0x000000000072d6df (oninit) gettupl
0x000000000073492a (oninit) scan_next
0x000000000075a0a0 (oninit) hjoin_next
0x0000000000752280 (oninit) sort_open
0x000000000073c55c (oninit) prepselect
0x00000000008b7c12 (oninit) open_cursor
0x00000000008ce808 (oninit) sql_open
0x00000000008ceb36 (oninit) sq_open
0x00000000009898c6 (oninit) sqmain
0x000000000114d347 (oninit) spawn_thread
0x000000000109a9bb (oninit) startup
10:30:59 See Also: /tmp/af.2b238de3, shmem.2b238de3.0
---------------------------------
Begin System Alarm Program Output
---------------------------------
Assertion Failure Type: FAILURE
Host Name: franklin
Database Server Name: nsofref_tcp
Time of failure: Tue Jul 1 10:30:59 UTC 2014
AF file: /tmp/af.2b238de3
Shared memory file: None
System Blocking: OFF
===========------------- - - - - - -
tail -100 /dbbackup/online_log/online_ref.log:
08:24:00 Checkpoint Completed: duration was 0 seconds.
08:24:00 Tue Jul 1 - loguniq 157304, logpos 0xa5c7018, timestamp:
0x5870ed1b Interval: 350949
08:24:00 Maximum server connections 8
08:24:00 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
0, Plog used 2, Llog used 2
08:39:00 Checkpoint Completed: duration was 0 seconds.
08:39:00 Tue Jul 1 - loguniq 157304, logpos 0xa5c9018, timestamp:
0x5870ed2e Interval: 350950
08:39:00 Maximum server connections 8
08:39:00 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
0, Plog used 2, Llog used 2
08:54:00 Checkpoint Completed: duration was 0 seconds.
08:54:00 Tue Jul 1 - loguniq 157304, logpos 0xa5cb018, timestamp:
0x5870ed41 Interval: 350951
08:54:00 Maximum server connections 8
08:54:00 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
0, Plog used 2, Llog used 2
09:09:00 Checkpoint Completed: duration was 0 seconds.
09:09:00 Tue Jul 1 - loguniq 157304, logpos 0xa5cd018, timestamp:
0x5870ed54 Interval: 350952
09:09:00 Maximum server connections 8
09:09:00 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
0, Plog used 2, Llog used 2
09:19:00 Checkpoint Completed: duration was 0 seconds.
09:19:00 Tue Jul 1 - loguniq 157304, logpos 0xa5d6018, timestamp:
0x5870edd2 Interval: 350953
09:19:00 Maximum server connections 8
09:19:00 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
0, Plog used 15, Llog used 9
09:24:00 Checkpoint Completed: duration was 0 seconds.
09:24:00 Tue Jul 1 - loguniq 157304, logpos 0xa5d8018, timestamp:
0x5870ede1 Interval: 350954
09:24:00 Maximum server connections 8
09:24:00 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
0, Plog used 2, Llog used 2
09:39:00 Checkpoint Completed: duration was 0 seconds.
09:39:00 Tue Jul 1 - loguniq 157304, logpos 0xa5da018, timestamp:
0x5870edf4 Interval: 350955
09:39:00 Maximum server connections 8
09:39:00 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
0, Plog used 2, Llog used 2
09:54:01 Checkpoint Completed: duration was 0 seconds.
09:54:01 Tue Jul 1 - loguniq 157304, logpos 0xa5dc018, timestamp:
0x5870ee07 Interval: 350956
09:54:01 Maximum server connections 8
09:54:01 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
0, Plog used 2, Llog used 2
10:09:01 Checkpoint Completed: duration was 0 seconds.
10:09:01 Tue Jul 1 - loguniq 157304, logpos 0xa5de018, timestamp:
0x5870ee1a Interval: 350957
10:09:01 Maximum server connections 8
10:09:01 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
0, Plog used 2, Llog used 2
10:19:01 Checkpoint Completed: duration was 0 seconds.
10:19:01 Tue Jul 1 - loguniq 157304, logpos 0xa5ec018, timestamp:
0x5870eec6 Interval: 350958
10:19:01 Maximum server connections 8
10:19:01 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
0, Plog used 23, Llog used 14
10:24:01 Checkpoint Completed: duration was 0 seconds.
10:24:01 Tue Jul 1 - loguniq 157304, logpos 0xa98d018, timestamp:
0x5871123f Interval: 350959
10:24:01 Maximum server connections 8
10:24:01 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
0, Plog used 408, Llog used 929
10:29:01 Checkpoint Completed: duration was 0 seconds.
10:29:01 Tue Jul 1 - loguniq 157304, logpos 0xad33018, timestamp:
0x587135d8 Interval: 350960
10:29:01 Maximum server connections 8
10:29:01 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked
0, Plog used 407, Llog used 934
10:30:59 Assert Failed: read_record: decompress_row, source =
0x0xb97d56f4, target = 0x0xc57350a8
10:30:59 IBM Informix Dynamic Server Version 11.50.FC8
10:30:59 Who: Session(133, bwishner@franklin, -1, 0xc2391848)
Thread(10043, sqlexec, c2358c88, 8)
File: rsread.c Line: 3637
10:30:59 Assert Failed: read_record: decompress_row, source =
0x0xb97d56f4, target = 0x0xc58740a8
10:30:59 Assert Failed: read_record: decompress_row, source =
0x0xb97d56f4, target = 0x0xc66fe0a8
10:30:59 IBM Informix Dynamic Server Version 11.50.FC8
10:30:59 IBM Informix Dynamic Server Version 11.50.FC8
10:30:59 Who: Session(134, bwishner@franklin, -1, 0xc238f958)
Thread(10044, sqlexec, c234feb0, 10)
File: rsread.c Line: 3637
10:30:59 Who: Session(131, bwishner@franklin, -1, 0xc238f010)
Thread(10041, sqlexec, c23562d0, 12)
File: rsread.c Line: 3637
10:30:59 Results: Record not read
10:30:59 Action: Please notify IBM Informix Technical Support.
10:30:59 stack trace for pid 25623 written to /tmp/af.2b218de3
10:30:59 Results: Record not read
10:30:59 Action: Please notify IBM Informix Technical Support.
10:30:59 stack trace for pid 25619 written to /tmp/af.2b238de3
10:30:59 Results: Record not read
10:30:59 Action: Please notify IBM Informix Technical Support.
10:30:59 stack trace for pid 25621 written to /tmp/af.2b248de3
10:30:59 See Also: /tmp/af.2b218de3, shmem.2b218de3.0
10:30:59 See Also: /tmp/af.2b238de3, shmem.2b238de3.0
10:30:59 See Also: /tmp/af.2b248de3, shmem.2b248de3.0
--001a11c30e222ab21704fd204d6e
google "informix read_record decompress row record not read" says ...
http://www-01.ibm.com/support/docview.wss?uid=swg1IC74521
Fixed in 11.50.FC9 ... whether that is your specific issue would be dependent
on a valid, definitive, repeatable test case.
You could check whether you do have in-place alters but that could be quite
tricky on a big production table ... oncheck -pT
Folks,
Need help!
IDS11.FC8, RHEL6.
This issue has given us a hard time. We need ALTER one big
table(160Millions rows ) in our Operational db.
From the following description , is it possible to alter the column type
from int to bigint by setting Dirty Read , or other read mode first ....?
Any other work around to get the ALTER done? ( IDS version upgrade is not
a option currently)
Thanks
Frank
IC74521: READ_RECORD: DECOMPRESS_ROW ASSERTION FAILURE SELECTING FROM A T
ABLE USING COMMITTED READ LAST COMMITTED ISOLATION LEVEL OPEN IN
APAR status
- Closed as program error.
Error description
-
If the table a session is querying has open in-place alters and
the session is using committed read last committed isolation
level, it can be possible to generate the following assertion
failure messages in the MSGPATH log file:
08:45:12 Assert Failed: read_record: decompress_row, source =
0x112416068, target = 0x112562710
08:45:12 IBM Informix Dynamic Server Version 11.50.FC7
08:45:12 Who: Session(77, testusr@testmachine, 2685,
1115861a8)
Thread(105, sqlexec, 1115485a8, 3)
File: rsread.c Line: 3634
08:45:12 Results: Record not read
-
-
On Tue, Jul 1, 2014 at 10:11 AM, JON RITSON <jonritson@sky.com> wrote:
> google "informix read_record decompress row record not read" says ...
>
> http://www-01.ibm.com/support/docview.wss?uid=swg1IC74521
>
> Fixed in 11.50.FC9 ... whether that is your specific issue would be
> dependent
> on a valid, definitive, repeatable test case.
>
> You could check whether you do have in-place alters but that could be quite
> tricky on a big production table ... oncheck -pT
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a113ac052c1947804fd40a084
Several approaches, but not enough information for real advice ...
1. Can you provide the full dbschema -ss of the table?
Checking things like indexes and referential constraints etc. etc.
2. Have you got "spare space" with at least the same as consumed by the
existing table (preferably more to allow for growth)
3. Could you confirm the actual version?
11.FC8 is not complete ...should be something like 11.70.FC8?? or 11.50.FC8??
There are several "options" if the later version (11.70.FC8 for example has
NOVALIDATE if rebuilding by creating a new RAW table, loading old to new,
rename existing to old and old to new etc. etc.
HTH
Related threads
- Fragmentation Fundamental Question
- LVARCHAR data type
- Re: SQL convert number into the date
- Re: Slow dbexport
- doubt about parameters (PDQ)