SQL/MX 2.x Installation and Management Guide (H06.10+, J06.03+)

Performing Recovery Operations
HP NonStop SQL/MX Installation and Management Guide—544536-007
12-37
Recovering From SCF Commands
mxtool GOAWAY is an OSS command-line utility run from mxtool that removes
SQL/MX format file labels for both the resource and the data forks associated with a
Guardian file.
For more information about GOAWAY, including command syntax, see the SQL/MX
Reference Manual.
Recovering From SCF Commands
Incorrect use of SCF commands can cause serious and possibly irreparable
inconsistencies in an SQL/MX database.
If your site needs to use any of these SCF commands on a volume with SQL/MX
objects, you should first carefully plan a recovery:
•
ABORT DISK
•
ALTER DISK
°
, ALTNAME
°
, LABEL
°
, VOLNAME
•
INITIALIZE DISK
•
RENAME DISK
•
STOP DISK
•
START DISK
ABORT DISK
The ABORT DISK command puts a disk into the STOPPED state, substate
HARDDOWN, but leaves the disk process running. Do not use the stopped drive to
store production SQL/MX database files. Use the drive for a test database or for
temporary space for sort files. You must ensure that you can make the volume inactive
and revive the drive back to its original mirrored configuration with no effect on the
original database.
Use the ABORT DISK command on a volume to put a particular volume out of
operation. You can later use the START DISK command to put the same disk back into
operation. See START DISK and STOP DISK on page 12-39. Inconsistency is unlikely
if the disk brought up is identical to the disk brought down. Always perform a
STOPOPENS DISK on the volume and a CONTROL DISK, REFRESH on the volume
to ensure valid file labels before you make the volume inactive.
Note. mxtool GOAWAY does not remove corresponding metadata entries and does
not support ANSI names. Use the MXCI SHOWLABEL command to identify the
Guardian file names that correspond to ANSI object names.
Caution. You cannot use ABORT DISK on a volume and replace the volume with an earlier
version of that same volume without causing inconsistencies in the database.