Database Checkpointing

The tools perform automatic checkpointing, recording transactions in the SD-UX depot catalog, or Installed Products Database (IPD) at the fileset level. Additionally, checkpointing at the file level is supported through attributes stored with the file.

During a swinstall or swcopy operation, all filesets in the current product being loaded are recorded in the depot catalog or IPD as having a state of transient. After all filesets in a product complete the copy or install, the state is changed to available or installed, and the next product is started. At this point, retrying an operation will not attempt to recopy or reinstall the filesets that are already installed (see “Retry Command”).

	NOTE: This behavior requires that either the product or fileset have a revision defined.

The current state and revisions of filesets can be displayed with the command:

swlist [-d] -l fileset -a revision -a state

If there is an error installing a fileset in the product that causes the install to fail (e.g., lost connection to the source), all filesets in the product are changed from transient to corrupt. (All filesets are assumed corrupt since the product level postinstall script has not been run yet. In actuality, the filesets may be properly installed.)

Independent of a fileset being installed (either properly or in a corrupt state) you can determine whether any particular file is installed properly with a high degree of certainty through the file’s size, mtime, and cksum attributes. Through these file attributes, checkpointing at the file level is approximated (this is described in the previous section).