Finding and Fixing Database Errors

C1–Possible Cache Control Problems
H1 - Process Hangs
Handling a Hung Process
H2–OpenVMS Status
H3–Database Access Problems
H4–Database Cache Problems
H5–Critical Section Problems
H6–OpenVMS Problems
H7–Disk Hardware Problems
H8–Application Problems
I1–MUPIP INTEG Errors
I2–GT.M Version Mismatch
I3–File Header Errors
I4–File Size Errors
I5–More Database Access Problems
I6–Transient Errors
I7–Database Rundown Problem
I8–Repair-Induced Problems
K1–Bad Key
K2–Keys Misplaced
K3–Block Doubly Allocated
K4–Pointer Problems
K5–Star Key Problems
K6–Compression Count Error
K7–Key Warning
M1–Bitmap Errors
M2–Bitmap Header Problems
O1–Bad Block
O2–Record Errors
O3–Data Block Errors
O4–Salvage of Data Blocks with Lost Indices
P1–Process Damage
Q1–Restricting Database Access
R1–GT.M Run-Time Errors
R2–Structural Database Integrity Errors
R3–Run-time Database Cache Problems
R4–Stopped Processes
R5–No More Room in the File
R6–GTMASSERT and GTMCHECK Errors
R7–Interlocked Queue Hardware Problems
R8–Database Tree Maximum Level Exceeded
R9–Read-only Process Blocked

The rest of this chapter is arranged loosely in the form of a decision tree. The material covers a wide range of scenarios and possible actions.

As you begin the decision-making process, follow these general guidelines from this point:

IF THE SYMPTOM IS A FAILURE TO PROCESS, refer to section H1.

IF THE SYMPTOM IS A MUPIP INTEG ERROR REPORT, refer to section I1. If you are investigating a particular error message, refer to the "MUPIP INTEG errors" table.

IF THE SYMPTOM IS A GT.M RUN-TIME ERROR REPORT, refer to section R1. If you are investigating a particular error message, refer to the"MUPIP INTEG errors" table.

To facilitate use of the material as a troubleshooting guide, the text in these sections refers to other sections with alphanumeric designators. Each alphanumeric section describes suggested actions to employ in handling a particular situation.