Database, Repair

 

[Revised Apr 06]

 

Because pharmacy data is so important, four levels of recovery from database corruption are provided;

 

1. 'Repair' (as below) runs a quick check on the database, and can fix some problems. It should tried if problems arise.

 

2. 'Compact database'  is a more thorough utility that rebuilds all indexes and clears out temporary data. It is part of the monthly preventative maintenance and can fix most database problems..

 

3. In the rare situation that both these fail 'Restore from backup' can usually be accomplished without loss of data due to the 'roll-forward' recovery ability which will enter for itself work done since the last backup was taken.

 

4. A 'Restore' is unlikely to fail, so if restoring does not help consider whether the disk might be full, and see how many *.tmp files exist and whether they are clogging the hard drive. Normally all *.tmp files can be deleted.... but note;

Warning; If the DOS 'QuickScript' program is on the same computer, do not erase all the TMP files as a file names index.tmp is used by QuickScript.

 

To 'Repair' the database

From the 'start menu' select Tools, Utilities, Database utilities, Repair.

It usually takes between 10 seconds and five minutes, depending on the amount of repair necessary.

 

If this utility cannot be reached through the start menu, go through the 'my computer' to c:\RxOne\repair.exe and click on that to run it directly.

 

Automatic 'Repair' of DB

[Warning, do not set this to work automatically unless requested by Help-desk]

This option will run an automatic 'Repair' and 'Compact' of the database overnight. (Tools, Options, Switchboard, Select Maintain Database Checkbox and enter a time for the maintenance to begin e.g. 2300). Note: The time entered must be after 1700hrs)

 

Failure of Rebuild

The 'repair' will sometimes fail if a non-standard database path is used, see below.

Only if problems still persist, see 'Rebuild database' below.

 

Failure of these functions

If any of these fail, it is possible that the database is in a non-standard position... see  'Non-standard database path' below.

 

Related Topics

Compact database

Corrupted database

Non-standard Database path

Repair database

Restore from backup

Roll-forward recovery of data