OASIS uses the Adaptive Server Anywhere (ASA) configuration tool to manage your database service. This tool stores and protects the OASIS database. However, the database software will not perform a full database validation automatically. Users must perform this process manually. We recommend running this process at least once per quarter and storing the backup at an offsite location for easy recovery. We also recommend completing this process during non-peak hours, as it can place heavy strain on the server.
The recommended best practice is to run the validation on a separate machine from the production database using a copy of the backup database. However, a validation can be run on the production database after logging all users out and stopping the database service, then allowing the validation tool to start the database in read-only mode.
1. (Log all users out of OASIS if validating the production database and stop the production database in ASA Configuration using the Stop button.)
2. On the machine hosting the database, search for and launch ASA Configuration.
3. The Adaptive Server Anywhere window will appear.
4. Click Tools.
5. Select Verify Database from the drop-down list.
6. The Select database to verify window will appear.
7. Select the most current OASIS database copy or backup. For more information on obtaining a backup, click here. Note: if you are creating an off site copy of the database, select the database that was written to an external device.
8. Click Open.
9. ASA will begin validating the database. Note: as this process runs, the window status will read "Running..."
Here is an example of a successful completion:
If the validation process finds that your database is corrupt or incomplete, an "ABNORMAL END" message will appear. Contact customer support.
Here is an example of a failed validation:
Attempting to validate a backup database on the same server as the production database while the production database is running will result in the backup being started on an alternate port and the utility connecting to the production database on the default port. This shouldn't cause damage but will cause extreme performance issues, as well as not accomplishing the goal of validating the backup.