stupid question time
A DBA found his 2GB root dbspace 91% full on IDS 11.50 (HP-UX) and asked how to see what was in it and whether to just add a chunk. Replies pointed him to 'oncheck -pe' (plus a sysmaster query on systabnames/sysptnhdr, and checking sysutils/sysadmin growth), which revealed a stray 1.4GB temp table in rootdbs. Art Kagel explained the cause: logged temp tables go to rootdbs unless a non-temp dbspace is listed in DBSPACETEMP, so either add one or set TEMPTAB_NOLOG; also watch for databases created without an IN <dbspace> clause. To locate the tables he suggested: select tabname from systables where dbinfo('dbspace', partnum)='rootdbs'. It was also noted there's no parameter to forbid user tables in rootdbs.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Informix 11.50.FC6 on HP-UX 11.31 ia64 (Integrity server) BL870c I have a nightly cron job that run Jacob Salomon's monitor-space script to check how full dbspaces are. Well this morning I got a report that root is 91% full. Root dbspace has one 2GB chuck. Since it has been over 5 years that I had to deal with filling root dbspace, my brain is full of cob webs of what to look for and best steps to correct this matter. My first stupid question how do I find what is actually in the root dbspace? As my cob web full mind thought 5 years ago I moved everything out of root except the needed system databases. The second question is should I try cleanup or should I just add another chuck and call it good? Or something else? John Adamski Sr. network Specialist Graceland University
Does your sysutils database need to be pruned out and tables rebuilt? bar_action bar_instance bar_object bar_orderseq bar_ordertab bar_server -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of John Adamski Sent: Tuesday, July 12, 2011 8:55 AM To: ids@iiug.org Subject: stupid question time [24306] Informix 11.50.FC6 on HP-UX 11.31 ia64 (Integrity server) BL870c I have a nightly cron job that run Jacob Salomon's monitor-space script to check how full dbspaces are. Well this morning I got a report that root is 91% full. Root dbspace has one 2GB chuck. Since it has been over 5 years that I had to deal with filling root dbspace, my brain is full of cob webs of what to look for and best steps to correct this matter. My first stupid question how do I find what is actually in the root dbspace? As my cob web full mind thought 5 years ago I moved everything out of root except the needed system databases. The second question is should I try cleanup or should I just add another chuck and call it good? Or something else? John Adamski Sr. network Specialist Graceland University ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
Hi John,
Ignoring a "seemingly" stupid question can raise all sorts of cain down the
road so there really is NO stupid question.
oncheck -pe will tell you exactly what is in your dbspaces. I suggestredirection to a file that you can view aftyerwards. And I would also suggest
keepuing the root dbspace as clean as possible. It has enough stuff to do w/o
cluttering it up.
Good Luck,
dan
An update:
Someone pointed me to oncheck -pe root and it looks like somehow a
developer/user created a 1.4GB temp table in my root dbspace. I'm trying to
track down the culprit now and get this corrected. (baseball bat in hand) :-D
Guess I need to check my temp space setting as I thought was forcing them to
use the 3 temp dbspaces.
John
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of John
Adamski
Sent: Tuesday, July 12, 2011 8:55 AM
To: ids@iiug.org
Subject: stupid question time [24306]
Informix 11.50.FC6 on HP-UX 11.31 ia64 (Integrity server) BL870c
I have a nightly cron job that run Jacob Salomon's monitor-space script to
check how full dbspaces are. Well this morning I got a report that root is 91%
full. Root dbspace has one 2GB chuck.
Since it has been over 5 years that I had to deal with filling root dbspace,
my brain is full of cob webs of what to look for and best steps to correct
this matter.
My first stupid question how do I find what is actually in the root dbspace?
As my cob web full mind thought 5 years ago I moved everything out of root
except the needed system databases.
The second question is should I try cleanup or should I just add another chuck
and call it good? Or something else?
John Adamski
Sr. network Specialist
Graceland University
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Hi,
We had the same issue a while back. Which made me remember of an unofficial
survey :
Who has the smallest ? rootdbs that is !!!
Chunks
address chunk/dbs offset size free bpages
flags pathname
700001c8fd4a028 1 1 4 512000 490652
PO-B ./rootdbs
83 odd MB used. And I still need to clear some trash.
On Tue, Jul 12, 2011 at 4:18 PM, John Adamski <adamski@graceland.edu> wrote:
> An update:
>
> Someone pointed me to oncheck -pe root and it looks like somehow a
> developer/user created a 1.4GB temp table in my root dbspace. I'm trying to
> track down the culprit now and get this corrected. (baseball bat in hand)
> :-D
>
> Guess I need to check my temp space setting as I thought was forcing them
> to
> use the 3 temp dbspaces.
>
> John
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of John
> Adamski
> Sent: Tuesday, July 12, 2011 8:55 AM
> To: ids@iiug.org
> Subject: stupid question time [24306]
>
> Informix 11.50.FC6 on HP-UX 11.31 ia64 (Integrity server) BL870c
>
> I have a nightly cron job that run Jacob Salomon's monitor-space script to
> check how full dbspaces are. Well this morning I got a report that root is
> 91%
> full. Root dbspace has one 2GB chuck.
>
> Since it has been over 5 years that I had to deal with filling root
> dbspace,
> my brain is full of cob webs of what to look for and best steps to correct
> this matter.
>
> My first stupid question how do I find what is actually in the root
> dbspace?
> As my cob web full mind thought 5 years ago I moved everything out of root
> except the needed system databases.
>
> The second question is should I try cleanup or should I just add another
> chuck
> and call it good? Or something else?
>
> John Adamski
> Sr. network Specialist
> Graceland University
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--20cf302ad698ade0f404a7e00e15
Hello.
I´d like to suggest you to check sysadmin database, along with others
already....
Run the following query to check the sizes of them, and join with the
output of oncheck -pe ok???
---------------------------------------
SELECT dbsname,
round(sum(nptotal)*(t2.pagesize/1024)/1024,2) mb_total,
round(sum(npused)*(t2.pagesize/1024)/1024,2) mb_used,
round(sum(npdata)*(t2.pagesize/1024)/1024,2) mb_data
FROM sysmaster:systabnames t1, sysmaster:sysptnhdr t2
WHERE t1.partnum = t2.partnum
AND dbsname != "HASHTEMP"
AND dbsname != "BEFIMAGE"
AND dbsname != "SORTTEMP"
AND tabname != "TBLSpace"
GROUP BY dbsname, t2.pagesize
ORDER BY 2 desc;
Regards.
Em 12/07/2011 10:14, DAN MUELLER escreveu:
> Hi John,
>
> Ignoring a "seemingly" stupid question can raise all sorts of cain down the
> road so there really is NO stupid question.
>
> oncheck -pe will tell you exactly what is in your dbspaces. I suggest> redirection to a file that you can view aftyerwards. And I would also suggest
> keepuing the root dbspace as clean as possible. It has enough stuff to do w/o
> cluttering it up.
>
> Good Luck,
> dan
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Alexandre Marini
Tecnologia da Informação - DBA
msn: alexandre_marini@hotmail.com
SEFAZ-MS / SGI-UGSR / Sistemas IBM-Informix
<Cert-Info-Mgmt_color.jpg>
IBM Certified System Administrator - Informix Dynamic Server V10 / V11 /
V11.70
IBM Information Management Informix Technical Professional v3
John, Whether or not the temp tables are logged would also play a role in where they are created. Art Kagel has beat it into my head that is the reason for having a "non temp" dbspace listed in your onconfig DBSPACETEMP parameter. But I would still go beat up a developer just to relieve your stress level. Dan
It could be logged temp tables which default to using the rootdb space unless there is another non-temp dbspace listed in DBSPACETEMP. So, that's one fix you can do. Another is to set TEMPTAB_NOLOG in your ONCONFIG file which will prevent temp tables from ever being logged (it will make unlogged the default and the only way to make them logged is to explicitely create the temp table in a normal dbspace. Also look for databases that were created in rootdb which is the default if you don't specify an IN <dbspacename> clause when you create the database. Art Art S. Kagel 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 Tue, Jul 12, 2011 at 9:54 AM, John Adamski <adamski@graceland.edu> wrote: > Informix 11.50.FC6 on HP-UX 11.31 ia64 (Integrity server) BL870c > > I have a nightly cron job that run Jacob Salomon's monitor-space script to > check how full dbspaces are. Well this morning I got a report that root is > 91% > full. Root dbspace has one 2GB chuck. > > Since it has been over 5 years that I had to deal with filling root > dbspace, > my brain is full of cob webs of what to look for and best steps to correct > this matter. > > My first stupid question how do I find what is actually in the root > dbspace? > As my cob web full mind thought 5 years ago I moved everything out of root > except the needed system databases. > > The second question is should I try cleanup or should I just add another > chuck > and call it good? Or something else? > > John Adamski > Sr. network Specialist > Graceland University > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --20cf307f37fe7a810d04a7e06d1b
See - told ya.(-; dan
Well DBSPACETEMP is set-- each is 2GB in size --
DBSPACETEMP temp0,temp1,temp2
But looks like TEMPTAB_NOLOG is the default :-(
TEMPTAB_NOLOG 0
So will change that. Is this a new setting in 11.50? I sure missed this when I
upgrade to whatever version introduced it.
About 5-6 years ago I switched all of the non-sys database out of the root
dbspace. Our ERP had created them all in there. If I go into OAT and look at
storage & root dbspace it says 2 tables from 'cars; database still are in
root. I'm hoping they are temp tables, one of them being this big 1.4GB one.
What is the best way to find what tables are in root dbspace for the cars
database? So I can remove them or move them depending on what they are.
John
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art Kagel
Sent: Tuesday, July 12, 2011 9:51 AM
To: ids@iiug.org
Subject: Re: stupid question time [24313]
It could be logged temp tables which default to using the rootdb space unless
there is another non-temp dbspace listed in DBSPACETEMP. So, that's one fix
you can do. Another is to set TEMPTAB_NOLOG in your ONCONFIG file which will
prevent temp tables from ever being logged (it will make unlogged the default
and the only way to make them logged is to explicitely create the temp table
in a normal dbspace.
Also look for databases that were created in rootdb which is the default if
you don't specify an IN <dbspacename> clause when you create the database.
Art
Art S. Kagel
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 Tue, Jul 12, 2011 at 9:54 AM, John Adamski <adamski@graceland.edu> wrote:
> Informix 11.50.FC6 on HP-UX 11.31 ia64 (Integrity server) BL870c
>
> I have a nightly cron job that run Jacob Salomon's monitor-space
> script to check how full dbspaces are. Well this morning I got a
> report that root is 91% full. Root dbspace has one 2GB chuck.
>
> Since it has been over 5 years that I had to deal with filling root
> dbspace, my brain is full of cob webs of what to look for and best
> steps to correct this matter.
>
> My first stupid question how do I find what is actually in the root
> dbspace?
> As my cob web full mind thought 5 years ago I moved everything out of
> root except the needed system databases.
>
> The second question is should I try cleanup or should I just add
> another chuck and call it good? Or something else?
>
> John Adamski
> Sr. network Specialist
> Graceland University
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--20cf307f37fe7a810d04a7e06d1b
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Alexandre
Well I ran the query and I don't see anything that looks bad in the sysxxxxx
databases. My guess it is mostly this mysterious 1.4GB temp table with the
funny name that the problem. Granted my dba skills are very rusty because 3
years ago due to a staff reduction I've been doing everything except my DBA
work.
dbsname cars
mb_total 16738.21
mb_used 13840.24
mb_data 7408.51
dbsname train
mb_total 13357.14
mb_used 10490.39
mb_data 5721.33
dbsname cars_audit
mb_total 11392.56
mb_used 8616.00
mb_data 3218.90
dbsname uni93
mb_total 594.13
mb_used 586.37
mb_data 151.71
dbsname sysadmin
mb_total 32.29
mb_used 31.37
mb_data 17.63
dbsname sysmaster
mb_total 4.00
mb_used 3.15
mb_data 2.09
dbsname sysutils
mb_total 2.96
mb_used 2.25
mb_data 1.50
dbsname sysuser
mb_total 2.77
mb_used 2.14
mb_data 1.45
dbsname system
mb_total 0.03
mb_used 0.03
mb_data 0.03
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Alexandre Marini
Sent: Tuesday, July 12, 2011 9:26 AM
To: ids@iiug.org
Subject: Re: stupid question time [24311]
Hello.
I´d like to suggest you to check sysadmin database, along with others
already....
Run the following query to check the sizes of them, and join with the output
of oncheck -pe ok???
---------------------------------------
SELECT dbsname,
round(sum(nptotal)*(t2.pagesize/1024)/1024,2) mb_total,
round(sum(npused)*(t2.pagesize/1024)/1024,2) mb_used,
round(sum(npdata)*(t2.pagesize/1024)/1024,2) mb_data FROM
sysmaster:systabnames t1, sysmaster:sysptnhdr t2 WHERE t1.partnum = t2.partnum
AND dbsname != "HASHTEMP"
AND dbsname != "BEFIMAGE"
AND dbsname != "SORTTEMP"
AND tabname != "TBLSpace"
GROUP BY dbsname, t2.pagesize
ORDER BY 2 desc;
Regards.
Em 12/07/2011 10:14, DAN MUELLER escreveu:
> Hi John,
>
> Ignoring a "seemingly" stupid question can raise all sorts of cain
> down the road so there really is NO stupid question.
>
> oncheck -pe will tell you exactly what is in your dbspaces. I suggest> redirection to a file that you can view aftyerwards. And I would also
suggest
> keepuing the root dbspace as clean as possible. It has enough stuff to
> do
w/o
> cluttering it up.
>
> Good Luck,
> dan
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Alexandre Marini
Tecnologia da Informação - DBA
msn: alexandre_marini@hotmail.com
SEFAZ-MS / SGI-UGSR / Sistemas IBM-Informix
<Cert-Info-Mgmt_color.jpg>
IBM Certified System Administrator - Informix Dynamic Server V10 / V11 /
V11.70
IBM Information Management Informix Technical Professional v3
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
select tabname
from systables
where dbinfo('dbspace', partnum) = 'rootdbs';
Art
Art S. Kagel
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 Tue, Jul 12, 2011 at 11:19 AM, John Adamski <adamski@graceland.edu>wrote:
> Well DBSPACETEMP is set-- each is 2GB in size --
>
> DBSPACETEMP temp0,temp1,temp2
>
> But looks like TEMPTAB_NOLOG is the default :-(
>
> TEMPTAB_NOLOG 0>
> So will change that. Is this a new setting in 11.50? I sure missed this
> when I
> upgrade to whatever version introduced it.
>
> About 5-6 years ago I switched all of the non-sys database out of the root
> dbspace. Our ERP had created them all in there. If I go into OAT and look
> at
> storage & root dbspace it says 2 tables from 'cars; database still are in
> root. I'm hoping they are temp tables, one of them being this big 1.4GB
> one.
> What is the best way to find what tables are in root dbspace for the cars
> database? So I can remove them or move them depending on what they are.
>
> John
>
> -----Original Message-----
> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art
> Kagel
> Sent: Tuesday, July 12, 2011 9:51 AM
> To: ids@iiug.org
> Subject: Re: stupid question time [24313]
>
> It could be logged temp tables which default to using the rootdb space
> unless
> there is another non-temp dbspace listed in DBSPACETEMP. So, that's one fix
> you can do. Another is to set TEMPTAB_NOLOG in your ONCONFIG file which
> will
> prevent temp tables from ever being logged (it will make unlogged the
> default
> and the only way to make them logged is to explicitely create the temp
> table
> in a normal dbspace.
>
> Also look for databases that were created in rootdb which is the default if
> you don't specify an IN <dbspacename> clause when you create the database.
>
> Art
>
> Art S. Kagel
> 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 Tue, Jul 12, 2011 at 9:54 AM, John Adamski <adamski@graceland.edu>
> wrote:
>
> > Informix 11.50.FC6 on HP-UX 11.31 ia64 (Integrity server) BL870c
> >
> > I have a nightly cron job that run Jacob Salomon's monitor-space
> > script to check how full dbspaces are. Well this morning I got a
> > report that root is 91% full. Root dbspace has one 2GB chuck.
> >
> > Since it has been over 5 years that I had to deal with filling root
> > dbspace, my brain is full of cob webs of what to look for and best
> > steps to correct this matter.
> >
> > My first stupid question how do I find what is actually in the root
> > dbspace?
> > As my cob web full mind thought 5 years ago I moved everything out of
> > root except the needed system databases.
> >
> > The second question is should I try cleanup or should I just add
> > another chuck and call it good? Or something else?
> >
> > John Adamski
> > Sr. network Specialist
> > Graceland University
> >
> >
> >
> >
>
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --20cf307f37fe7a810d04a7e06d1b
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--20cf307f3536fdaae004a7e10871
Is there a parameter in any 11.X versions to prevent user tables from being created in ROOTDBS? Can LBAC prevent it? Possible feature request? Bob ----- Original Message ----- From: "Art Kagel" <art.kagel@gmail.com> To: ids@iiug.org Sent: Tuesday, July 12, 2011 10:51:03 AM Subject: Re: stupid question time [24313] It could be logged temp tables which default to using the rootdb space unless there is another non-temp dbspace listed in DBSPACETEMP. So, that's one fix you can do. Another is to set TEMPTAB_NOLOG in your ONCONFIG file which will prevent temp tables from ever being logged (it will make unlogged the default and the only way to make them logged is to explicitely create the temp table in a normal dbspace. Also look for databases that were created in rootdb which is the default if you don't specify an IN <dbspacename> clause when you create the database. Art Art S. Kagel 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 Tue, Jul 12, 2011 at 9:54 AM, John Adamski <adamski@graceland.edu> wrote: > Informix 11.50.FC6 on HP-UX 11.31 ia64 (Integrity server) BL870c > > I have a nightly cron job that run Jacob Salomon's monitor-space script to > check how full dbspaces are. Well this morning I got a report that root is > 91% > full. Root dbspace has one 2GB chuck. > > Since it has been over 5 years that I had to deal with filling root > dbspace, > my brain is full of cob webs of what to look for and best steps to correct > this matter. > > My first stupid question how do I find what is actually in the root > dbspace? > As my cob web full mind thought 5 years ago I moved everything out of root > except the needed system databases. > > The second question is should I try cleanup or should I just add another > chuck > and call it good? Or something else? > > John Adamski > Sr. network Specialist > Graceland University > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --20cf307f37fe7a810d04a7e06d1b ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
Nothing right now. You can prevent users from creating databases under 11.70, but if the user has resource or dba privs in a database, he/she can create tables in any dbspace. Art Art S. Kagel 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 Tue, Jul 12, 2011 at 3:56 PM, rroussey@comcast.net <rroussey@comcast.net>wrote: > Is there a parameter in any 11.X versions to prevent user tables from being > created in ROOTDBS? Can LBAC prevent it? Possible feature request? > > Bob > > ----- Original Message ----- > > From: "Art Kagel" <art.kagel@gmail.com> > To: ids@iiug.org > Sent: Tuesday, July 12, 2011 10:51:03 AM > Subject: Re: stupid question time [24313] > > It could be logged temp tables which default to using the rootdb space > unless there is another non-temp dbspace listed in DBSPACETEMP. So, that's > one fix you can do. Another is to set TEMPTAB_NOLOG in your ONCONFIG file > which will prevent temp tables from ever being logged (it will make > unlogged > the default and the only way to make them logged is to explicitely create > the temp table in a normal dbspace. > > Also look for databases that were created in rootdb which is the default if > you don't specify an IN <dbspacename> clause when you create the database. > > Art > > Art S. Kagel > 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 Tue, Jul 12, 2011 at 9:54 AM, John Adamski <adamski@graceland.edu> > wrote: > > > Informix 11.50.FC6 on HP-UX 11.31 ia64 (Integrity server) BL870c > > > > I have a nightly cron job that run Jacob Salomon's monitor-space script > to > > check how full dbspaces are. Well this morning I got a report that root > is > > 91% > > full. Root dbspace has one 2GB chuck. > > > > Since it has been over 5 years that I had to deal with filling root > > dbspace, > > my brain is full of cob webs of what to look for and best steps to > correct > > this matter. > > > > My first stupid question how do I find what is actually in the root > > dbspace? > > As my cob web full mind thought 5 years ago I moved everything out of > root > > except the needed system databases. > > > > The second question is should I try cleanup or should I just add another > > chuck > > and call it good? Or something else? > > > > John Adamski > > Sr. network Specialist > > Graceland University > > > > > > > > > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > --20cf307f37fe7a810d04a7e06d1b > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --20cf307f325af271b004a7e5c16f