Was this helpful?
Format of the Checkpoint Template File in UNIX
The checkpoint template file, cktmpl.def, uses the UNIX tar command. This file can be found in $II_SYSTEM/ingres/files.
Each line is a command preceded by a four-character code that instructs the checkpoint operation when to use the command.
By altering this file you can change how checkpoints are performed. You can add or delete flags from the tar commands or you can supply your own shell scripts to perform the backup and restore steps.
For example, the command:
BSTD: echo beginning checkpoint to tape %C of 
      %N locations
indicates what is done initially, before the device is used (B), when the checkpoint operation is used to save (S) a database location to tape (T) for a database (D).
As another example, when executing a checkpoint on a database that spans multiple locations, the following command is executed once for each location:
PSTD: echo mount tape %N and press return;
      read foo;
WSTD: cd %D; /bin/tar cbf 20 %C *
The command instructs the checkpoint operation to save each location on a tape and to use the tar command with the parameter cbf 20. The checkpoint utility automatically substitutes the appropriate value for “%N,” “%D,” and “%C.”
Alternate Checkpoint Template Files (UNIX and Linux)
UNIX: An alternate checkpoint template file, cktmpl_cpio.def, uses the UNIX cpio command to back up and restore the database files.
Linux: An alternate checkpoint template file, cktmpl_ocfs.def, is for use with the Oracle Cluster File System (OCFS) on Linux.
The alternate file can be found in $II_SYSTEM/ingres/files.
To use an alternate template file and override the default cktmpl.def template file, use the ingsetenv command. For example:
ingsetenv II_CKTMPL_FILE $II_SYSTEM/ingres/files/cktmpl_cpio.def
Last modified date: 11/28/2023