Oninit cdi / Archive
Talk to an expert →

rootdbs full for IDS 9.3

Posted in 2003

Summary

An IDS 9.3 user saw ON-Bar failures in bar_act.log (SQL -271 / ISAM -131, no free disk space) with onstat -d showing rootdbs almost full. Repliers explained the sysutils database lives in rootdbs and ON-Bar's backup history tables (bar_action etc.) grow there; suggestions included checking extents with oncheck -pe/-pt, adding a chunk to rootdbs, or purging old records. The poster resolved it by running onsmsync -i "12 00:00:00" to delete bar_action rows older than 12 days, reclaiming rootdbs space, and planned to run it monthly plus add a rootdbs chunk.

Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.

Topics: Storage & Space Management, Error Codes & Troubleshooting, Versions, Editions & End-of-Life

Rahn Payne — — source: IIUG Forums & Mailing Lists

This is a multi-part message in MIME format. ------=_NextPart_000_0056_01C2C77C.864CAFC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hey all, I'm running IDS 9.3 and am getting the following message in my = bar_act.log: 2003-01-29 08:37:24 31598 37464 SQL -271 Could not insert new row = into the table. 2003-01-29 08:37:24 31598 37464 ISAM -131 ISAM error: no free disk = space My onstat -d looks like this: address chk/dbs offset size free bpages flags pathname 400ff918 1 1 0 7500 7 PO- = /data01/root_rmgr 4015da98 2 2 0 7500 6991 PO- = /appl/tmp/tmp1_rmgr 4015dc08 3 3 0 125000 0 PO- = /data01/dbs01_rmgr 4015dd78 4 4 0 125000 1 PO- = /data02/dbs02_rmgr 400ffac0 5 5 0 2500 197 PO- = /data01/phys_rmgr 400ffc30 6 6 0 7500 6959 PO- = /data01/tmp2_rmgr 400ffda0 7 7 0 7500 6951 PO- = /data02/tmp3_rmgr 4014e030 8 8 0 500 47 PO- = /data01/logic1_rmgr 4014e1a0 9 9 0 500 47 PO- = /data01/logic2_rmgr 4014e310 10 10 0 500 47 PO- = /data01/logic3_rmgr 4014e480 11 11 0 500 47 PO- = /data01/logic4_rmgr 4014e5f0 12 12 0 500 47 PO- = /data01/logic5_rmgr 4014e760 13 13 0 500 47 PO- = /data02/logic6_rmgr 4014e8d0 14 14 0 500 47 PO- = /data02/logic7_rmgr 4014ea40 15 15 0 500 47 PO- = /data02/logic8_rmgr 4014ebb0 16 16 0 500 47 PO- = /data02/logic9_rmgr 4014ed20 17 17 0 500 47 PO- = /data02/logic10_rmgr 4014ee90 18 3 125000 250000 313 PO- = /data01/dbs01_rmgr 40731018 19 4 125000 250000 30745 PO- = /data02/dbs02_rmgr 40731188 20 3 375000 100000 91805 PO- = /data01/dbs01_rmgr 407312f8 21 4 375000 100000 99997 PO- = /data02/dbs02_rmgr I suspect that it is the root_rmgr (rootdbs) that is too full to be = written to. Does anyone know how space can be restored to rootdbs? = According to the manuals and training, rootdbs is set once (at about = 30MB), can't be increased, and I didn't know it would fill up! I have = been very careful not to create tables in rootdbs. I think it has just = slowly filled. Thanks for any suggestions! Rahn Rahn Payne Rehab Manager, Inc. email: rpayne@rehabmgr.com ------=_NextPart_000_0056_01C2C77C.864CAFC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Dwindows-1252" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>Hey all,</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>I'm running IDS 9.3 and am getting the = following=20 message in my bar_act.log:</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>2003-01-29 08:37:24 31598&nbsp; 37464=20 SQL&nbsp;&nbsp;&nbsp;&nbsp; -271&nbsp; Could not insert new row into the = table.<BR>2003-01-29 08:37:24 31598&nbsp; 37464 = ISAM&nbsp;&nbsp;&nbsp;&nbsp;=20 -131 ISAM error: no free disk space</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>My onstat -d looks like = this:</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>address&nbsp; chk/dbs = offset&nbsp;&nbsp;=20 size&nbsp;&nbsp;&nbsp;&nbsp; free&nbsp;&nbsp;&nbsp;&nbsp; = bpages&nbsp;&nbsp;=20 flags pathname<BR><STRONG>400ff918 1&nbsp;&nbsp; 1&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&nbsp;&nbsp;&nbsp;&nbsp; = 7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/root_rmgr<BR></STRONG>4015da98 2&nbsp;&nbsp;=20 2&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 7500&nbsp;&nbsp;&nbsp;&nbsp;=20 6991&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;&nbsp;=20 PO-&nbsp;&nbsp; /appl/tmp/tmp1_rmgr<BR>4015dc08 3&nbsp;&nbsp; = 3&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 125000&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/dbs01_rmgr<BR>4015dd78 4&nbsp;&nbsp; = 4&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 125000&nbsp;&nbsp;=20 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data02/dbs02_rmgr<BR>400ffac0 5&nbsp;&nbsp; = 5&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2500&nbsp;&nbsp;&nbsp;&nbsp; = 197&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs= p;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/phys_rmgr<BR>400ffc30 6&nbsp;&nbsp; = 6&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&nbsp;&nbsp;&nbsp;&nbsp; = 6959&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/tmp2_rmgr<BR>400ffda0 7&nbsp;&nbsp; = 7&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&nbsp;&nbsp;&nbsp;&nbsp; = 6951&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;&nbsp;=20 PO-&nbsp;&nbsp; /data02/tmp3_rmgr<BR>4014e030 8&nbsp;&nbsp; = 8&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= ;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/logic1_rmgr<BR>4014e1a0 9&nbsp;&nbsp; = 9&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= ;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/logic2_rmgr<BR>4014e310 10&nbsp; 10&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= ;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/logic3_rmgr<BR>4014e480 11&nbsp; 11&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= ;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/logic4_rmgr<BR>4014e5f0 12&nbsp; 12&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= ;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/logic5_rmgr<BR>4014e760 13&nbsp; 13&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= ;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data02/logic6_rmgr<BR>4014e8d0 14&nbsp; 14&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= ;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data02/logic7_rmgr<BR>4014ea40 15&nbsp; 15&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

↪ replying to Rahn Payne
Mark Scranton — — source: IIUG Forums & Mailing Lists

Rahn - Odds on the engine is trying to allocate another extent to a table in the sysutils database (which is used by onbar), and there aren't enough free contiguous pages in the root chunk (although there are 7 free according to the onstat -d, they may not be contiguous. oncheck -pe would show you). The minimum extent size the engine will allocate is 4 pages. This error will also turn up when a given table has reached it's maximum number of extents. This is not a hard-coded number...you can check this value via oncheck -pt sysutils:<table> or sysmaster:sysptnhdr. If the number of extents is high (3 digits), it's possible that you have simply run out of space in the partition page for that table to track the extents. The only cure for that is to reorg the table. Being a system catalog, I I don't advise it (playing safe here), but tech support could help you with it. I believe there is a utility that will clean up/sync the onbar logs and the sysutils database. Can't recall it's name. This may remove/purge old/expired rows from the sysutils database. I really can't remember how this works - anyone??? HTH - Mark. |---------+----------------------------> | | "Rahn Payne" | | | <rpayne@rehabmgr.| | | com> | | | Sent by: | | | forum.subscriber@| | | iiug.org | | | | | | | | | 01/29/2003 09:01 | | | AM | | | | |---------+----------------------------> >------------------------------------------------------------------------------- ----------------------------------------------| | | | To: ids@iiug.org | | cc: | | Subject: rootdbs full for IDS 9.3 [156] | | | >------------------------------------------------------------------------------- ----------------------------------------------| This is a multi-part message in MIME format. ------=_NextPart_000_0056_01C2C77C.864CAFC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hey all, I'm running IDS 9.3 and am getting the following message in my = bar_act.log: 2003-01-29 08:37:24 31598 37464 SQL -271 Could not insert new row = into the table. 2003-01-29 08:37:24 31598 37464 ISAM -131 ISAM error: no free disk = space My onstat -d looks like this: address chk/dbs offset size free bpages flags pathname 400ff918 1 1 0 7500 7 PO- = /data01/root_rmgr 4015da98 2 2 0 7500 6991 PO- = /appl/tmp/tmp1_rmgr 4015dc08 3 3 0 125000 0 PO- = /data01/dbs01_rmgr 4015dd78 4 4 0 125000 1 PO- = /data02/dbs02_rmgr 400ffac0 5 5 0 2500 197 PO- = /data01/phys_rmgr 400ffc30 6 6 0 7500 6959 PO- = /data01/tmp2_rmgr 400ffda0 7 7 0 7500 6951 PO- = /data02/tmp3_rmgr 4014e030 8 8 0 500 47 PO- = /data01/logic1_rmgr 4014e1a0 9 9 0 500 47 PO- = /data01/logic2_rmgr 4014e310 10 10 0 500 47 PO- = /data01/logic3_rmgr 4014e480 11 11 0 500 47 PO- = /data01/logic4_rmgr 4014e5f0 12 12 0 500 47 PO- = /data01/logic5_rmgr 4014e760 13 13 0 500 47 PO- = /data02/logic6_rmgr 4014e8d0 14 14 0 500 47 PO- = /data02/logic7_rmgr 4014ea40 15 15 0 500 47 PO- = /data02/logic8_rmgr 4014ebb0 16 16 0 500 47 PO- = /data02/logic9_rmgr 4014ed20 17 17 0 500 47 PO- = /data02/logic10_rmgr 4014ee90 18 3 125000 250000 313 PO- = /data01/dbs01_rmgr 40731018 19 4 125000 250000 30745 PO- = /data02/dbs02_rmgr 40731188 20 3 375000 100000 91805 PO- = /data01/dbs01_rmgr 407312f8 21 4 375000 100000 99997 PO- = /data02/dbs02_rmgr I suspect that it is the root_rmgr (rootdbs) that is too full to be = written to. Does anyone know how space can be restored to rootdbs? = According to the manuals and training, rootdbs is set once (at about = 30MB), can't be increased, and I didn't know it would fill up! I have = been very careful not to create tables in rootdbs. I think it has just = slowly filled. Thanks for any suggestions! Rahn Rahn Payne Rehab Manager, Inc. email: rpayne@rehabmgr.com ------=_NextPart_000_0056_01C2C77C.864CAFC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Dwindows-1252" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>Hey all,</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>I'm running IDS 9.3 and am getting the = following=20 message in my bar_act.log:</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>2003-01-29 08:37:24 31598&nbsp; 37464=20 SQL&nbsp;&nbsp;&nbsp;&nbsp; -271&nbsp; Could not insert new row into the = table.<BR>2003-01-29 08:37:24 31598&nbsp; 37464 = ISAM&nbsp;&nbsp;&nbsp;&nbsp;=20 -131 ISAM error: no free disk space</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>My onstat -d looks like = this:</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>address&nbsp; chk/dbs = offset&nbsp;&nbsp;=20 size&nbsp;&nbsp;&nbsp;&nbsp; free&nbsp;&nbsp;&nbsp;&nbsp; = bpages&nbsp;&nbsp;=20 flags pathname<BR><STRONG>400ff918 1&nbsp;&nbsp; 1&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&nbsp;&nbsp;&nbsp;&nbsp; = 7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/root_rmgr<BR></STRONG>4015da98 2&nbsp;&nbsp;=20 2&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 7500&nbsp;&nbsp;&nbsp;&nbsp;=20 6991&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;&nbsp;=20 PO-&nbsp;&nbsp; /appl/tmp/tmp1_rmgr<BR>4015dc08 3&nbsp;&nbsp; = 3&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 125000&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/dbs01_rmgr<BR>4015dd78 4&nbsp;&nbsp; = 4&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 125000&nbsp;&nbsp;=20 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data02/dbs02_rmgr<BR>400ffac0 5&nbsp;&nbsp; = 5&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2500&nbsp;&nbsp;&nbsp;&nbsp; = 197&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs= p;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/phys_rmgr<BR>400ffc30 6&nbsp;&nbsp; = 6&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&nbsp;&nbsp;&nbsp;&nbsp; = 6959&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/tmp2_rmgr<BR>400ffda0 7&nbsp;&nbsp; = 7&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&nbsp;&nbsp;&nbsp;&nbsp; = 6951&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;&nbsp;=20 PO-&nbsp;&nbsp; /data02/tmp3_rmgr<BR>4014e030 8&nbsp;&nbsp; = 8&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&

↪ replying to Rahn Payne
Palmer, George — — source: IIUG Forums & Mailing Lists

Please do not post MIME. The reason rootdbs filled is that database sysutils ( created when the system was brought up ) is in rootdbs. Onbar records saveset information there and has grown the tables. Look for utility onsmsync ( which purges sysutils, and other things duties ) or add an additional chunk to rootdbs. George Palmer Senior DBA Pegasus solutions. -----Original Message----- From: Rahn Payne [mailto:rpayne@rehabmgr.com] Sent: Wednesday, January 29, 2003 9:02 AM To: ids@iiug.org Subject: rootdbs full for IDS 9.3 [156] This is a multi-part message in MIME format. ------=_NextPart_000_0056_01C2C77C.864CAFC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hey all, I'm running IDS 9.3 and am getting the following message in my = bar_act.log: 2003-01-29 08:37:24 31598 37464 SQL -271 Could not insert new row = into the table. 2003-01-29 08:37:24 31598 37464 ISAM -131 ISAM error: no free disk = space My onstat -d looks like this: address chk/dbs offset size free bpages flags pathname 400ff918 1 1 0 7500 7 PO- = /data01/root_rmgr 4015da98 2 2 0 7500 6991 PO- = /appl/tmp/tmp1_rmgr 4015dc08 3 3 0 125000 0 PO- = /data01/dbs01_rmgr 4015dd78 4 4 0 125000 1 PO- = /data02/dbs02_rmgr 400ffac0 5 5 0 2500 197 PO- = /data01/phys_rmgr 400ffc30 6 6 0 7500 6959 PO- = /data01/tmp2_rmgr 400ffda0 7 7 0 7500 6951 PO- = /data02/tmp3_rmgr 4014e030 8 8 0 500 47 PO- = /data01/logic1_rmgr 4014e1a0 9 9 0 500 47 PO- = /data01/logic2_rmgr 4014e310 10 10 0 500 47 PO- = /data01/logic3_rmgr 4014e480 11 11 0 500 47 PO- = /data01/logic4_rmgr 4014e5f0 12 12 0 500 47 PO- = /data01/logic5_rmgr 4014e760 13 13 0 500 47 PO- = /data02/logic6_rmgr 4014e8d0 14 14 0 500 47 PO- = /data02/logic7_rmgr 4014ea40 15 15 0 500 47 PO- = /data02/logic8_rmgr 4014ebb0 16 16 0 500 47 PO- = /data02/logic9_rmgr 4014ed20 17 17 0 500 47 PO- = /data02/logic10_rmgr 4014ee90 18 3 125000 250000 313 PO- = /data01/dbs01_rmgr 40731018 19 4 125000 250000 30745 PO- = /data02/dbs02_rmgr 40731188 20 3 375000 100000 91805 PO- = /data01/dbs01_rmgr 407312f8 21 4 375000 100000 99997 PO- = /data02/dbs02_rmgr I suspect that it is the root_rmgr (rootdbs) that is too full to be = written to. Does anyone know how space can be restored to rootdbs? = According to the manuals and training, rootdbs is set once (at about = 30MB), can't be increased, and I didn't know it would fill up! I have = been very careful not to create tables in rootdbs. I think it has just = slowly filled. Thanks for any suggestions! Rahn Rahn Payne Rehab Manager, Inc. email: rpayne@rehabmgr.com ------=_NextPart_000_0056_01C2C77C.864CAFC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Dwindows-1252" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>Hey all,</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>I'm running IDS 9.3 and am getting the = following=20 message in my bar_act.log:</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>2003-01-29 08:37:24 31598&nbsp; 37464=20 SQL&nbsp;&nbsp;&nbsp;&nbsp; -271&nbsp; Could not insert new row into the = table.<BR>2003-01-29 08:37:24 31598&nbsp; 37464 = ISAM&nbsp;&nbsp;&nbsp;&nbsp;=20 -131 ISAM error: no free disk space</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>My onstat -d looks like = this:</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>address&nbsp; chk/dbs = offset&nbsp;&nbsp;=20 size&nbsp;&nbsp;&nbsp;&nbsp; free&nbsp;&nbsp;&nbsp;&nbsp; = bpages&nbsp;&nbsp;=20 flags pathname<BR><STRONG>400ff918 1&nbsp;&nbsp; 1&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&nbsp;&nbsp;&nbsp;&nbsp; = 7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/root_rmgr<BR></STRONG>4015da98 2&nbsp;&nbsp;=20 2&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 7500&nbsp;&nbsp;&nbsp;&nbsp;=20 6991&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;&nbsp;=20 PO-&nbsp;&nbsp; /appl/tmp/tmp1_rmgr<BR>4015dc08 3&nbsp;&nbsp; = 3&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 125000&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/dbs01_rmgr<BR>4015dd78 4&nbsp;&nbsp; = 4&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 125000&nbsp;&nbsp;=20 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data02/dbs02_rmgr<BR>400ffac0 5&nbsp;&nbsp; = 5&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2500&nbsp;&nbsp;&nbsp;&nbsp; = 197&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs= p;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/phys_rmgr<BR>400ffc30 6&nbsp;&nbsp; = 6&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&nbsp;&nbsp;&nbsp;&nbsp; = 6959&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/tmp2_rmgr<BR>400ffda0 7&nbsp;&nbsp; = 7&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&nbsp;&nbsp;&nbsp;&nbsp; = 6951&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;&nbsp;=20 PO-&nbsp;&nbsp; /data02/tmp3_rmgr<BR>4014e030 8&nbsp;&nbsp; = 8&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= ;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/logic1_rmgr<BR>4014e1a0 9&nbsp;&nbsp; = 9&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= ;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/logic2_rmgr<BR>4014e310 10&nbsp; 10&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= ;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/logic3_rmgr<BR>4014e480 11&nbsp; 11&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= ;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/logic4_rmgr<BR>4014e5f0 12&nbsp; 12&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= ;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/logic5_rmgr<BR>4014e760 13&nbsp; 13&nbsp;=20 0&nbsp;&nbsp

↪ replying to Mark Scranton
Rajib Sarkar — — source: IIUG Forums & Mailing Lists

the utility is onsmsync ..:-) Thanx much, Rajib Sarkar Advisory Support Engineer (Wells Fargo Bank) IBM Data Management Group Ph : (602)-217-2100 Fax: (602)-217-2100 As long as you derive inner help and comfort from anything, keep it -- Mahatma Gandhi Mark Scranton/Denver/ To: ids@iiug.org IBM@IBMUS cc: Sent by: Subject: Re: rootdbs full for IDS 9.3 [157] forum.subscriber @iiug.org 01/29/2003 09:41 AM Rahn - Odds on the engine is trying to allocate another extent to a table in the sysutils database (which is used by onbar), and there aren't enough free contiguous pages in the root chunk (although there are 7 free according to the onstat -d, they may not be contiguous. oncheck -pe would show you). The minimum extent size the engine will allocate is 4 pages. This error will also turn up when a given table has reached it's maximum number of extents. This is not a hard-coded number...you can check this value via oncheck -pt sysutils:<table> or sysmaster:sysptnhdr. If the number of extents is high (3 digits), it's possible that you have simply run out of space in the partition page for that table to track the extents. The only cure for that is to reorg the table. Being a system catalog, I I don't advise it (playing safe here), but tech support could help you with it. I believe there is a utility that will clean up/sync the onbar logs and the sysutils database. Can't recall it's name. This may remove/purge old/expired rows from the sysutils database. I really can't remember how this works - anyone??? HTH - Mark. |---------+----------------------------> | | "Rahn Payne" | | | <rpayne@rehabmgr.| | | com> | | | Sent by: | | | forum.subscriber@| | | iiug.org | | | | | | | | | 01/29/2003 09:01 | | | AM | | | | |---------+----------------------------> >------------------------------------------------------------------------------- ----------------------------------------------| | | | To: ids@iiug.org | | cc: | | Subject: rootdbs full for IDS 9.3 [156] | | | >------------------------------------------------------------------------------- ----------------------------------------------| This is a multi-part message in MIME format. ------=_NextPart_000_0056_01C2C77C.864CAFC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hey all, I'm running IDS 9.3 and am getting the following message in my = bar_act.log: 2003-01-29 08:37:24 31598 37464 SQL -271 Could not insert new row = into the table. 2003-01-29 08:37:24 31598 37464 ISAM -131 ISAM error: no free disk = space My onstat -d looks like this: address chk/dbs offset size free bpages flags pathname 400ff918 1 1 0 7500 7 PO- = /data01/root_rmgr 4015da98 2 2 0 7500 6991 PO- = /appl/tmp/tmp1_rmgr 4015dc08 3 3 0 125000 0 PO- = /data01/dbs01_rmgr 4015dd78 4 4 0 125000 1 PO- = /data02/dbs02_rmgr 400ffac0 5 5 0 2500 197 PO- = /data01/phys_rmgr 400ffc30 6 6 0 7500 6959 PO- = /data01/tmp2_rmgr 400ffda0 7 7 0 7500 6951 PO- = /data02/tmp3_rmgr 4014e030 8 8 0 500 47 PO- = /data01/logic1_rmgr 4014e1a0 9 9 0 500 47 PO- = /data01/logic2_rmgr 4014e310 10 10 0 500 47 PO- = /data01/logic3_rmgr 4014e480 11 11 0 500 47 PO- = /data01/logic4_rmgr 4014e5f0 12 12 0 500 47 PO- = /data01/logic5_rmgr 4014e760 13 13 0 500 47 PO- = /data02/logic6_rmgr 4014e8d0 14 14 0 500 47 PO- = /data02/logic7_rmgr 4014ea40 15 15 0 500 47 PO- = /data02/logic8_rmgr 4014ebb0 16 16 0 500 47 PO- = /data02/logic9_rmgr 4014ed20 17 17 0 500 47 PO- = /data02/logic10_rmgr 4014ee90 18 3 125000 250000 313 PO- = /data01/dbs01_rmgr 40731018 19 4 125000 250000 30745 PO- = /data02/dbs02_rmgr 40731188 20 3 375000 100000 91805 PO- = /data01/dbs01_rmgr 407312f8 21 4 375000 100000 99997 PO- = /data02/dbs02_rmgr I suspect that it is the root_rmgr (rootdbs) that is too full to be = written to. Does anyone know how space can be restored to rootdbs? = According to the manuals and training, rootdbs is set once (at about = 30MB), can't be increased, and I didn't know it would fill up! I have = been very careful not to create tables in rootdbs. I think it has just = slowly filled. Thanks for any suggestions! Rahn Rahn Payne Rehab Manager, Inc. email: rpayne@rehabmgr.com ------=_NextPart_000_0056_01C2C77C.864CAFC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Dwindows-1252" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>Hey all,</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>I'm running IDS 9.3 and am getting the = following=20 message in my bar_act.log:</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>2003-01-29 08:37:24 31598&nbsp; 37464=20 SQL&nbsp;&nbsp;&nbsp;&nbsp; -271&nbsp; Could not insert new row into the = table.<BR>2003-01-29 08:37:24 31598&nbsp; 37464 = ISAM&nbsp;&nbsp;&nbsp;&nbsp;=20 -131 ISAM error: no free disk space</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>My onstat -d looks like = this:</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT face=3DArial size=3D2>address&nbsp; chk/dbs = offset&nbsp;&nbsp;=20 size&nbsp;&nbsp;&nbsp;&nbsp; free&nbsp;&nbsp;&nbsp;&nbsp; = bpages&nbsp;&nbsp;=20 flags pathname<BR><STRONG>400ff918 1&nbsp;&nbsp; 1&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&nbsp;&nbsp;&nbsp;&nbsp; = 7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/root_rmgr<BR></STRONG>4015da98 2&nbsp;&nbsp;=20 2&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 7500&nbsp;&nbsp;&nbsp;&nbsp;=20 6991&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;&nbsp;=20 PO-&nbsp;&nbsp; /appl/tmp/tmp1_rmgr<BR>4015dc08 3&nbsp;&nbsp; = 3&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 125000&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/dbs01_rmgr<BR>4015dd78 4&nbsp;&nbsp; = 4&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 125000&nbsp;&nbsp;=20 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data02/dbs02_rmgr<BR>400ffac0 5&nbsp;&nbsp; = 5&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2500&nbsp;&nbsp;&nbsp;&nbsp; = 197&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs= p;&nbsp;&nbsp;=20 PO-&nbsp;&nbsp; /data01/phys_rmgr<BR>400ffc30 6&nbsp;&nbsp; = 6&nbsp;&nbsp;=20 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&n

↪ replying to Rahn Payne
Ali Kemal BAKIR — — source: IIUG Forums & Mailing Lists

Hi, Your rootdbs which is 15MB is full... I think it's not poosible to extend by chunks. If any db is created on it. I can can suggest you to backup,and then drop that db. May be you can free it a little. Or get all dbs backed up by dbexport. Then you initialize rootdbs ( by oinit -i ) on a larger character device (chunk). Not less than 500 MB. Regards, A. Kemal BAKIR ----- Original Message ----- From: "Rahn Payne" <rpayne@rehabmgr.com> To: <ids@iiug.org> Sent: Wednesday, January 29, 2003 6:01 PM Subject: rootdbs full for IDS 9.3 [156] > This is a multi-part message in MIME format. > > ------=_NextPart_000_0056_01C2C77C.864CAFC0 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > > Hey all, > > I'm running IDS 9.3 and am getting the following message in my = > bar_act.log: > > 2003-01-29 08:37:24 31598 37464 SQL -271 Could not insert new row = > into the table. > 2003-01-29 08:37:24 31598 37464 ISAM -131 ISAM error: no free disk = > space > > My onstat -d looks like this: > > address chk/dbs offset size free bpages flags pathname > 400ff918 1 1 0 7500 7 PO- = > /data01/root_rmgr > 4015da98 2 2 0 7500 6991 PO- = > /appl/tmp/tmp1_rmgr > 4015dc08 3 3 0 125000 0 PO- = > /data01/dbs01_rmgr > 4015dd78 4 4 0 125000 1 PO- = > /data02/dbs02_rmgr > 400ffac0 5 5 0 2500 197 PO- = > /data01/phys_rmgr > 400ffc30 6 6 0 7500 6959 PO- = > /data01/tmp2_rmgr > 400ffda0 7 7 0 7500 6951 PO- = > /data02/tmp3_rmgr > 4014e030 8 8 0 500 47 PO- = > /data01/logic1_rmgr > 4014e1a0 9 9 0 500 47 PO- = > /data01/logic2_rmgr > 4014e310 10 10 0 500 47 PO- = > /data01/logic3_rmgr > 4014e480 11 11 0 500 47 PO- = > /data01/logic4_rmgr > 4014e5f0 12 12 0 500 47 PO- = > /data01/logic5_rmgr > 4014e760 13 13 0 500 47 PO- = > /data02/logic6_rmgr > 4014e8d0 14 14 0 500 47 PO- = > /data02/logic7_rmgr > 4014ea40 15 15 0 500 47 PO- = > /data02/logic8_rmgr > 4014ebb0 16 16 0 500 47 PO- = > /data02/logic9_rmgr > 4014ed20 17 17 0 500 47 PO- = > /data02/logic10_rmgr > 4014ee90 18 3 125000 250000 313 PO- = > /data01/dbs01_rmgr > 40731018 19 4 125000 250000 30745 PO- = > /data02/dbs02_rmgr > 40731188 20 3 375000 100000 91805 PO- = > /data01/dbs01_rmgr > 407312f8 21 4 375000 100000 99997 PO- = > /data02/dbs02_rmgr > > I suspect that it is the root_rmgr (rootdbs) that is too full to be = > written to. Does anyone know how space can be restored to rootdbs? = > According to the manuals and training, rootdbs is set once (at about = > 30MB), can't be increased, and I didn't know it would fill up! I have = > been very careful not to create tables in rootdbs. I think it has just = > slowly filled. > > Thanks for any suggestions! > > Rahn > > Rahn Payne > Rehab Manager, Inc. > email: rpayne@rehabmgr.com > > > ------=_NextPart_000_0056_01C2C77C.864CAFC0 > Content-Type: text/html; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > <HTML><HEAD> > <META content=3D"text/html; charset=3Dwindows-1252" = > http-equiv=3DContent-Type> > <META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR> > <STYLE></STYLE> > </HEAD> > <BODY bgColor=3D#ffffff> > <DIV>&nbsp;</DIV> > <DIV><FONT face=3DArial size=3D2>Hey all,</FONT></DIV> > <DIV>&nbsp;</DIV> > <DIV><FONT face=3DArial size=3D2>I'm running IDS 9.3 and am getting the = > following=20 > message in my bar_act.log:</FONT></DIV> > <DIV>&nbsp;</DIV> > <DIV><FONT face=3DArial size=3D2>2003-01-29 08:37:24 31598&nbsp; 37464=20 > SQL&nbsp;&nbsp;&nbsp;&nbsp; -271&nbsp; Could not insert new row into the = > > table.<BR>2003-01-29 08:37:24 31598&nbsp; 37464 = > ISAM&nbsp;&nbsp;&nbsp;&nbsp;=20 > -131 ISAM error: no free disk space</FONT></DIV> > <DIV>&nbsp;</DIV> > <DIV><FONT face=3DArial size=3D2>My onstat -d looks like = > this:</FONT></DIV> > <DIV>&nbsp;</DIV> > <DIV><FONT face=3DArial size=3D2>address&nbsp; chk/dbs = > offset&nbsp;&nbsp;=20 > size&nbsp;&nbsp;&nbsp;&nbsp; free&nbsp;&nbsp;&nbsp;&nbsp; = > bpages&nbsp;&nbsp;=20 > flags pathname<BR><STRONG>400ff918 1&nbsp;&nbsp; 1&nbsp;&nbsp;=20 > 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&nbsp;&nbsp;&nbsp;&nbsp; = > > 7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= > &nbsp;&nbsp;&nbsp;&nbsp;=20 > PO-&nbsp;&nbsp; /data01/root_rmgr<BR></STRONG>4015da98 2&nbsp;&nbsp;=20 > 2&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 > 7500&nbsp;&nbsp;&nbsp;&nbsp;=20 > 6991&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= > sp;&nbsp;=20 > PO-&nbsp;&nbsp; /appl/tmp/tmp1_rmgr<BR>4015dc08 3&nbsp;&nbsp; = > 3&nbsp;&nbsp;=20 > 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 125000&nbsp;&nbsp;=20 > 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= > &nbsp;&nbsp;&nbsp;&nbsp;=20 > PO-&nbsp;&nbsp; /data01/dbs01_rmgr<BR>4015dd78 4&nbsp;&nbsp; = > 4&nbsp;&nbsp;=20 > 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 125000&nbsp;&nbsp;=20 > 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= > &nbsp;&nbsp;&nbsp;&nbsp;=20 > PO-&nbsp;&nbsp; /data02/dbs02_rmgr<BR>400ffac0 5&nbsp;&nbsp; = > 5&nbsp;&nbsp;=20 > 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2500&nbsp;&nbsp;&nbsp;&nbsp; = > > 197&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs= > p;&nbsp;&nbsp;=20 > PO-&nbsp;&nbsp; /data01/phys_rmgr<BR>400ffc30 6&nbsp;&nbsp; = > 6&nbsp;&nbsp;=20 > 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&nbsp;&nbsp;&nbsp;&nbsp; = > > 6959&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= > sp;&nbsp;=20 > PO-&nbsp;&nbsp; /data01/tmp2_rmgr<BR>400ffda0 7&nbsp;&nbsp; = > 7&nbsp;&nbsp;=20 > 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7500&nbsp;&nbsp;&nbsp;&nbsp; = > > 6951&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= > sp;&nbsp;=20 > PO-&nbsp;&nbsp; /data02/tmp3_rmgr<BR>4014e030 8&nbsp;&nbsp; = > 8&nbsp;&nbsp;=20 > 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = > 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 > 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= > ;&nbsp;&nbsp;&nbsp;=20 > PO-&nbsp;&nbsp; /data01/logic1_rmgr<BR>4014e1a0 9&nbsp;&nbsp; = > 9&nbsp;&nbsp;=20 > 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = > 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 > 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= > ;&nbsp;&nbsp;&nbsp;=20 > PO-&nbsp;&nbsp; /data01/logic2_rmgr<BR>4014e310 10&nbsp; 10&nbsp;=20 > 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = > 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 > 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= > ;&nbsp;&nbsp;&nbsp;=20 > PO-&nbsp;&nbsp; /data01/logic3_rmgr<BR>4014e480 11&nbsp; 11&nbsp;=20 > 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = > 500&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 > 47&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= > ;&nbsp;&nb

↪ replying to Mark Scranton
Peter J Diaz de Leon — — source: IIUG Forums & Mailing Lists

> > >I believe there is a utility that will clean up/sync the onbar logs and the >sysutils database. Can't recall it's name. This may remove/purge >old/expired rows from the sysutils database. I really can't remember how >this works - anyone??? > >HTH - >Mark. > > > The command is omsync. It is described in the Informix Backup and Restore manual. -Peter

↪ replying to Peter J Diaz de Leon
Rahn Payne — — source: IIUG Forums & Mailing Lists

Thanks to all who replied! Your suggestions led me to the Documentation for IBM Informix Dynamic Server, Version 9.30 (Backup and Restore Guide), which gave me the format for this command: onsmsync -i "12 00:00:00" When I ran it, it deleted bar_action table rows older than 12 days from the sysutils database. This reclaimed space in rootdbs -- although I won't be able to tell until either the 'disk full' errors stop, or I can see over time in "onstat -d" that rootdbs is no longer growing (for a while). I plan to run this command about once a month. I will also add a chunk to rootdbs some time soon. Thanks again, Rahn ----- Original Message ----- From: Peter J Dia.... <pdiazdeleon@infinityhealthcare.com> To: <ids@iiug.org> Sent: Wednesday, January 29, 2003 11:57 AM Subject: Re: rootdbs full for IDS 9.3 [162] > > > > > >I believe there is a utility that will clean up/sync the onbar logs and the > >sysutils database. Can't recall it's name. This may remove/purge > >old/expired rows from the sysutils database. I really can't remember how > >this works - anyone??? > > > >HTH - > >Mark. > > > > > > > The command is omsync. It is described in the Informix Backup and > Restore manual. > > -Peter > > > >

↪ replying to Rahn Payne
Michael Lowe — — source: IIUG Forums & Mailing Lists

Rahn; Onbar is likely failing because there's no room to add space to the sysutils database. You are partially correct when you talk about the rootdbs size, but what's actually true is that you cannot change the size of the initial chunk (or any chunk, for that matter) once it's been created. The simplest solution would be to just add another chunk to the root dbspace. There are still some conditions to be aware of, but which may or may not be a factor in your case. The specific one I'm referring to is that all the system Reserved Pages and Extended Reserved Pages must fit into the initial chunk of the root dbspace. This becomes a factor when you're trying to add chunks and dbspaces to a large system with a very small initial root chunk (yours is pretty small) and there isn't enough room in that initial chunk to add Extended Reserved Pages. That doesn't seem to be your problem here, though, so the simplest thing would be to just add another chunk. Everything else that I'm aware of that lives in the root dbspace can live in any chunk of the root dbspace, so the concern's only if you're going to be adding lots more dbspaces and chunks. HTH... Mike =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Mike Lowe Certified Consulting Education Specialist Data Management Solutions IBM Software Group Tel: 303-773-5216 Tie Line: 565-5216 e-Fax: 413-674-2415 mlowe0@us.ibm.com WWW: ibm.com/software/data Hey all, I'm running IDS 9.3 and am getting the following message in my = bar_act.log: 2003-01-29 08:37:24 31598 37464 SQL -271 Could not insert new row = into the table. 2003-01-29 08:37:24 31598 37464 ISAM -131 ISAM error: no free disk = space My onstat -d looks like this: address chk/dbs offset size free bpages flags pathname 400ff918 1 1 0 7500 7 PO- = /data01/root_rmgr 4015da98 2 2 0 7500 6991 PO- = /appl/tmp/tmp1_rmgr 4015dc08 3 3 0 125000 0 PO- = /data01/dbs01_rmgr 4015dd78 4 4 0 125000 1 PO- = /data02/dbs02_rmgr 400ffac0 5 5 0 2500 197 PO- = /data01/phys_rmgr 400ffc30 6 6 0 7500 6959 PO- = /data01/tmp2_rmgr 400ffda0 7 7 0 7500 6951 PO- = /data02/tmp3_rmgr 4014e030 8 8 0 500 47 PO- = /data01/logic1_rmgr 4014e1a0 9 9 0 500 47 PO- = /data01/logic2_rmgr 4014e310 10 10 0 500 47 PO- = /data01/logic3_rmgr 4014e480 11 11 0 500 47 PO- = /data01/logic4_rmgr 4014e5f0 12 12 0 500 47 PO- = /data01/logic5_rmgr 4014e760 13 13 0 500 47 PO- = /data02/logic6_rmgr 4014e8d0 14 14 0 500 47 PO- = /data02/logic7_rmgr 4014ea40 15 15 0 500 47 PO- = /data02/logic8_rmgr 4014ebb0 16 16 0 500 47 PO- = /data02/logic9_rmgr 4014ed20 17 17 0 500 47 PO- = /data02/logic10_rmgr 4014ee90 18 3 125000 250000 313 PO- = /data01/dbs01_rmgr 40731018 19 4 125000 250000 30745 PO- = /data02/dbs02_rmgr 40731188 20 3 375000 100000 91805 PO- = /data01/dbs01_rmgr 407312f8 21 4 375000 100000 99997 PO- = /data02/dbs02_rmgr I suspect that it is the root_rmgr (rootdbs) that is too full to be = written to. Does anyone know how space can be restored to rootdbs? = According to the manuals and training, rootdbs is set once (at about = 30MB), can't be increased, and I didn't know it would fill up! I have = been very careful not to create tables in rootdbs. I think it has just = slowly filled. Thanks for any suggestions! Rahn Rahn Payne Rehab Manager, Inc. email: rpayne@rehabmgr.com

↪ replying to Rahn Payne
MALCOLM WEALLANS — — source: IIUG Forums & Mailing Lists

I read right to the bottom of your email and you are misleading yourself. It is possible to add a chunk to rootdbs, just like any other dbspace. It is also not fixed that rootdbs should be 30Mbyte. You can make it any size you like. I suspect that Mark Scranton is right in this case that you couldn't extend sysutils and you need to manage that database. Once that is done you shouldn't have any more problems but you should really consider your configuration. If I looked at your configuration I suspect that you have rootdbs, a few temp dbspaces, a dbspace for data, and a few dbspaces for logs. Each one quite small. I normally don't allocate one dbspace for each log but instead have 2 logs dbspaces on different drives if I have them. I then alternate the logs between the two dbspaces. I have never seen any advantage in separate dbspaces for each log or in any really small dbspaces. Each dbspace has an area allocated for the tblspace tblspace whcih is unused in logs dbspaces. I strongly recommend that you should plan a time when you can reconfigure your system. At that time you should dbexport the databases, reconfigure the disk space to remove the small dbspaces rebuild the databases using dbimport. regards Malcolm

Related threads

Glossary