Scheduler error message
On IDS 11.50.FC4 (Red Hat 5), the online.log repeatedly showed SCHAPI errors -206 (table mon_syssqltrace not in database) and -111 from the 'Save SQL Trace' sensor, and the poster couldn't find the table's schema. One reply guessed OAT created it; the working answer came from Edcel Barcena: the schema is inside the sysadmin stored procedure sql_showsnap (view with dbschema -d sysadmin -f sql_showsnap -ss), which should create four tables on first run but stops after mon_syssqltrace_info. Creating the missing mon_syssqltrace, mon_syssqltrace_hvar and mon_syssqltrace_iter tables by hand fixed it, as the poster confirmed.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
IDS 11.50 FC4 on Redhat Enterprise 5 I'm seeing the following in my online.log file 01/13/10 09:15:00 SCHAPI: Error -206 The specified table (mon_syssqltrace) is not in the database. 01/13/10 09:15:00 SCHAPI: Type: SENSOR, Name: Save SQL Trace, Location: NULL. 01/13/10 09:15:00 SCHAPI: Error -111 ISAM error: no record found. 01/13/10 09:15:00 SCHAPI: Type: SENSOR, Name: Save SQL Trace, Location: NULL. Obviously this is related to the SQLTRACE feature. I've starting using the OAT recently. I'm pretty sure that this table is supposed to be in the sysadmin database, but I can't find a schema for it. Can somebody please point me in the right direction?
It´s certainly a table created on the installation of OAT, because I didn´t found it here on the sysadmin creation scripts. You could just try to enter on the OAT install homepage again, and that should work fine. Regards. Alexandre Marini Tecnologia da Informação - DBA SEFAZ-MS / SGI-UIMP / Sistemas IBM-Informix IIUG Member <http://www.iiug.org>; jgedyedba@teleformix.com escreveu: > IDS 11.50 FC4 on Redhat Enterprise 5 > > I'm seeing the following in my online.log file > > 01/13/10 09:15:00 SCHAPI: Error -206 The specified table > (mon_syssqltrace) is not in the database. > 01/13/10 09:15:00 SCHAPI: Type: SENSOR, Name: Save SQL Trace, Location: > NULL. > 01/13/10 09:15:00 SCHAPI: Error -111 ISAM error: no record found. > 01/13/10 09:15:00 SCHAPI: Type: SENSOR, Name: Save SQL Trace, Location: > NULL. > > Obviously this is related to the SQLTRACE feature. I've starting using > the OAT recently. I'm pretty sure that this table is supposed to be in > the sysadmin database, but I can't find a schema for it. Can somebody > please point me in the right direction? > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > > >
Are you sure that it gets created with the installation of OAT? If that's the case, I'll need to install OAT on every machine with an engine. I installed OAT on a central machine and then use that to connect to machines/engines. -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Alexandre Marini Sent: Wednesday, January 13, 2010 10:07 AM To: ids@iiug.org Subject: Re: Scheduler error message [18663] It´s certainly a table created on the installation of OAT, because I didn´t found it here on the sysadmin creation scripts. You could just try to enter on the OAT install homepage again, and that should work fine. Regards. Alexandre Marini Tecnologia da Informação - DBA SEFAZ-MS / SGI-UIMP / Sistemas IBM-Informix IIUG Member <http://www.iiug.org>; jgedyedba@teleformix.com escreveu: > IDS 11.50 FC4 on Redhat Enterprise 5 > > I'm seeing the following in my online.log file > > 01/13/10 09:15:00 SCHAPI: Error -206 The specified table > (mon_syssqltrace) is not in the database. > 01/13/10 09:15:00 SCHAPI: Type: SENSOR, Name: Save SQL Trace, Location: > NULL. > 01/13/10 09:15:00 SCHAPI: Error -111 ISAM error: no record found. > 01/13/10 09:15:00 SCHAPI: Type: SENSOR, Name: Save SQL Trace, Location: > NULL. > > Obviously this is related to the SQLTRACE feature. I've starting using > the OAT recently. I'm pretty sure that this table is supposed to be in > the sysadmin database, but I can't find a schema for it. Can somebody > please point me in the right direction? > > > **************************************************************************** *** > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum.
You can find the schema in a function called "sql_showsnap" in the sysadmin
database. Run "dbschema -d sysadmin -f sql_showsnap -ss". This SP is executed
when the Save SQL Trace task starts and is suppose to create 4 tables in
sysadmin on it's first run but somehow bails out after creating the first
table, mon_syssqltrace_info. Just create the rest of the tables manually and
it should be ok.
Regards,
Edcel
> To: ids@iiug.org
> From: jgedyedba@teleformix.com
> Subject: RE: Scheduler error message [18674]
> Date: Wed, 13 Jan 2010 16:48:50 -0500
>
> Are you sure that it gets created with the installation of OAT? If that's
> the case, I'll need to install OAT on every machine with an engine. I
> installed OAT on a central machine and then use that to connect to
> machines/engines.
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Alexandre Marini
> Sent: Wednesday, January 13, 2010 10:07 AM
> To: ids@iiug.org
> Subject: Re: Scheduler error message [18663]
>
> It´s certainly a table created on the installation of OAT, because I didn´t
> found it here on the sysadmin creation scripts.
> You could just try to enter on the OAT install homepage again, and that
> should work fine.
>
> Regards.
>
> Alexandre Marini
>
> Tecnologia da Informação - DBA
>
> SEFAZ-MS / SGI-UIMP / Sistemas IBM-Informix
>
> IIUG Member
>
> <http://www.iiug.org>;
>
> jgedyedba@teleformix.com escreveu:
> > IDS 11.50 FC4 on Redhat Enterprise 5
> >
> > I'm seeing the following in my online.log file
> >
> > 01/13/10 09:15:00 SCHAPI: Error -206 The specified table
> > (mon_syssqltrace) is not in the database.
> > 01/13/10 09:15:00 SCHAPI: Type: SENSOR, Name: Save SQL Trace, Location:
> > NULL.
> > 01/13/10 09:15:00 SCHAPI: Error -111 ISAM error: no record found.
> > 01/13/10 09:15:00 SCHAPI: Type: SENSOR, Name: Save SQL Trace, Location:
> > NULL.
> >
> > Obviously this is related to the SQLTRACE feature. I've starting using
> > the OAT recently. I'm pretty sure that this table is supposed to be in
> > the sysadmin database, but I can't find a schema for it. Can somebody
> > please point me in the right direction?
> >
> >
> >
> ****************************************************************************
> ***
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
> >
> >
>
> ****************************************************************************
> ***
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
I´m sorry, I just said I think it´s not created by the database engine, because it´s not on the sysadmin scripts. I didn´t find the creation command anywhere here. Did someone else??? Alexandre Marini Tecnologia da Informação - DBA SEFAZ-MS / SGI-UIMP / Sistemas IBM-Informix IIUG Member <http://www.iiug.org>; Jamie Gedye escreveu: > Are you sure that it gets created with the installation of OAT? If that's > the case, I'll need to install OAT on every machine with an engine. I > installed OAT on a central machine and then use that to connect to > machines/engines. > > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of > Alexandre Marini > Sent: Wednesday, January 13, 2010 10:07 AM > To: ids@iiug.org > Subject: Re: Scheduler error message [18663] > > It´s certainly a table created on the installation of OAT, because I didn´t > found it here on the sysadmin creation scripts. > You could just try to enter on the OAT install homepage again, and that > should work fine. > > Regards. > > Alexandre Marini > > Tecnologia da Informação - DBA > > SEFAZ-MS / SGI-UIMP / Sistemas IBM-Informix > > IIUG Member > > <http://www.iiug.org>; > > jgedyedba@teleformix.com escreveu: > >> IDS 11.50 FC4 on Redhat Enterprise 5 >> >> I'm seeing the following in my online.log file >> >> 01/13/10 09:15:00 SCHAPI: Error -206 The specified table >> (mon_syssqltrace) is not in the database. >> 01/13/10 09:15:00 SCHAPI: Type: SENSOR, Name: Save SQL Trace, Location: >> NULL. >> 01/13/10 09:15:00 SCHAPI: Error -111 ISAM error: no record found. >> 01/13/10 09:15:00 SCHAPI: Type: SENSOR, Name: Save SQL Trace, Location: >> NULL. >> >> Obviously this is related to the SQLTRACE feature. I've starting using >> the OAT recently. I'm pretty sure that this table is supposed to be in >> the sysadmin database, but I can't find a schema for it. Can somebody >> please point me in the right direction? >> >> >> >> > **************************************************************************** > *** > >> Forum Note: Use "Reply" to post a response in the discussion forum. >> >> >> >> >> > > **************************************************************************** > *** > Forum Note: Use "Reply" to post a response in the discussion forum. > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > >
This was it. The sysadmin database already had mon_syssqltrace_info in it,
but I had to create mon_syssqltrace_hvar, mon_syssqltrace_iter, and
mon_syssqltrace
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Edcel
Barcena
Sent: Wednesday, January 13, 2010 6:35 PM
To: ids@iiug.org
Subject: RE: Scheduler error message [18675]
You can find the schema in a function called "sql_showsnap" in the sysadmin
database. Run "dbschema -d sysadmin -f sql_showsnap -ss". This SP is
executed when the Save SQL Trace task starts and is suppose to create 4
tables in sysadmin on it's first run but somehow bails out after creating
the first table, mon_syssqltrace_info. Just create the rest of the tables
manually and it should be ok.
Regards,
Edcel
> To: ids@iiug.org
> From: jgedyedba@teleformix.com
> Subject: RE: Scheduler error message [18674]
> Date: Wed, 13 Jan 2010 16:48:50 -0500
>
> Are you sure that it gets created with the installation of OAT? If
> that's the case, I'll need to install OAT on every machine with an
> engine. I installed OAT on a central machine and then use that to
> connect to machines/engines.
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
> Alexandre Marini
> Sent: Wednesday, January 13, 2010 10:07 AM
> To: ids@iiug.org
> Subject: Re: Scheduler error message [18663]
>
> It´s certainly a table created on the installation of OAT, because I
> didn´t found it here on the sysadmin creation scripts.
> You could just try to enter on the OAT install homepage again, and
> that should work fine.
>
> Regards.
>
> Alexandre Marini
>
> Tecnologia da Informação - DBA
>
> SEFAZ-MS / SGI-UIMP / Sistemas IBM-Informix
>
> IIUG Member
>
> <http://www.iiug.org>;
>
> jgedyedba@teleformix.com escreveu:
> > IDS 11.50 FC4 on Redhat Enterprise 5
> >
> > I'm seeing the following in my online.log file
> >
> > 01/13/10 09:15:00 SCHAPI: Error -206 The specified table
> > (mon_syssqltrace) is not in the database.
> > 01/13/10 09:15:00 SCHAPI: Type: SENSOR, Name: Save SQL Trace, Location:
> > NULL.
> > 01/13/10 09:15:00 SCHAPI: Error -111 ISAM error: no record found.
> > 01/13/10 09:15:00 SCHAPI: Type: SENSOR, Name: Save SQL Trace, Location:
> > NULL.
> >
> > Obviously this is related to the SQLTRACE feature. I've starting
> > using the OAT recently. I'm pretty sure that this table is supposed
> > to be in the sysadmin database, but I can't find a schema for it.
> > Can somebody please point me in the right direction?
> >
> >
> >
> **********************************************************************
> ******
> ***
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
> >
> >
>
> **********************************************************************
> ******
> ***
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
****************************************************************************
***
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
****************************************************************************
***
Forum Note: Use "Reply" to post a response in the discussion forum.