Re: Sysadmin Database Errors
The poster saw -214/-106 errors from Auto Update Statistics and wanted to drop and rebuild the sysadmin database, but the running dbScheduler and dbWorker threads held it, and restarting the server didn't help. Replies advised stopping the scheduler with EXECUTE FUNCTION task("scheduler shutdown"), then rebuilding with task/admin("reset sysadmin") (disconnecting from sysadmin first), and restarting with task("scheduler start"); John Miller noted reset sysadmin already does the shutdown/restart implicitly. The poster confirmed sysadmin was rebuilt and the threads restarted.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
We too have the -214 / 106 error messages in the log from Auto Statistics and tried to drop the sysadmin database as the first step to rebuild but can't get exclusive access. There is a dbSchedu and two dbWorker threads running that prevent the sysadmin db from being dropped. A reboot just does that - reboots without rebuilding the sysadmin database. Any advice would be appreciated. Thanks!
Don,
Stop the scheduler first, then you should have exclusive access:
Execute function task ("scheduler shutdown");
Jeff
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of DONALD
KORTHAUER
Sent: Monday, February 15, 2010 2:58 PM
To: ids@iiug.org
Subject: Re: Sysadmin Database Errors [19050]
We too have the -214 / 106 error messages in the log from Auto Statistics
and
tried to drop the sysadmin database as the first step to rebuild but can't
get
exclusive access.
There is a dbSchedu and two dbWorker threads running that prevent the
sysadmin
db from being dropped.
A reboot just does that - reboots without rebuilding the sysadmin database.
Any advice would be appreciated.
Thanks!
****************************************************************************
***
Forum Note: Use "Reply" to post a response in the discussion forum.
To drop the sysadmin database and rebuilt it from scratch run
the following:
As user informix
dbaccess sysadmin
execute function task("reset sysadmin");now exit dbaccess
NOTE: It is very important that you exist your current connection as
the database can not be rebuilt while you are connected to
the database.
John F. Miller III
STSM, Support Architect
miller3@us.ibm.com
503-578-5645
IBM Informix Dynamic Server (IDS)
ids-bounces@iiug.org wrote on 02/15/2010 12:58:23 PM:
> [image removed]
>
> Re: Sysadmin Database Errors [19050]
>
> DONALD KORTHAUER
>
> to:
>
> ids
>
> 02/15/2010 12:59 PM
>
> Sent by:
>
> ids-bounces@iiug.org
>
> Please respond to ids
>
> We too have the -214 / 106 error messages in the log from Auto Statistics
and
> tried to drop the sysadmin database as the first step to rebuild butcan't
get
> exclusive access.
>
> There is a dbSchedu and two dbWorker threads running that prevent
> the sysadmin
> db from being dropped.
> A reboot just does that - reboots without rebuilding the sysadmin
database.
>
> Any advice would be appreciated.
>
> Thanks!
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
Try this:
EXECUTE FUNCTION task("scheduler shutdown"); -- Stop the scheduler threads
Followed by this:
EXECUTE FUNCTION admin("reset sysadmin"); -- Drop & recreate sysadmin
EXECUTE FUNCTION task("scheduler start");
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
IIUG Board of Directors (art@iiug.org)
See you at the 2010 IIUG Informix Conference
April 25-28, 2010
Overland Park (Kansas City), KS
www.iiug.org/conf
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, 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, Feb 15, 2010 at 3:58 PM, DONALD KORTHAUER <
don.korthauer@ama-assn.org> wrote:
> We too have the -214 / 106 error messages in the log from Auto Statistics
> and
> tried to drop the sysadmin database as the first step to rebuild but can't
> get
> exclusive access.
>
> There is a dbSchedu and two dbWorker threads running that prevent the
> sysadmin
> db from being dropped.
> A reboot just does that - reboots without rebuilding the sysadmin database.
>
> Any advice would be appreciated.
>
> Thanks!
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001517493aae778499047faa2bbf
Gentlemen, Your assistance is greatly appreciated. We now have a successfully rebuilt sysadmin database and the dbSchedu and dbWorker threads started. We will see if this clears up our AUS issue. Thanks a bunch.
FYI,
The command reset sysadmin implicitly
does a shutdown before and a restart
after the command is run.
John F. Miller III
STSM, Support Architect
miller3@us.ibm.com
503-578-5645
IBM Informix Dynamic Server (IDS)
ids-bounces@iiug.org wrote on 02/15/2010 01:19:33 PM:
> [image removed]
>
> Re: Sysadmin Database Errors [19053]
>
> Art Kagel
>
> to:
>
> ids
>
> 02/15/2010 01:23 PM
>
> Sent by:
>
> ids-bounces@iiug.org
>
> Please respond to ids
>
> Try this:
>
> EXECUTE FUNCTION task("scheduler shutdown"); -- Stop the schedulerthreads
>
> Followed by this:
>
> EXECUTE FUNCTION admin("reset sysadmin"); -- Drop & recreate sysadmin
> EXECUTE FUNCTION task("scheduler start");>
> Art
>
> Art S. Kagel
> Advanced DataTools (www.advancedatatools.com)
> IIUG Board of Directors (art@iiug.org)
>
> See you at the 2010 IIUG Informix Conference
> April 25-28, 2010
> Overland Park (Kansas City), KS
> www.iiug.org/conf
>
> Disclaimer: Please keep in mind that my own opinions are my own opinions
and
> do not reflect on my employer, Advanced DataTools, 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, Feb 15, 2010 at 3:58 PM, DONALD KORTHAUER <
> don.korthauer@ama-assn.org> wrote:
>
> > We too have the -214 / 106 error messages in the log from Auto
Statistics
> > and
> > tried to drop the sysadmin database as the first step to rebuild but
can't
> > get
> > exclusive access.
> >
> > There is a dbSchedu and two dbWorker threads running that prevent the
> > sysadmin
> > db from being dropped.
> > A reboot just does that - reboots without rebuilding the sysadmin
database.
> >
> > Any advice would be appreciated.
> >
> > Thanks!
> >
> >
> >
> >
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --001517493aae778499047faa2bbf
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>