Lots of SCHAPI errors

Posted in 2016

Summary

A user saw bursts of SCHAPI errors in the online log after moving to a newer Informix install: db_purge_tables tasks failing with -211 "Cannot read system catalog (sysprocedures)" and -103 "illegal key descriptor", plus an earlier AUS Evaluator failure on an unresolvable column. Art Kagel said this isn't a connectivity problem but a partially updated sysadmin database from the in-place migration (procedures updated, schema not), suggesting dropping and recreating sysadmin after saving site-specific settings. Andreas Legner asked about oncheck output and UTF8/GL_USEGLU as a -103 cause; the poster replied oncheck was clean, no UTF-8, GL_USEGLU=1. No confirmed fix is recorded.

Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.

Topics: General Discussion

R MICHAEL — Fri, 16 Dec 2016 16:43:04 — source: IIUG Forums & Mailing Lists

Hi everybody, We had some interruptions at a moment and when I checked the logs I saw lots of SCHAPI errors and couldn't figure it out if it's because of sort memory, bad tables or maybe bad queries. Onceck shows no errors. I uploaded some filtered logs. The instance is stable now. I assume that IDS couldn't accept connections when this happened and that's why the problem was raised. https://filehost.net/e4cdcea2f0e15234 https://filehost.net/0b255bb221f1724f Thanks.

↪ replying to R MICHAEL

Art Kagel — Fri, 16 Dec 2016 17:02:54 — source: IIUG Forums & Mailing Lists

Michael: I looked at your err2 file online. It looks like the AUS Evaluator is encountering a column (mongo_pam_auth) in some database that it cannot associate with any table. Very strange, but it's not a connectivity issue. The AUS Evaluator is failing. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com 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 Fri, Dec 16, 2016 at 11:43 AM, R MICHAEL <mboncalo@gmail.com> wrote: > Hi everybody, > > We had some interruptions at a moment and when I checked the logs I saw > lots > of SCHAPI errors and couldn't figure it out if it's because of sort memory, > bad tables or maybe bad queries. Onceck shows no errors. > I uploaded some filtered logs. > The instance is stable now. I assume that IDS couldn't accept connections > when > this happened and that's why the problem was raised. > > https://filehost.net/e4cdcea2f0e15234 > https://filehost.net/0b255bb221f1724f > > Thanks. > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --001a11423f32d3e7af0543c989be

↪ replying to Art Kagel

R MICHAEL — Tue, 20 Dec 2016 08:24:54 — source: IIUG Forums & Mailing Lists

Sorry, those were some older errors. The last ones are : 00:45:01 SCHAPI: [db_purge_tables 38-29122] Error -103 ISAM error: illegal key descriptor (too many parts or too long). 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX_ALLOW_NEWLINE('T') 00:45:01 SCHAPI: [db_purge_tables 38-29123] Error -211 Cannot read system catalog (sysprocedures). 00:45:01 SCHAPI: [db_purge_tables 38-29123] Error -103 ISAM error: illegal key descriptor (too many parts or too long). 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX_ALLOW_NEWLINE('T') 00:45:01 SCHAPI: [db_purge_tables 38-29125] Error -211 Cannot read system catalog (sysprocedures). 00:45:01 SCHAPI: [db_purge_tables 38-29125] Error -103 ISAM error: illegal key descriptor (too many parts or too long). 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX_ALLOW_NEWLINE('T') 00:45:01 SCHAPI: [db_purge_tables 38-29127] Error -211 Cannot read system catalog (sysprocedures). 00:45:01 SCHAPI: [db_purge_tables 38-29127] Error -103 ISAM error: illegal key descriptor (too many parts or too long). 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX_ALLOW_NEWLINE('T') 00:45:01 SCHAPI: [db_purge_tables 38-29128] Error -211 Cannot read system catalog (sysprocedures). 00:45:01 SCHAPI: [db_purge_tables 38-29128] Error -103 ISAM error: illegal key descriptor (too many parts or too long). 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX_ALLOW_NEWLINE('T') 00:45:01 SCHAPI: [db_purge_tables 38-29129] Error -211 Cannot read system catalog (sysprocedures). 00:45:01 SCHAPI: [db_purge_tables 38-29129] Error -103 ISAM error: illegal key descriptor (too many parts or too long). Here is the problem. But they lasted about 35 seconds.

↪ replying to R MICHAEL

Art Kagel — Tue, 20 Dec 2016 11:15:45 — source: IIUG Forums & Mailing Lists

It looks like you did a recent upgrade and sysadmin was only partially updated. You might try dropping it and recreating it. Don't forget to save and restore site specific configuration changes and procedures. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com 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 Tue, Dec 20, 2016 at 3:24 AM, R MICHAEL <mboncalo@gmail.com> wrote: > Sorry, those were some older errors. The last ones are : > 00:45:01 SCHAPI: [db_purge_tables 38-29122] Error -103 ISAM error: illegal > key > descriptor (too many parts or too long). > > 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX_ALLOW_NEWLINE('T') > 00:45:01 SCHAPI: [db_purge_tables 38-29123] Error -211 Cannot read system > catalog (sysprocedures). > > 00:45:01 SCHAPI: [db_purge_tables 38-29123] Error -103 ISAM error: illegal > key > descriptor (too many parts or too long). > > 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX_ALLOW_NEWLINE('T') > 00:45:01 SCHAPI: [db_purge_tables 38-29125] Error -211 Cannot read system > catalog (sysprocedures). > > 00:45:01 SCHAPI: [db_purge_tables 38-29125] Error -103 ISAM error: illegal > key > descriptor (too many parts or too long). > > 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX_ALLOW_NEWLINE('T') > 00:45:01 SCHAPI: [db_purge_tables 38-29127] Error -211 Cannot read system > catalog (sysprocedures). > > 00:45:01 SCHAPI: [db_purge_tables 38-29127] Error -103 ISAM error: illegal > key > descriptor (too many parts or too long). > > 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX_ALLOW_NEWLINE('T') > 00:45:01 SCHAPI: [db_purge_tables 38-29128] Error -211 Cannot read system > catalog (sysprocedures). > > 00:45:01 SCHAPI: [db_purge_tables 38-29128] Error -103 ISAM error: illegal > key > descriptor (too many parts or too long). > > 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX_ALLOW_NEWLINE('T') > 00:45:01 SCHAPI: [db_purge_tables 38-29129] Error -211 Cannot read system > catalog (sysprocedures). > > 00:45:01 SCHAPI: [db_purge_tables 38-29129] Error -103 ISAM error: illegal > key > descriptor (too many parts or too long). > Here is the problem. But they lasted about 35 seconds. > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --089e0122ae9a978cd30544152755

↪ replying to Art Kagel

R MICHAEL — Tue, 20 Dec 2016 12:27:41 — source: IIUG Forums & Mailing Lists

I didn't upgrade the instance, a newer version ifx instance was installed and used the same database.

↪ replying to R MICHAEL

Art Kagel — Tue, 20 Dec 2016 12:31:50 — source: IIUG Forums & Mailing Lists

That's an upgrade. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com 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 Tue, Dec 20, 2016 at 7:27 AM, R MICHAEL <mboncalo@gmail.com> wrote: > I didn't upgrade the instance, a newer version ifx instance was installed > and > used the same database. > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --001a11423f32c6c598054416378f

↪ replying to Art Kagel

R MICHAEL — Tue, 20 Dec 2016 12:42:32 — source: IIUG Forums & Mailing Lists

I didn't upgrade the instance, a newer version ifx instance was installed and used the same database.

↪ replying to R MICHAEL

Keith Simmons — Tue, 20 Dec 2016 13:03:42 — source: IIUG Forums & Mailing Lists

If you are trying to say that a new version of Informix was installed and pointed at an existing, running instance, then you have serious issues both with your understanding of the Informix Database software and up grading procedures, and with the database you are running and the data within it. I would suggest you urgently need to shutdown your instance, restore the last archive before the new version was installed (you did take one didn't you !!) using the old version of software and then check everything runs as expected. Then RTFM with regard upgrading Informix to a newer version. If you have processed too much work into the database that a restore is not an option then you will probably need support from IBM (assuming you've paid for that !!) On 20 December 2016 at 12:42, R MICHAEL <mboncalo@gmail.com> wrote: > I didn't upgrade the instance, a newer version ifx instance was installed > and > used the same database. > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --001a113676542a5d2b054416a921

↪ replying to Keith Simmons

R MICHAEL — Tue, 20 Dec 2016 13:28:09 — source: IIUG Forums & Mailing Lists

Sorry for the confusion.The upgrade I did is named "In-place migration", installed a newer version in another location, copied the configuration files, added or modified needed parameters and started the new instance.After the instance was started the database should be converted to the new version and probably something happened to sysadmin like Kagel said.

↪ replying to R MICHAEL

Andreas Legner — Tue, 20 Dec 2016 19:54:20 — source: IIUG Forums & Mailing Lists

What's oncheck (-cc, -cDI) saying for sysadmin db? Using/used UTF8 with any of your databases? Absence / presence of=20 GL=5FUSEGLU a factor possibly? Just asking as this typically causes -103 o= n=20 system tables. HTH, Andreas From: "R MICHAEL" <mboncalo@gmail.com> To: ids@iiug.org Date: 20.12.2016 09:25 Subject: Re: Lots of SCHAPI errors [38341] Sent by: ids-bounces@iiug.org Sorry, those were some older errors. The last ones are :=20 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29122] Error -103 ISAM error: ille= gal=20 key=20 descriptor (too many parts or too long).=20 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX=5FALLOW=5FNEWLINE('T'= )=20 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29123] Error -211 Cannot read syst= em=20 catalog (sysprocedures).=20 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29123] Error -103 ISAM error: ille= gal=20 key=20 descriptor (too many parts or too long).=20 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX=5FALLOW=5FNEWLINE('T'= )=20 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29125] Error -211 Cannot read syst= em=20 catalog (sysprocedures).=20 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29125] Error -103 ISAM error: ille= gal=20 key=20 descriptor (too many parts or too long).=20 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX=5FALLOW=5FNEWLINE('T'= )=20 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29127] Error -211 Cannot read syst= em=20 catalog (sysprocedures).=20 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29127] Error -103 ISAM error: ille= gal=20 key=20 descriptor (too many parts or too long).=20 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX=5FALLOW=5FNEWLINE('T'= )=20 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29128] Error -211 Cannot read syst= em=20 catalog (sysprocedures).=20 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29128] Error -103 ISAM error: ille= gal=20 key=20 descriptor (too many parts or too long).=20 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE IFX=5FALLOW=5FNEWLINE('T'= )=20 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29129] Error -211 Cannot read syst= em=20 catalog (sysprocedures).=20 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29129] Error -103 ISAM error: ille= gal=20 key=20 descriptor (too many parts or too long).=20 Here is the problem. But they lasted about 35 seconds.=20 ***************************************************************************= ****=20 Forum Note: Use "Reply" to post a response in the discussion forum.=20

↪ replying to Andreas Legner

Art Kagel — Tue, 20 Dec 2016 19:58:15 — source: IIUG Forums & Mailing Lists

I don't think that it's a check problem. I think that the sysadmin just has an older schema. I've seen that from time-to-time. The stored procedures get changed but the schema's don't get altered during the upgrade. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com 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 Tue, Dec 20, 2016 at 2:54 PM, Andreas Legner <andreas.legner@de.ibm.com> wrote: > What's oncheck (-cc, -cDI) saying for sysadmin db? > > Using/used UTF8 with any of your databases? Absence / presence of=20 > GL=5FUSEGLU a factor possibly? Just asking as this typically causes -103 o= > n=20 > system tables. > > HTH, > Andreas > > From: "R MICHAEL" <mboncalo@gmail.com> > To: ids@iiug.org > Date: 20.12.2016 09:25 > Subject: Re: Lots of SCHAPI errors [38341] > Sent by: ids-bounces@iiug.org > > Sorry, those were some older errors. The last ones are :=20 > 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29122] Error -103 ISAM error: > ille= > gal=20 > key=20 > descriptor (too many parts or too long).=20 > > 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE > IFX=5FALLOW=5FNEWLINE('T'= > )=20 > 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29123] Error -211 Cannot read > syst= > em=20 > catalog (sysprocedures).=20 > > 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29123] Error -103 ISAM error: > ille= > gal=20 > key=20 > descriptor (too many parts or too long).=20 > > 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE > IFX=5FALLOW=5FNEWLINE('T'= > )=20 > 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29125] Error -211 Cannot read > syst= > em=20 > catalog (sysprocedures).=20 > > 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29125] Error -103 ISAM error: > ille= > gal=20 > key=20 > descriptor (too many parts or too long).=20 > > 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE > IFX=5FALLOW=5FNEWLINE('T'= > )=20 > 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29127] Error -211 Cannot read > syst= > em=20 > catalog (sysprocedures).=20 > > 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29127] Error -103 ISAM error: > ille= > gal=20 > key=20 > descriptor (too many parts or too long).=20 > > 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE > IFX=5FALLOW=5FNEWLINE('T'= > )=20 > 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29128] Error -211 Cannot read > syst= > em=20 > catalog (sysprocedures).=20 > > 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29128] Error -103 ISAM error: > ille= > gal=20 > key=20 > descriptor (too many parts or too long).=20 > > 00:45:01 SCHAPI: last statement EXECUTE PROCEDURE > IFX=5FALLOW=5FNEWLINE('T'= > )=20 > 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29129] Error -211 Cannot read > syst= > em=20 > catalog (sysprocedures).=20 > > 00:45:01 SCHAPI: [db=5Fpurge=5Ftables 38-29129] Error -103 ISAM error: > ille= > gal=20 > key=20 > descriptor (too many parts or too long).=20 > Here is the problem. But they lasted about 35 seconds.=20 > > ************************************************************ > ***************= > ****=20 > > Forum Note: Use "Reply" to post a response in the discussion forum.=20 > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --089e0122ae9a46a9b905441c7414

↪ replying to Andreas Legner

R MICHAEL — Wed, 21 Dec 2016 21:25:46 — source: IIUG Forums & Mailing Lists

no, we are not using. Oncheck has no errors.

↪ replying to Andreas Legner

R MICHAEL — Wed, 21 Dec 2016 21:41:11 — source: IIUG Forums & Mailing Lists

We're not using UTF-8 and GL_USEGLU is set to 1 . Oncheck has no errors.

Related threads

Backup

Glossary

IDS (Informix Dynamic Server)