Nonstop Database, HiRDB Version 9 System Operation Guide

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

29.6 Troubleshooting

When a HiRDB expansion unit is used, the status managed by the system manager may differ from the status managed by the HiRDB expansion unit when certain errors occur. In such a case, a problem can occur such as the HiRDB expansion unit not automatically starting during a restart, in response to which corrective action must be taken.

This section explains the system status and condition when an error occurs and the corrective action that can be taken. For details about recovering a database from errors that are not explained here, see 20. Error Handling Procedures.

Table 29-2 System status and condition when an error occurs and the corrective action that can be taken

System status when an error occurs Condition Refer to this subsection for corrective action
During HiRDB startup (between KFPS01800-I and KFPS05271-I) The unit in which the system manager is located terminates abnormally and message KFPS05276-E is output. (1) Corrective measure 1
The unit in which the system manager is located terminates abnormally and message KFPS04695-I is output, but not KFPS05273-I. (2) Corrective measure 2
When HiRDB has started normally (between KFPS05220-I and KFPS01850-I) Messages KFPS05275-W and KFPS01850-I are output. (3) Corrective measure 3
Message KFPS05275-W is output, but not KFPS01850-I. (4) Corrective measure 4
The unit in which the system manager is located terminates abnormally. (5) Corrective measure 5
During HiRDB expansion unit startup (between KFPS1800-I and KFPS05273-I) Message KFPS05275-W is output. (6) Corrective measure 6
The unit in which the system manager is located terminates abnormally. (7) Corrective measure 7
System switchover occurs in the unit in which the system manager is located. (8) Corrective measure 8
HiRDB expansion unit is terminating (between KFPS01840-I and KFPS05274-I) Message KFPS5275-W is output. (9) Corrective measure 9
The unit in which the system manager is located terminates abnormally. (10) Corrective measure 10
HiRDB expansion unit is running When HiRDB restarts following abnormal termination, the server machine in which the HiRDB expansion unit is located cannot start because of a problem such as a hardware error (11) Corrective measure 11
Organization of this section
(1) Corrective measure 1
(2) Corrective measure 2
(3) Corrective measure 3
(4) Corrective measure 4
(5) Corrective measure 5
(6) Corrective measure 6
(7) Corrective measure 7
(8) Corrective measure 8
(9) Corrective measure 9
(10) Corrective measure 10
(11) Corrective measure 11

(1) Corrective measure 1

The corrective procedure follows:

Procedure
  1. Recover from the error by following the instructions in message KFPS05276-E.
  2. Execute the pdls -d ust command in all base units and check their operating status. If a unit's status is STARTING (in the process of starting), use the pdstop -z command to terminate that unit.
  3. Re-execute the pdstart command to start HiRDB.

(2) Corrective measure 2

The corrective procedure follows:

Procedure
  1. Execute the pdls -d ust command in the HiRDB expansion unit displayed in message KFPS04695-I, and check that unit's operating status.
  2. If the unit's status is STARTING (in the process of starting) or ONLINE (running), use the pdstop -z command to terminate that unit once, and then execute the pdstart -q command to start the unit.

(3) Corrective measure 3

Refer to the message that is output before message KFPS05275-W and remove the cause of the error. The status of the HiRDB expansion unit is correctly managed. No action is necessary with regard to the HiRDB expansion unit.

(4) Corrective measure 4

The corrective procedure follows:

Procedure
  1. Refer to the message that was output before message KFPS05275-W and remove the cause of the error.
  2. Execute the pdls -d ust command in the HiRDB expansion unit displayed in message KFPS05275-W, and check that unit's operating status.
  3. If the HiRDB expansion unit's status is ONLINE (running) or STOPPING (being stopped), use the pdstop -z command to terminate that unit once, and then execute the pdstart -q command to start the unit.

The next time HiRDB starts, the HiRDB expansion unit displayed in message KFPS05275-W may start. If the HiRDB expansion unit starts the next time HiRDB starts, use the pdstop -u command to terminate the unit.

(5) Corrective measure 5

The corrective procedure follows:

Procedure
  1. Execute the pdls -d ust command in the HiRDB expansion unit displayed in message KFPS01840-I, and check that unit's operating status.
  2. If the HiRDB expansion unit's status is ONLINE (running) or STOPPING (being stopped), use the pdstop -z command to terminate that unit once, and then execute the pdstart -q command to start the unit.

The next time HiRDB starts, the HiRDB expansion unit displayed in message KFPS01840-I may start. If the HiRDB expansion unit starts the next time HiRDB starts, use the pdstop -u command to terminate the HiRDB expansion unit.

(6) Corrective measure 6

The corrective procedure follows:

Procedure
  1. Refer to the message that was output before message KFPS05275-W and remove the cause of the error.
  2. Use the pdstop -u command to terminate the HiRDB expansion unit displayed in the message KFPS05275-W, and then use the pdstart -u command to start it.

(7) Corrective measure 7

The corrective procedure follows:

Procedure
  1. Execute the pdls -d ust command in the HiRDB expansion unit displayed in message KFPS01800-I, and check that unit's operating status.
  2. If the HiRDB expansion unit's status is STARTING (in the process of starting) or ONLINE (running), use the pdstop -z command to terminate that unit once, and then execute the pdstart -q command to start the unit.

The next time HiRDB starts, the HiRDB expansion unit displayed in message KFPS01800-I may not start. If the HiRDB expansion unit does not start the next time HiRDB starts, use the pdstart -u command to start the unit.

(8) Corrective measure 8

The corrective procedure follows:

Procedure
  1. Execute the pdls -d ust command in the HiRDB expansion unit displayed in message KFPS01800-I, and check that unit's operating status.
  2. If the HiRDB expansion unit's status is STARTING (in the process of starting) or ONLINE (running), use the pdstop -z command to terminate that unit once, and then execute the pdstart -q command to start the unit.

(9) Corrective measure 9

The corrective procedure follows:

Procedure
  1. Refer to the message that was output before the message KFPS05275-W and remove the cause of the error.
  2. Use the pdstart -u command to start the HiRDB expansion unit displayed in message KFPS05275-W, and then use the pdstop -u command to terminate it.

(10) Corrective measure 10

The corrective procedure follows:

Procedure
  1. Execute the pdls -d ust command in the HiRDB expansion unit displayed in message KFPS01840-I, and check that unit's operating status.
  2. If the HiRDB expansion unit's status is ONLINE (running) or STOPPING (being stopped), use the pdstop -z command to terminate that unit once, and then execute the pdstart -q command to start the unit.

The next time HiRDB starts, the HiRDB expansion unit displayed in message KFPS01840-I may start. If the HiRDB expansion unit starts the next time HiRDB starts, use the pdstop -u command to terminate the unit.

(11) Corrective measure 11

If HiRDB terminates abnormally and restarts while a HiRDB expansion unit is active, the HiRDB expansion unit that was active during the previous session also starts. During this process, if the HiRDB expansion unit does not start because of a a problem such as a hardware error, HiRDB cannot start. In such a case, HiRDB can be started using the reduced activation facility even when the HiRDB expansion unit does not start.

However, if a HiRDB expansion unit and the reduced activation facility are used together#, the HiRDB start processing completion point differs from the reduced activation completion point, as shown below in Table 28-3. Keep each processing completion point in mind during operation.

#:
That is, if the same unit is specified in both the pd_start_skip_unit and pd_system_expand_unit operands.

Table 29-3 Units that start when the pdstart command is executed, and start processing and reduced activation completion points

HiRDB expansion unit termination status during the previous session# Units that start HiRDB start processing completion point (KFPS05210-I output) Reduced activation completion point (KFPS05217-I output)
Normal termination All base units except the unit specified in the pd_start_skip_unit operand Start processing completion point of all base units One of the following, whichever is earlier:
  • Start processing completion point of all base units except the unit specified in the pd_start_skip_unit operand
  • Point at which the value specified in the pd_reduced_check_time operand is exceeded
Planned termination
Forced termination
Abnormal termination		 All base units and HiRDB expansion units except the unit specified in the pd_start_skip_unit operand Start processing completion point of all base units and HiRDB expansion units One of the following, whichever is earlier:
  • Start processing completion point of all base units and HiRDB expansion units except the unit specified in the pd_start_skip_unit operand
  • Point at which the value specified in the pd_reduced_check_time operand is exceeded

#:
You can check how the HiRDB expansion unit terminated during the previous session based on whether message KFPS05274-I was output. If this message was output, normal termination occurred. If not, planned termination, forced termination, or abnormal termination occurred.

[Contents][Back][Next]

[Trademarks]

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