ADIC FileServ Version 4.0 600716 Rev A manual CheckDBALL

Administrative Tasks

	When the checkpoint script runs, it tars the entire contents of
	the FileServ database to a separate file system. After this
	process is completed, it zeros out the journal file. If the
	journaling file system becomes full, processing stops.
	Therefore, it is important to checkpoint the database regularly
	through a cron process.
	Checkpointing can be written to the host computer disk or table,
	but these files must not be placed under FileServ’s control.
checkDBALL	The $FS_HOME/util/checkDBALL script checks the
	database consistency by validating the position of each record
	occurrence and checking the integrity of deleted chains. The
	consistency check verifies that the member and owner record
	types are valid, the membership count is current, and the
	doubley linked lists are properly formed.
	The script also validates the existence of the key values
	associated with each record and the key field in the data files.
	For each key in the key file, the script reads the associated
	record and checks to ensure that the key’s data field contents
	match that stored in the key file. Finally, the checkDBALL
	script performs a timestamp consistency check on the database.
	The checkDBALL database script should always be run after a
	host platform crash because FileServ may have been
	performing a database transaction when the crash occurred.

1-12 System Tasks 600716 Rev A