Maintaining Checkpoint Files Offline
If you do not have sufficient disk space for N sets of checkpoint and journal files, you must back up these files and
manually delete them from disk (see page
Delete Old Checkpoints Manually).
In the context of a live database, the checkpoint, the associated files (with the same checkpoint number) in the dmp directory, and all subsequent journal files are required to be able to restore that database. So you should remove only the set of files associated with the oldest checkpoint each time.
In addition, if the live database configuration file is lost or broken, you will also need the aaaaaaaa.cnf file from the dmp directory. Because the files in the dmp directory are usually small, it is easiest to simply back up the entire dmp directory.
Delete Old Checkpoints Manually
If you do not have disk space for all the checkpoints referenced in the database configuration file, or if some of the files are not referenced (as indicated by infodb dbname), you must delete these files manually.
To delete old checkpoints manually
Use an operating system command, as follows:
Windows: Use the Windows del command from the II_CHECKPOINT\ingres\ckp\dbname directory.
UNIX: Use the UNIX rm command from the ii_checkpoint/ingres/ckp/dbname directory, where ii_checkpoint is the value of II_CHECKPOINT as displayed by the ingprenv command.
VMS: Use the VMS delete command.