NonStop S-Series Operations Guide (G06.24+)

Disk Drives: Monitoring and Recovery
HP NonStop S-Series Operations Guide—522459-007
9-15
Recovery Operations for a Nearly Full Database File
Recovery Operations for a Nearly Full Database File
When a database file is 90 percent full or more, you can modify the file extents
dynamically with FUP or perform other procedures as determined by your local system
policies.
To allocate additional extents to the file MEMOS:
> FUP
- ALTER MEMOS, MAXEXTENTS 20
- INFO MEMOS, DETAIL
A report such as this one is sent to your home terminal:
This report shows that the maximum number of extents allocated to this file has been
increased to 20 and that the file MEMOS is now only 78.5 percent full.
For more information about setting file extents, see the File Utility Program (FUP)
Reference Manual.
Recovery Operations for Performance Problems
Performance problems can have various causes, including path switches or a too small
cache size. For information about disk load balancing and increasing cache size, refer
to the SCF Reference Manual for the Storage Subsystem.
Recovery Operations for a Corrupt $SYSTEM Disk
If both disks of your mirrored system disk volume become corrupted, use an alternate
system disk if one is available. For information about how an alternate (emergency)
system disk is created, refer to the NonStop S-Series Planning and Configuration
Note. The allocation of additional extents to any file causes that file to take up more disk
space. Before you change the maximum allowable extents for any file, as shown in the next
example, check your local procedures to determine whether this is the appropriate action for
you to take.
$DATA.DATA1.MEMOS 12 Jul 1993, 14:05
ENSCRIBE
TYPE U
CODE 101
EXT ( 2 PAGES, 2 PAGES )
ODDUNSTR
MAXEXTENTS 20
BUFFERSIZE 4096
OWNER 8,255
SECURITY (RWEP): NUNU
DATA MODIF: 12 Jul 1993, 14:04
CREATION DATE: 12 Jan 1993, 14:04
LAST OPEN: 12 Jul 1993, 14:24
EOF 567022 (78.5% USED)
FILE LABEL: 649 (22.8% USED)
EXTENTS ALLOCATED: 10