rootdbs is full message
Posted in 2018
A user on Informix 12.10 (HP-UX) saw repeated 'rootdbs is full' and 'tempdbs is full' messages in online.log even though neither space looked full when checked. Replies explained the space is freed as soon as the session errors out, so it looks fine afterwards, and that logged temp tables (e.g. SELECT ... INTO TEMP with logging) spill into rootdbs rather than DBSPACETEMP. Suggested fixes: add more temp/normal dbspaces to the DBSPACETEMP list, keep permanent tables and sysadmin out of rootdbs, and use SQLTRACE to find the offending queries. No confirmation of a fix was posted.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: Storage & Space Management
hi I'm using informix 12.10 in HPUX I found message 'rootdbs is full' and 'tempdbs is full' in online.log but rootdbs was not full, and tempdbs also not full so I want to know, when tempdbs was full, is informix using rootdbs? and if informix using rootdbs instead of tempdbs, how to solve this problem? please give some hint thank you
On Mon, Apr 23, 2018 at 4:36 AM, GOBLINMANIAC@NAVER.COM BEOMSEOK < goblinmaniac@naver.com> wrote: > hi > > I'm using informix 12.10 in HPUX > > I found message 'rootdbs is full' and 'tempdbs is full' in online.log > > but rootdbs was not full, and tempdbs also not full > > so I want to know, when tempdbs was full, is informix using rootdbs? > > and if informix using rootdbs instead of tempdbs, how to solve this > problem? > > please give some hint > > thank you > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > When a session is consuming temporary space (either in temp dbspaces or others) and runs out of space it will get an error and typically the space will be freed. So, it's possible that when you look at the utilization is has already been freed. The system may consume rootdbs for "temporary space". And example, but there are others is if you create temporary tables with logging. Regards. -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently...
Hello. Just a shot: is dbscheduler running? sysadmin default dbspace is rootdbs, maybe it is filling it up. Permanent tables/databases should also not be stored in rootdbs, as a general "best practice". HTH Regards. Alexandre Marini IBM Informix Certified Professional v10 / v11.50 / v11.70 / v12.10 IBM Informix on Cloud - Database Administrator - 2017 IBM dashDB Managed Service for Analytics and Transactions - 2017 DB2 Advanced DBA - v10.5 for LUW IBM Information Management Informix Technical Professional IBM Certified Developer - Informix Genero Informix independent consultant ________________________________ De: ids-bounces@iiug.org <ids-bounces@iiug.org> em nome de Fernando Nunes <domusonline@gmail.com> Enviado: segunda-feira, 23 de abril de 2018 05:36 Para: ids@iiug.org Assunto: Re: rootdbs is full message [41035] On Mon, Apr 23, 2018 at 4:36 AM, GOBLINMANIAC@NAVER.COM BEOMSEOK < goblinmaniac@naver.com> wrote: > hi > > I'm using informix 12.10 in HPUX > > I found message 'rootdbs is full' and 'tempdbs is full' in online.log > > but rootdbs was not full, and tempdbs also not full > > so I want to know, when tempdbs was full, is informix using rootdbs? > > and if informix using rootdbs instead of tempdbs, how to solve this > problem? > > please give some hint > > thank you > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > When a session is consuming temporary space (either in temp dbspaces or others) and runs out of space it will get an error and typically the space will be freed. So, it's possible that when you look at the utilization is has already been freed. The system may consume rootdbs for "temporary space". And example, but there are others is if you create temporary tables with logging. Regards. -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently... ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
Just a maybe... we had a situation where rootdbs was filling up when creation of a temp table was using logged space, I had thought our default was non-logged but something got missed, and for two statements in our entire code base Informix used rootdbs as the temp space, since it was logged, and that was enough to fill rootdbs unexpectedly. Regards, Bryce. -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Fernando Nunes Sent: Monday, 23 April 2018 8:37 PM To: ids@iiug.org Subject: Re: rootdbs is full message [41035] On Mon, Apr 23, 2018 at 4:36 AM, GOBLINMANIAC@NAVER.COM BEOMSEOK < goblinmaniac@naver.com> wrote: > hi > > I'm using informix 12.10 in HPUX > > I found message 'rootdbs is full' and 'tempdbs is full' in online.log > > but rootdbs was not full, and tempdbs also not full > > so I want to know, when tempdbs was full, is informix using rootdbs? > > and if informix using rootdbs instead of tempdbs, how to solve this > problem? > > please give some hint > > thank you > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > When a session is consuming temporary space (either in temp dbspaces or others) and runs out of space it will get an error and typically the space will be freed. So, it's possible that when you look at the utilization is has already been freed. The system may consume rootdbs for "temporary space". And example, but there are others is if you create temporary tables with logging. Regards. -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently... ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
Thank you for your response.
I checked rootdbs using 'oncheck -pe rootdbs' so I'm thinking to your first
opnion
but that message occured several time, so how can I not make that message?
Add temporary dbspace? or other way?
and how can I find operation that using high cost tempdbs?
Add a normal dbspace and add that to the dbspacetemp list ????
Cheers
Paul
Paul Watson
Oninit www.oninit.com
Tel: +1 913 674 0360
Cell: +1 913 387 7529
Oninit® is a registered trademark of Oninit LLC
Failure is not as frightening as regret.
If you want to improve, be content to be thought foolish and stupid.
> On Apr 23, 2018, at 21:56, GOBLINMANIAC@NAVER.COM BEOMSEOK
<goblinmaniac@naver.com> wrote:
>
> Thank you for your response.
>
> I checked rootdbs using 'oncheck -pe rootdbs' so I'm thinking to your first
> opnion
>
> but that message occured several time, so how can I not make that message?
>
> Add temporary dbspace? or other way?
>
> and how can I find operation that using high cost tempdbs?
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
--Apple-Mail-F5D20898-A13F-4E4B-B39E-88327EBC7328
It usually helps to include some additional information:
1) the specific lines from the onconfig pertaining to DBTemp spaces
2) 'onstat -d' output showing the root and temp space flags.
3) the section from the message log with the error, and the surrounding few
minutes of entries.
Without either constantly checking what SQLs are running, or setting SQLTRACE,
there is no easy way to discover the source of the error -- even setting
something in the alarm program probably won't catch the offender since
Informix will kill the session as soon as it records the warning.
But, with the symptoms you've described, the proposed idea that Temp Tables
are causing the warning sounds like the best bet. "INTO TEMP" can be dangerous
if dbspacetemp is not set appropriately.
Hope that helps.
Michael Hoffman