When Not to Change Installation Locations
Before changing an existing installation location, be sure that the change is really necessary: ask yourself what needs to be moved, and why.
Installation locations do not need to be changed if:
• The installation needs space for future growth.
• Existing databases are outgrowing their present disk partitions.
Allocation of Space for Future Growth
Ingres provides the capability of creating new locations and placing any new databases, tables, or indexes in these new locations. If the requirement is space for new tables or databases, you do not need to change existing locations.
Instead, create the necessary new locations for these future tables and databases and use the available location flags of createdb (-d, -c, -j, -b, and -w) to create the data, checkpoint, journal, dump, and work files for the newly created database in some other location.
For more information on creating new databases, see the createdb command in the Command Reference Guide.
Allocation of Additional Space for Existing Tables
If space is becoming limited on a disk partition containing a particularly large table, you can move the table to a new disk or partition. Use the MODIFY...TO RELOCATE and MODIFY...TO REORGANIZE statements as described in the Database Administrator Guide.
Last modified date: 01/30/2023