Once you understand the cause of a database integrity problem, you can correct or improve the environment to prevent or minimize future damage. These changes may include hardware reconfiguration, such as improving the quality of power; changes to the operational procedures, such as implementing journaling; and/or changes to the Global Directories, such as balancing data assignment into files of more manageable sizes.
Use the following tools to help determine the cause of a database integrity problem.
Knowledge of the application and how it is used
Context dumps produced by application programs
Core dumps produced by application programs
Core dumps produced by GT.M
Interviews with users to discover their actions
The DCL command ANALYZE /ERROR to examine the OpenVMS error log
Review of messages in operator facility
Review of all recent changes to hardware, VMS, GT.M, the application, procedures, etc.
Copies of damaged files
The trail from DSE sessions in the form of notes, SET HOST /LOG files,a script file recording the session, sequential files, and saved blocks.