Warning: The storage pool is out of space
Posted in 2013
A user on IDS 11.70.FC4 saw repeated "The storage pool is out of space" warnings in online.log even though dbspaces had free space and SP_THRESHOLD was 0 (which should disable the check). Art Kagel and Paul Watson explained TBLTBLFIRST/TBLTBLNEXT are unrelated (they only set root dbspace partition-table extent sizes at initialization). A sysmaster:sysconfig query confirmed SP_THRESHOLD was effectively 0, so the mon_low_storage scheduler task had apparently been re-enabled; the advice was to disable it manually (update ph_task set tk_enable='f' where tk_name='mon_low_storage', or onmode -wm SP_THRESHOLD=0). No confirmation from the poster is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Topics: Storage & Space Management, Server Administration, Third-Party Tools & Monitoring
Hello All,
I am using the IDS 11.70 FC4, and I am not using the automatic storage pool
provisioning feature.
But, I have seen this message in the online.log file.
I have enough free space available in the dbspaces.
Can someone explain that why this warning msg has appeared and what could be
the possible impact of this?
Here are my onconfig parameters related to automatice storage provisioning:
SP_AUTOEXPAND 1
SP_THRESHOLD 0
SP_WAITTIME 30
TBLTBLFIRST 0
TBLTBLNEXT 0
TBLSPACE_STATS 1
13:16:01 Warning: The storage pool is out of space. To enable automatic chunk
creation use the OpenAdmin Tool to add space to the pool.
Also please suggest that do i need to perform any action to avoid this message
or potential problem?
Thanks.
Regards,
Khan
Doesn't SP_THRESHOLD = 0 mean it is the automatic is off ?
> Hello All,
>
> I am using the IDS 11.70 FC4, and I am not using the automatic storage
> pool
> provisioning feature.
>
> But, I have seen this message in the online.log file.
>
> I have enough free space available in the dbspaces.
>
> Can someone explain that why this warning msg has appeared and what could
> be
> the possible impact of this?
>
> Here are my onconfig parameters related to automatice storage
> provisioning:
>
> SP_AUTOEXPAND 1
> SP_THRESHOLD 0
> SP_WAITTIME 30
>
> TBLTBLFIRST 0
> TBLTBLNEXT 0
> TBLSPACE_STATS 1>
> 13:16:01 Warning: The storage pool is out of space. To enable automatic
> chunk
>
> creation use the OpenAdmin Tool to add space to the pool.
>
> Also please suggest that do i need to perform any action to avoid this
> message
> or potential problem?
>
> Thanks.
>
> Regards,
> Khan
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
--
Paul Watson
Tel: +1 913-674-0360
Mob: +1 913-387-7529
Web: www.oninit.com
www.advancedatatools.com
Failure is not as frightening as regret.
If you want to improve, be content to be thought foolish and stupid.
What this country needs are more unemployed politicians
Paul is correct, SP_THRESHOLD 0 is supposed to turn off the monitoring task
that sends that message. Is it possible that the ONCONFIG file was
manually changed and the server was not bounced? What does this return:
select *
from sysmaster:sysconfig
where cf_name = 'SP_THRESHOLD';
If the cf_effective value isn't zero then that's your problem. You can
change it in memory with: onmode -wm SP_THRESHOLD=0, you can also manually
disable the mon_low_storage task with:
update ph_task
set tk_enable = 'f'
where tk_name = 'mon_low_storage';
Art
Art S. Kagel, Principal Consultant
Advanced DataTools (www.advancedatatools.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 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 Fri, Oct 11, 2013 at 1:45 PM, O KHAN <theultimateboy@hotmail.com> wrote:
> Hello All,
>
> I am using the IDS 11.70 FC4, and I am not using the automatic storage pool
> provisioning feature.
>
> But, I have seen this message in the online.log file.
>
> I have enough free space available in the dbspaces.
>
> Can someone explain that why this warning msg has appeared and what could
> be
> the possible impact of this?
>
> Here are my onconfig parameters related to automatice storage provisioning:
>
> SP_AUTOEXPAND 1
> SP_THRESHOLD 0
> SP_WAITTIME 30
>
> TBLTBLFIRST 0
> TBLTBLNEXT 0
> TBLSPACE_STATS 1>
> 13:16:01 Warning: The storage pool is out of space. To enable automatic
> chunk
>
> creation use the OpenAdmin Tool to add space to the pool.
>
> Also please suggest that do i need to perform any action to avoid this
> message
> or potential problem?
>
> Thanks.
>
> Regards,
> Khan
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a11c3c704406da304e87afc3d
But I have read in the documentation that if both TBLTBLFIRST & TBLTBLNEXT
parameters are set to zero, then it is not considerered as auto-expandable.
I have following values in my onconfig.
TBLTBLFIRST 0
TBLTBLNEXT 0
Regards,
Khan
This is the result of your query: cf_id 347 cf_name SP_THRESHOLD cf_flags 0 cf_original 0.000000 cf_effective 0.000000 cf_default 0.000000 No, I have just restarted the instance yesterday and have not made any changes in the memory. what could the reason than? Regards, Khan
Aren't these purely to control the tablespace tablespace, leaving them at
zero means the engine will control the tablespace tablespace extent
sizing/growth
Cheers
Paul
> But I have read in the documentation that if both TBLTBLFIRST & TBLTBLNEXT
> parameters are set to zero, then it is not considerered as
> auto-expandable.
>
> I have following values in my onconfig.
> TBLTBLFIRST 0
> TBLTBLNEXT 0>
> Regards,
> Khan
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
--
Paul Watson
Tel: +1 913-674-0360
Mob: +1 913-387-7529
Web: www.oninit.com
www.advancedatatools.com
Failure is not as frightening as regret.
If you want to improve, be content to be thought foolish and stupid.
What this country needs are more unemployed politicians
NO! TBLTBLFIRST and TBLTBLNEXT controlled (past tense) the size of the
first and next extents for the root dbspace partition table (ie space used
for the table headers for tables created in the root dbspace) at the time
the engine was originally initialized (ie: oninit -i). If they were set to
zero at the time of initialization it just means that the default values of
the equivalent of 250 pages and 4 pages respectively (so 500K & 8K or 1000K
& 16K depending on your platform). These have nothing to do with either
chunk extension or dbspace expansion using storage pools.
Art
Art S. Kagel, Principal Consultant
Advanced DataTools (www.advancedatatools.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 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 Fri, Oct 11, 2013 at 2:12 PM, O KHAN <theultimateboy@hotmail.com> wrote:
> But I have read in the documentation that if both TBLTBLFIRST & TBLTBLNEXT
> parameters are set to zero, then it is not considerered as auto-expandable.
>
> I have following values in my onconfig.
> TBLTBLFIRST 0
> TBLTBLNEXT 0>
> Regards,
> Khan
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a11c33fe64dd16f04e87b2faf
Odd, according to the docs, setting SP_THRESHOLD to zero is supposed to disable the task that is doing the checking. It's possible that for some reason the mon_low_storage task has been re-enabled. Just manually disable it using the update I posted and the messages will go away. Art Art S. Kagel, Principal Consultant Advanced DataTools (www.advancedatatools.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 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 Fri, Oct 11, 2013 at 2:16 PM, O KHAN <theultimateboy@hotmail.com> wrote: > This is the result of your query: > > cf_id 347 > cf_name SP_THRESHOLD > cf_flags 0 > cf_original 0.000000 > cf_effective 0.000000 > cf_default 0.000000 > > No, I have just restarted the instance yesterday and have not made any > changes > in the memory. > > what could the reason than? > > Regards, > Khan > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --047d7b3a8c5822bade04e87b49db