Hello,

we have an ingres db with a .t00 file with 2gb size. the db logs errors
like
NFS001 ::[32781 , 09856100]: Sat Apr 3 23:09:16 2004
E_DM9000_BAD_FILE_ALLOCATE Disk file allocation error on
database:cadbase table:astpdat
pathname:/opt/ingresii/ingres/data/default/cadbase filename:aaaaabcn.t00

the file aaaaabcn.t00 is 2gb large. ckpdb only tries to stall the db and
waits with select(), but does nothing else.

our question is now, how to get the db running. Any help appreciated.

regards,
Andreas

Hi Andreas,

The database should be perfectly okay until you attempt to access the
table astpdat. At which point this error will be generated because the OS
does not support a 2G file.

If the database comes up okay. Dont do a checkpoint.

You now have to reorganize the table over multiple data locations.

To do this you must have an alternate data location. If you only have an
II_DATABASE defined and no other areas set up for data then the easiest
option is to make an 'internal' data location on II_DATABASE.
eg. mkdir `ingprenv II_DATABASE`/ingres/data/dbdata2
chmod 777 `ingprenv II_DATABASE`/ingres/data/dbdata2

Then define this area as an alternate data location by using accessdb
or via:
sql iidbdb << SQL_END
create location ii_database_2 with area = 'dbdata2',
usage=(database);
\g
SQL_END

Having made the alternate location or if you already have an alternate
location defined then simply spread the database to that location. This
can best be done using accessdb.

You should now be able to reorganize the table to mult-location eg.
sql cadbase << SQL_END
/* Note that this preserves the table structure and its indexes */
modify astpdat to reorganize with location=(ii_database,ii_database_2);
commit
\p\g
\q
SQL_END

After this statement succeeds you'll have two 1G files that make up the
table. One will be a .t01 file in II_DATABASE and the other a .t01 in
ii_database_2. The checkpoint should now work perfectly well. And now is a
good time to take it!

The only source of problem I can see for you is that the table is already
very large and that the system may not allow the reorg. There are some
games we can play if that happens.

If all is cool, I recomend that you create a table monitoring script that
checks regurly how big tables are and records this in a meaningful manner
for later analysis.

Martin Bowes

>
> Hello,
>
> we have an ingres db with a .t00 file with 2gb size. the db logs errors
> like
> NFS001 ::[32781 , 09856100]: Sat Apr 3 23:09:16 2004
> E_DM9000_BAD_FILE_ALLOCATE Disk file allocation error on
> database:cadbase table:astpdat
> pathname:/opt/ingresii/ingres/data/default/cadbase filename:aaaaabcn.t00
>
> the file aaaaabcn.t00 is 2gb large. ckpdb only tries to stall the db and
> waits with select(), but does nothing else.
>
> our question is now, how to get the db running. Any help appreciated.
>
> regards,
> Andreas
>


--
Random Titus Quote #14:
Born free. Taxed to death.