Nonstop Database, HiRDB Version 9 System Operation Guide

[Contents][Index][Back][Next]

20.8.1 Actions to be taken in the event of an error in the current file

The following table shows the actions to be taken in the event of an error in the current file.

Table 20-15 Actions to be taken in the event of an error in the current file

Item Condition at the time of an error HiRDB processing HiRDB administrator's action
1 There are spare files. Swaps the status files. Also issues the KFPS01062-I is output.
Shuts down the erroneous file and resumes processing using one of the spare files as the current file.		 Place the shutdown status file in spare status with the procedure shown in (1).
2 There are no spare files. Single operation of status file specified#1 Resumes processing, placing the status file in single operation mode. Also issues the KFPS01044-I message. Create a spare file immediately and return the status file operation mode to double operation.
Use the procedure shown in (1) or (2) to create a spare file. Then use the procedure shown in (3) to set a spare file as the current file.
3 Single operation of status file not specified#2 Abnormally terminates the unit containing the erroneous status file. Create a new status file and then restart the unit. For details about restarting the unit, see 20.8.2 Procedure for starting a HiRDB (unit) while there is an erroneous status file.
Then place the shutdown status file in spare status with the procedure shown in (1).
4 Error during single operation or error in both file versions during double operation Abnormally terminates the unit containing the erroneous status file. The unit cannot be restarted because needed information has been lost. See 20.8.3 Actions to be taken when a HiRDB (unit) cannot be restarted due to an error in both versions of the current file.
If there is no spare status file, create a new status file before starting the unit forcibly.

#1: Applicable when pd_syssts_singleoperation=continue was specified in the unit control information definition or pd_sts_singleoperation=continue was specified in the server definition.

#2: Applicable when pd_syssts_singleoperation=stop (default value) was specified in the unit control information definition or pd_sts_singleoperation=stop (default value) was specified in the server definition.

Organization of this subsection
(1) Placing shutdown files in spare status
(2) Placing reserved files in spare status
(3) Setting a reserved file as the current file

(1) Placing shutdown files in spare status

Procedure
  1. Use the pdls command to check for status files that have been shut down.
    For unit status files:
    pdls -d sts -u UNT1
    For server status files:
    pdls -d sts -s b001
  2. Check if an error has occurred at the disk storing status files that have been shut down. If an error has occurred, correct the error. Also check for a physical error (such as physical damage or a power outage), and for an OS or disk driver error; also check that the disk is enabled.
  3. Use the pdstsrm command to delete the status files in shutdown status.
    For unit status files:
    pdstsrm -u UNT1 -f /sysfile/usts1a
    pdstsrm -u UNT1 -f /sysfile/usts1b
    For server status files:
    pdstsrm -s b001 -f /sysfile/sstsb1a
    pdstsrm -s b001 -f /sysfile/sstsb1b
  4. Use the pdstsinit command to re-create the status files that were deleted in step 3.
    For unit status files:
    pdstsinit -u UNT1 -f /sysfile/usts1a -l 4096 -c 256
    pdstsinit -u UNT1 -f /sysfile/usts1b -l 4096 -c 256
    For server status files:
    pdstsinit -s b001 -f /sysfile/sstsb1a -l 4096 -c 256
    pdstsinit -s b001 -f /sysfile/sstsb1b -l 4096 -c 256
  5. Use the pdstsopen command to place in spare status the status files that were re-created in step 4.
    For unit status files:
    pdstsopen -u UNT1 -f /sysfile/usts1a
    pdstsopen -u UNT1 -f /sysfile/usts1b
    For server status files:
    pdstsopen -s b001 -f /sysfile/sstsb1a
    pdstsopen -s b001 -f /sysfile/sstsb1b
We recommend that after the command has executed you check whether the execution results are correct. For details on how to check command execution results, see the manual HiRDB Version 9 Command Reference.

(2) Placing reserved files in spare status

Procedure
  1. Use the pdls command to check for reserved status files.
    For unit status files:
    pdls -d sts -u UNT1
    For server status files:
    pdls -d sts -s b001
  2. Use the pdstsopen command to place the reserved status files in spare status.
    For unit status files:
    pdstsopen -u UNT1 -n usts1a
    For server status files:
    pdstsopen -s b001 -n sstsb01
We recommend that after the command has executed you check whether the execution results are correct. For details on how to check command execution results, see the manual HiRDB Version 9 Command Reference.

(3) Setting a reserved file as the current file

Procedure
  1. Use the pdstsswap command to set a reserved file as the current file.
    For a unit status file:
    pdstsswap -u UNT1
    For a server status file:
    pdstsswap -s b001
We recommend that after the command has executed you check whether the execution results are correct. For details on how to check command execution results, see the manual HiRDB Version 9 Command Reference.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2011, 2015, Hitachi, Ltd.