Rootdbs full
Howard's rootdbs filled up on IDS 9.21 under HP-UX 11, blocking logical-log backups and halting the system, with no free space in the volume group to extend the chunk. Suggestions included adding a chunk anywhere (even a cooked file) as a stopgap, checking oncheck -pe to see what occupies rootdbs, setting DBSPACETEMP so temp tables go elsewhere, moving tables with ALTER FRAGMENT or dbexport/dbimport, and adding logs in another dbspace then dropping the rootdbs ones. Howard resolved it by dropping and recreating the sysutils database. A side discussion noted cooked-file chunks (offset zero) are awkward to replace later with raw devices.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hello all, we have run out of space in the rootdbs dbspace which is preventing the logical-logs from backing up which in turn is stoping the system running. I was going to add more space to the raw-logical volume but it appears there is no space available within that area to add. What can I do to resolve this mess? Is there anyway to release space within the rootdbs? OS = HPUX 11.0 IDS= IDS9.21.FC4 Cheers, Howard
"Howard Jones" <howie_lfc@hotmail.com> wrote in message
news:yotHc.182$QW1.45@newsfe4-gui.ntli.net...
> Hello all,
>
> we have run out of space in the rootdbs dbspace which is preventing the
> logical-logs from backing up which in turn is stoping the system running.
> I was going to add more space to the raw-logical volume but it appears
there
> is no space available within that area to add.
>
> What can I do to resolve this mess?
> Is there anyway to release space within the rootdbs?
>
> OS = HPUX 11.0
> IDS= IDS9.21.FC4
To get yourself going in the short term, add a chunk to the root dbspace
from anywhere - even a cooked file will do.
Longer term, find out what's in the root dbspace. Post the relevant section
from the output of oncheck -pe so we can all have a look if you like .......
On Fri, 09 Jul 2004 05:17:18 -0400, Howard Jones wrote:
In addition, the rootdb space needed during logical log backup (and dbspace
backup for that matter) is likely temp space. Do you have any temp dbspaces?
Are they listed in the DBSPACETEMP environment variable? If not then
rootdbs is used for temp tables. As far as moving permanent stuff out of
rootdbs, it depends on what's there. You can ALTER FRAGMENT FOR ... INIT IN
... for a table (even a non-fragmented one) to move it to another dbspace(s).
However if the database itself lives in rootdbs the only way to move the
system catalog tables (which is a good idea performance wise) is to dbexport
the database, drop it, and dbimport it into another dbspace.
Art S. Kagel
> Hello all,
>
> we have run out of space in the rootdbs dbspace which is preventing the
> logical-logs from backing up which in turn is stoping the system running. I
> was going to add more space to the raw-logical volume but it appears there
> is no space available within that area to add.
>
> What can I do to resolve this mess?
> Is there anyway to release space within the rootdbs?
>
> OS = HPUX 11.0
> IDS= IDS9.21.FC4
>
> Cheers,
>
> Howard
To create space in the rootdbs you will need to add a chunk to the rootdbs, however I doubt this iwll help you resolve the problem as it sounds as if your logical logs are full. In order to activate any new logs you add you would need to take an archive and there would be o log spce to write the checkpoint record in the logical locks when you start the archive. I would suggest you contact your support vendor, but IDS 9.21 has passed its end of service date so unless you have a service extension contract with IBM they may not help. It looks like you may have to restore your last archive, but not backup the current logical log. Then you can restore to a point before the logical logs were full and redo any work you have lost. "Howard Jones" <howie_lfc@hotmail.com> wrote in message news:<yotHc.182$QW1.45@newsfe4-gui.ntli.net>... > Hello all, > > we have run out of space in the rootdbs dbspace which is preventing the > logical-logs from backing up which in turn is stoping the system running. > I was going to add more space to the raw-logical volume but it appears there > is no space available within that area to add. > > What can I do to resolve this mess? > Is there anyway to release space within the rootdbs? > > OS = HPUX 11.0 > IDS= IDS9.21.FC4 > > Cheers, > > Howard
Thanks everyone, I dropped and recreated the sysutils database and all is now working correctly, I guess it is time to upgrade! Thanks again, Howard "Howard Jones" <howie_lfc@hotmail.com> wrote in message news:yotHc.182$QW1.45@newsfe4-gui.ntli.net... > Hello all, > > we have run out of space in the rootdbs dbspace which is preventing the > logical-logs from backing up which in turn is stoping the system running. > I was going to add more space to the raw-logical volume but it appears there > is no space available within that area to add. > > What can I do to resolve this mess? > Is there anyway to release space within the rootdbs? > > OS = HPUX 11.0 > IDS= IDS9.21.FC4 > > Cheers, > > Howard > >
Well, try: 1. Adding logical logs in a different dbspace 2. Dropping logical logs in the rootdbs 3. Drop extra databases, tables, indexes in the rootdbs Step #3 will require logical log space, which you don't have in the rootdbs, which is the reason for step #1 and #2. You could also always call Informix tech support and ask them to dial-in. Hope these suggestions help. Brice Avila "Howard Jones" <howie_lfc@hotmail.com> wrote in message news:<yotHc.182$QW1.45@newsfe4-gui.ntli.net>... > Hello all, > > we have run out of space in the rootdbs dbspace which is preventing the > logical-logs from backing up which in turn is stoping the system running. > I was going to add more space to the raw-logical volume but it appears there > is no space available within that area to add. > > What can I do to resolve this mess? > Is there anyway to release space within the rootdbs? > > OS = HPUX 11.0 > IDS= IDS9.21.FC4 > > Cheers, > > Howard
Neil Truby wrote: > > To get yourself going in the short term, add a chunk to the root > dbspace from anywhere - even a cooked file will do. Although if it's a cooked file you'll have a hard time getting rid of it. Strive to attach a raw space.
"scottishpoet" <dryburghj@yahoo.com> wrote in message news:81714288.0407090853.6b8da294@posting.google.com... > I would suggest you contact your support vendor, but IDS 9.21 has > passed its end of service date so unless you have a service extension > contract with IBM they may not help. .... though you could upgrade to 9.40 just to get IBM to fix the problem then regress to 9.21 again straight away :-)
"Andrew Hamm" <ahamm@mail.com> wrote in message news:2l93vtFadf36U1@uni-berlin.de... > Neil Truby wrote: > > > > To get yourself going in the short term, add a chunk to the root > > dbspace from anywhere - even a cooked file will do. > > Although if it's a cooked file you'll have a hard time getting rid of it. > Strive to attach a raw space. Really? How about soft links and dd?
Neil Truby wrote: > "Andrew Hamm" <ahamm@mail.com> wrote in message > news:2l93vtFadf36U1@uni-berlin.de... >> Neil Truby wrote: >>> >>> To get yourself going in the short term, add a chunk to the root >>> dbspace from anywhere - even a cooked file will do. >> >> Although if it's a cooked file you'll have a hard time getting rid >> of it. Strive to attach a raw space. > > Really? > How about soft links and dd? How about you've added a chunk using a file, therefore with offset zero, and when it's time to shift to raw space, due to storage constraints you only have some spaces that require a non-zero offset? Actually, if the system is undermaintained, then i bet the physical and logical logs are in rootdbs, so just shifting the physical out to another dbspace will solve the immediate problem. Then the logicals can be moved and extended. If either of them are moved to a cooked file, they are one of the few data structures in the engine that can be moved to a chunk with a different offset.