upgrade from 7.31 to 9.2
A user wanted HPL's command-line onpladm, so attempted an in-place upgrade of IDS 7.31 to 9.21FC7, but conversion failed at the buildsmi/sysmaster build stage with ISAM error -103 (illegal key descriptor) and later an assertion failure in the buffer manager during conversion of the database tablespace. Replies said a column named 'item' (a 9.x keyword) would not block the upgrade, suggested running oncheck -cDI to check for corruption, noted 7.x and 9.2 use different key-descriptor structures (indexes should be flagged during conversion), and urged targeting a much newer release instead of 9.2. Another poster asked whether the attempt was on production or a copied instance and how the chunks were copied. No resolution is recorded in the thread.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
HI,
IDS7.31 has ipload but haven't the onpladm,I want to use the HPL command line
onpladm, so I try to upgrade from 7.31 to 9.2 using in-place upgrade.
When I doing the upgrade using oninit, ids report below errors when running
buildsmi.
finderr 103
-103 ISAM error: illegal key descriptor (too many parts or too long).
The ISAM processor has been given an invalid key descriptor. For C-ISAM
programs, review the key descriptor. Each key descriptor has a maximum
of 8 parts and 120 characters. If the error recurs, please refer to the
Appendix entitled "Trapping Errors" in your Administrator's Guide to
acquire additional diagnostics. Contact Informix Technical Support
with the diagnostic information.
How to fix this problem?
the application use one word 'item' as a columne name in the 7.31 database,but
'item' is a keyword in IDS9.21.
Do anybody know whether the 'item' keyworkd affect the upgrade?
Any suggestion would be appreciated.
Using a keyword in a column name should not prevent an in-place upgrade,
no. It may make it awkward to construct some queries. If you are not
careful some existing queries may return unexpected results or return
errors, but otherwise, no big deal.
Art
Art S. Kagel, Principal Consultant
ASK Database Management
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on the IIUG, nor any other organization with which I am
associated either explicitly, implicitly, or by inference. Neither do
those opinions reflect those of other individuals affiliated with any
entity with which I am affiliated nor those of the entities themselves.
On Mon, Jun 16, 2014 at 10:20 AM, CHUAN LU <luchuan@cn.ibm.com> wrote:
> HI,
>
> IDS7.31 has ipload but haven't the onpladm,I want to use the HPL command
> line
> onpladm, so I try to upgrade from 7.31 to 9.2 using in-place upgrade.
>
> When I doing the upgrade using oninit, ids report below errors when running
> buildsmi.
>
> finderr 103
> -103 ISAM error: illegal key descriptor (too many parts or too long).
>
> The ISAM processor has been given an invalid key descriptor. For C-ISAM
> programs, review the key descriptor. Each key descriptor has a maximum
> of 8 parts and 120 characters. If the error recurs, please refer to the
> Appendix entitled "Trapping Errors" in your Administrator's Guide to
> acquire additional diagnostics. Contact Informix Technical Support
> with the diagnostic information.
>
> How to fix this problem?
> the application use one word 'item' as a columne name in the 7.31
> database,but
> 'item' is a keyword in IDS9.21.
>
> Do anybody know whether the 'item' keyworkd affect the upgrade?
>
> Any suggestion would be appreciated.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a1133d1e2b17c3c04fbf571b5
HI, Another question is how to fix the -103 error? do anybody has experience in this area? thanks for your time.
Have you run an "oncheck -cDI" lately? It may be that something has been
corrupted.
Art
Art S. Kagel, Principal Consultant
ASK Database Management
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on the IIUG, nor any other organization with which I am
associated either explicitly, implicitly, or by inference. Neither do
those opinions reflect those of other individuals affiliated with any
entity with which I am affiliated nor those of the entities themselves.
On Mon, Jun 16, 2014 at 11:58 AM, CHUAN LU <luchuan@cn.ibm.com> wrote:
> HI,
> Another question is how to fix the -103 error?
> do anybody has experience in this area?
>
> thanks for your time.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--089e013d177cbb8a9304fbf627a2
Are you sure you mean 9.20? That was released in 1998 or 1999, and has
been obsolete for over a decade. The more recent fix packs of IDS 7.31
much more recent than 9.20. You shouldn't be thinking of moving to a
version less than 11.50; you should be moving to 12.10.
On Mon, Jun 16, 2014 at 7:20 AM, CHUAN LU <luchuan@cn.ibm.com> wrote:
> HI,
>
> IDS7.31 has ipload but haven't the onpladm,I want to use the HPL command
> line
> onpladm, so I try to upgrade from 7.31 to 9.2 using in-place upgrade.
>
> When I doing the upgrade using oninit, ids report below errors when running
> buildsmi.
>
> finderr 103
> -103 ISAM error: illegal key descriptor (too many parts or too long).
>
> The ISAM processor has been given an invalid key descriptor. For C-ISAM
> programs, review the key descriptor. Each key descriptor has a maximum
> of 8 parts and 120 characters. If the error recurs, please refer to the
> Appendix entitled "Trapping Errors" in your Administrator's Guide to
> acquire additional diagnostics. Contact Informix Technical Support
> with the diagnostic information.
>
> How to fix this problem?
> the application use one word 'item' as a columne name in the 7.31
> database,but
> 'item' is a keyword in IDS9.21.
>
> Do anybody know whether the 'item' keyworkd affect the upgrade?
>
> Any suggestion would be appreciated.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Jonathan Leffler <jonathan.leffler@gmail.com> #include <disclaimer.h>
Guardian of DBD::Informix - v2013.0521 - http://dbi.perl.org
"Blessed are we who can laugh at ourselves, for we shall never cease to be
amused."
--001a11c1d9c01f4a2d04fbf644b9
On 06/16/14 15:20, CHUAN LU wrote:
> HI,
>
> IDS7.31 has ipload but haven't the onpladm,I want to use the HPL command line
> onpladm, so I try to upgrade from 7.31 to 9.2 using in-place upgrade.
>
> When I doing the upgrade using oninit, ids report below errors when running
> buildsmi.
>
> finderr 103
> -103 ISAM error: illegal key descriptor (too many parts or too long).
>
> The ISAM processor has been given an invalid key descriptor. For C-ISAM
> programs, review the key descriptor. Each key descriptor has a maximum
> of 8 parts and 120 characters. If the error recurs, please refer to the
> Appendix entitled "Trapping Errors" in your Administrator's Guide to
> acquire additional diagnostics. Contact Informix Technical Support
> with the diagnostic information.
>
> How to fix this problem?
> the application use one word 'item' as a columne name in the 7.31
database,but
> 'item' is a keyword in IDS9.21.
>
> Do anybody know whether the 'item' keyworkd affect the upgrade?
>
> Any suggestion would be appreciated.
>
IDS 7.31 and 9.2(1) have a different key descriptor structure.
Normally an in place upgrade should mark indexes created with 7.x with a
special flag so that the 9.2 engine doesn't later get confused.
It could very well be that the in place upgrade process has not completed
properly - although buildsmi should be dropping and recreating the sysmaster
database anyhow.
In all honesty - without seeing a bit more diagnostic information, it's
impossible to say what's happening.
Also, as Jonathan as mentioned - 9.2 is 15 years old and 9.21 not much newer.
If you don't have access to a more recent engine, you are better off with 7.31
if, you have 7.31.UDx (x being a high single digit).
Next thing you are going to tell us is that you are on Sco Unix or HP-UX 10.01?
--
Ciao,
Marco
______________________________________________________________________________
Marco Greco /UK /IBM Standard disclaimers apply!
Structured Query Scripting Language http://www.4glworks.com/sqsl.htm
4glworks http://www.4glworks.com
Informix on Linux http://www.4glworks.com/ifmxlinux.htm
hi,
The target database version is ids11.7 on Suse Linux or Power 740. The
custonmer haven't decide now.
below are the AF file when doing the conversion from ids7.31FD1 to IDS9.21FC7.
17:18:24 Rowid 0x201 not found for delete in partnum 100002, key 1
treep
0700000400e37c00: 07000000 083a5fd8 00000001 2ec6beaa .....:_. ........
0700000400e37c10: 00010012 00007d00 ......}.
page addr stamp slots flag type frptr frcnt next prev
7000000294e7000 10449c 784776874 3 b0 BTREE 93 3987 0 0
slot ptr len flg
1 70 23 0
2 24 23 0
3 47 23 0
KEY: :
Node 1 Prev 0 Next 0
KEY:dzppt_srv :
Rowids: 208
KEY:sysmaster :
Rowids: 201
KEY:sysutils :
Rowids: 202
----------------------------------------------------------------------
17:18:24 bf_onwtlist: already buffer owner
buffer header
07000000083a5fd8: 00000001 00000000 00000000 00000000 ........ ........
07000000083a5fe8: 07000000 024d8fb0 07000000 024d8fb0 .....M.. .....M..
07000000083a5ff8: 07000000 0836b058 07000000 08358f58 .....6.X .....5.X
07000000083a6008: 00000802 00000001 00000004 00000000 ........ ........
07000000083a6018: 07000004 000ad7e0 00000000 00000000 ........ ........
07000000083a6028: 00000000 00000080 00000000 00100002 ........ ........
07000000083a6038: 00000001 00000001 00000000 2ecb0899 ........ ........
07000000083a6048: 00000000 ffffffff 0010449c 00000001 ........ ..D.....
07000000083a6058: 07000000 294e7000 ....)Np.
page header
07000000294e7000: 0010449c 2ec6beaa 000300b0 005d0f93 ..D..... .....]..
07000000294e7010: 00000000 00000000 ........
17:18:24
17:18:24 Informix Dynamic Server 2000 Version 9.21.FC7 Software Serial Number
AAB#J435865
17:18:24 Assert Failed: Fatal Error In Buffer Manager
17:18:24 Who: Session(10, informix@s85dnt, 0, 959592)
Thread(29, convert, 7000004000ad7e0, 1)
File: rsbuff.c Line: 109
17:18:24 Results: Dynamic Server 2000 must abort
17:18:24 Action: Reinitialize shared memory
17:18:24 Stack for thread: 29 convert
base: 0x0700000400e29000
len: 69632
pc: 0x000000010003566c
tos: 0x0700000400e355b0
state: running
vp: 1
0x00000000000357c4 (oninit)afstack (0x10005750, 0x438e, 0xe357c8, 0xf0b0, 0x0,
0x0, 0x93bf7001, 0x0)
0x0000000000036b48 (oninit)afhandler(0x0, 0x100281ac, 0xca8238, 0xca8280, 0x0,
0x0, 0x100281cc, 0x0)
0x00000000002dc818 (oninit)bf_fatalerr(0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
0x00000000002d74f4 (oninit)bf_onwtlist(0xe35f20, 0x0, 0xe35f20, 0x0, 0x0, 0x0,
0x0, 0x0)
0x00000000002dcb80 (oninit)bf_bfwait(0xe36208, 0x1, 0x18f3a0, 0x18f420,
0x18f360, 0xffffffff, 0x51eb851f, 0x8440)
0x00000000002dda6c (oninit)buffget (0x1, 0x10, 0x0, 0x1, 0xadd8c, 0x0,
0xffffffff, 0x10008)
0x0000000000357644 (oninit)btcurrent(0xe36c58, 0x3d0, 0x7, 0x0, 0xe36290, 0x0,
0x101beb18, 0x0)
0x0000000000246eb0 (oninit)find_page(0x101beb18, 0x0, 0x101be1c8, 0x100002,
0x100002, 0x0, 0x0, 0x0)
0x000000000024c944 (oninit)rsread (0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
0x000000000005e5d4 (oninit)dbstabidxname_long(0x362ec, 0x294e7ff0, 0x100e6c68,
0x101be268, 0x100e6c60, 0x100e6c58, 0x100e6c50, 0x294e7ffe)
0x0000000000062d5c (oninit)dbstabidxname(0x101d1a48, 0xc026a0, 0x201,
0x100002, 0x1, 0x2900, 0x93bf7001, 0x0)
0x000000000033d274 (oninit)btdelitem(0xff3028, 0x40, 0x101be1c8, 0x61, 0x0,
0x101beb18, 0xe37e30, 0x8030)
0x00000000002fbaf0 (oninit)rew_keys(0xe38650, 0x201, 0x0, 0x201, 0xe38510,
0xff2420, 0x2ff394, 0x0)
0x00000000002fd03c (oninit)rewrecord(0x0, 0xff3028, 0x0, 0x0, 0xe38690,
0xe38740, 0x101d16e8, 0x0)
0x00000000002ff5d4 (oninit)rsrewrec(0x101d1a48, 0xef10e0, 0xc2c720, 0xd0b0,
0x0, 0x2900, 0x93bf7001, 0x0)
0x00000000006b9df0 (oninit)convert_database_tablespace(0x0, 0x0, 0x0, 0x0,
0x0, 0x0, 0x0, 0x0)
0x00000000006c96a4 (oninit)convert (0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
0x00000000008aa16c (oninit)startup (0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
0x0000000000000000
---------------------------------
Begin System Alarm Program Output
---------------------------------
Assertion Failure Type: CRASH
Host Name: s85dnt
Database Server Name: diccyw_sec
Time of failure: Mon Jun 16 17:18:25 CDT 2014
AF file: /tmp/af.4056d30
Shared memory file: None
System Blocking: OFF
===========------------- - - - - - -
tail -100 /app/ifmx9/online.log:
15:21:12 Informix Dynamic Server 2000 Stopped.
17:17:53 Informix Dynamic Server 2000 Started.
17:18:01 Dynamically allocated new virtual shared memory segment (size
2096736KB)
17:18:01 Dynamically allocated new virtual shared memory segment (size
2096736KB)
17:18:01 Dynamically allocated new virtual shared memory segment (size
2096736KB)
17:18:01 Dynamically allocated new virtual shared memory segment (size
2096736KB)
17:18:01 Dynamically allocated new virtual shared memory segment (size
2096736KB)
17:18:01 Dynamically allocated new virtual shared memory segment (size
1989888KB)
17:18:01 Dynamically allocated new virtual shared memory segment (size
800000KB)
Mon Jun 16 17:18:08 2014
17:18:08 Event alarms enabled. ALARMPROG = '/app/ifmx9/etc/no_log.sh'
17:18:08 Booting Language <c> from module <>
17:18:08 Loading Module <CNULL>
17:18:08 Booting Language <builtin> from module <>
17:18:08 Loading Module <BUILTINNULL>
17:18:13 AIX MP latch code enabled
17:18:13 Requested shared memory segment size rounded from 1196KB to 1200KB
17:18:13 Dynamically allocated new message shared memory segment (size 1200KB)
17:18:13 Informix Dynamic Server 2000 Version 9.21.FC7 Software Serial Number
AAB#J435865
17:18:14 Conversion from version 7.3 Started
17:18:14 Informix Dynamic Server 2000 Initialized -- Shared Memory Initialized.
17:18:14 Physical Recovery Started at Page(1:289).
17:18:16 Physical Recovery Complete: 0 Pages Examined 0 Pages Restored.
17:18:16 Logical Recovery Started.
17:18:16 10 recovery worker threads will be started.
17:18:16 WARNING! Physical Log size 1000 is too small.
Physical Log overflows may occur during peak activity.
Recommended minimum Physical Log size is 20 times maximum
concurrent user threads.
17:18:18 Logical Recovery Complete.
0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks
17:18:19 Onconfig parameter MSGPATH modified from /home/informix/online.log to
/app/ifmx9/online.log.
17:18:19 Onconfig parameter LTAPEDEV modified from /tmp/ids.log to /dev/null.
17:18:19 Onconfig parameter DRLOSTFOUND modified from
/home/informix/etc/dr.lostfound to /app/ifmx9/etc/dr.lostfound.
17:18:19 Onconfig parameter ALARMPROGRAM modified from
/home/informix/etc/log_full.sh to /app/ifmx9/etc/no_log.sh.
17:18:20 Dataskip is now OFF for all dbspaces
17:18:24 Checkpoint Completed: duration was 3 seconds.
17:18:24 Checkpoint loguniq 15571, logpos 0x3018
17:18:24 On-Line Mode
17:18:24 Started the Conversion of the Database Tablespace
17:18:24 Building 'sysmaster' database ...
17:18:24 Assert Failed: Fatal Error In Buffer Manager
17:18:24 Informix Dynamic Server 2000 Version 9.21.FC7
17:18:24 Who: Session(10, informix@s85dnt, 0, 959592)
Thread(29, convert, 7000004000ad7e0, 1)
File: rsbuff.c Line: 109
17:18:24 Results: Dynamic Server
Hi, Is this being performed on the production 7.31 instance or is this being performed on a "copy" of the production 7.31 instance? If on a "copy" ... how did you "copy" the chunks and what was the state of the engine (i.e. online or offline?) JJ