Disk Drives: Monitoring and Recovery

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 according to your system policies.

Note. Allocating 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.

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:

$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

This report shows that the maximum extents allocated to this file have been increased to 20 and that the file MEMOS is now only 78.5% full.

Related Reading

For information about

Complete syntax, examples, and considerations for the SCF commands used in this section

Utilities such as:

DCOM

DSAP

BACKUP

RESTORE

See

SCF Reference Manual for the Storage Subsystem

Guardian Disk and Tape Utilities Reference Manual

Other operations procedures involving disk drives

Guardian User’s Guide

HP Integrity NonStop NS-Series Operations Guide529869-005

10-15

Page 149
Image 149
HP NonStop NS manual Recovery Operations for a Nearly Full Database File, FUP Alter MEMOS, Maxextents Info MEMOS, Detail