Guardian User's Guide

Using FUP for Basic File Management
Guardian User’s Guide—425266-001
7-22
Solving Common File Problems
Solving Common File Problems
Table 7-2 lists possible problems, causes, and solutions for common file problems. For
information about database files, see Section 19, Monitoring Hardware Components.
Table 7-2. Common File Problems
Problem Possible Causes Solution
Information in data
files becomes
inconsistent.
Transaction failures,
subsystem failures, disk
failures, or operator error.
Escalate the problem; database
recovery might be required. Refer to
the NonStop TM/MP Operations and
Recovery Guide for instructions on
database recovery.
Transactions and
queries directed at
certain files are slow.
Too many transactions are
directed at a single disk or
file: an alternate key is
needed.
Escalate the problem. Operations and
database management can decide
whether it is appropriate to move
files, partition files, or create alternate
key files or indexes.
Users or applications
have problems
accessing a certain file
or files.
Failure to open an alternate
key file (error 4).
Use the FUP commands ALTER or
LOAD ALTFILE.
File is not in the directory,
or the record is not in the
file (error 11).
Check syntax and reenter if
necessary. Use the RESTORE utility
to restore the file to disk.
File is in use (error 12). Wait and try later.
File is full (error 45). Make the file larger.
A security violation
occurred (error 48).
Check security setting and alter if
needed.
File is corrupted or bad
(error 59).
Escalate the problem to your
management.
A file or files are left
open when the system
is shut down.
Miscommunication, user
forgetfulness, or faulty or
incomplete system
shutdown procedures.
Use the FUP LISTOPENS command
to identify the user in question; notify
your management.