Copyright © 2010 Fidelity Information Services, Inc. All rights reserved.
October 26, 2010
Table of Contents
- About This Manual
- 1. About GT.M
- 2. Installing GT.M
- 3. Planning for GT.M
- 4. Global Directory Editor
- 5. MUPIP
- 6. GT.M Journaling
- 7. Database Replication
- 8. M Lock Utility
- 9. GT.M Database Structure(GDS)
- 10. Database Structure Editor
- 11. Maintaining Database Integrity
- Verifying Database Integrity
- Approaches to Database Recovery
- Repairing the Database with DSE
- 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
- Glossary
- Index
List of Figures
List of Tables