Managing, Resizing, and Repairing Database Files
A good discussion regarding UniVerse Files can be found on Rocket Software's Documentation Site. Please review this entire document for a good basic description of UniVerse's database layout and terminolgy.
To maintain optimum Database performance, data files should be checked proactively and regularly in order to RESIZE any files that have grown or shrunk or that have records in overflow. Checking files for ecorrupt data should also be performed regularly. A good method for this latter would be to use the uvbackup utility, as follows (UVHOME represents the folder where UniVerse is installed):
Windows: UVHOME\bin\uvbackup -f -v -walk . > nul 2> c:\temp\files.out
*nix: UVHOME/bin/uvbackup -f -v -walk . > /dev/null 2> /tmp/files.outThis sends the output of the backup to null and the file corruption data to files.out. Review this file to see which files need fixing.
The fixtool and the fixtool_sa (fixtool standalone) utilities can be used to verify and repair UniVerse files. Always make a backup before using the tool to fix files. The options, except the -force option in the case of the fixtool_sa utility, are the same for both tools.
To maintain proper sizing there are a few commands to use:
ACCOUNT.FILE.STATS with the LOCAL option stores the statistics in the local STAT.FILE
LIST.FILE.STATS will display to the terminal the collected file data. This can be printed using the LPTR or (P (flavor dependent) option
FILE.STAT is used to display Hashed file statistics
ANALYZE.FILE is used to display Dynamic file statistics
Again, the Rocket Software Documentation Site (using version 11.4.1 as a starting point) is the resource for information regarding all aspects of UniVerse.