17.14.1 Problems related to startup or termination of the cold standby configuration
This subsection explains the steps to take when a problem related to startup or termination of the cold standby configuration occurs.
- Organization of this subsection
(1) When the cold standby configuration cannot be started normally
The following table lists and describes possible reasons why the cold standby configuration cannot be started normally and the corrective actions to take.
|
No. |
Possible cause |
Action to take |
|---|---|---|
|
1 |
A failure has occurred in the active system or the standby system. |
Start the HADB server with the adbstart command, not HA Monitor's monbegin command. Note that in this case, the cold standby configuration is not used. Alternatively, if there is a substitute machine, set up the substitute machine's environment so that it is the same as the server machine on which the failure occurred. Then, start the HADB servers in the cold standby configuration by following the procedure in 17.4.1 How to start the cold standby configuration. |
|
2 |
The DB directory has not been mounted. |
Re-evaluate the values of the following operands specified in HA Monitor's servers file:
|
|
3 |
The DB directory has not been initialized correctly. |
Check if the DB directory had been mounted when the adbinit command was executed. |
If the cause is other than the above, eliminate the cause of the error according to the corrective action provided for the message that was output. Then, start the cold standby configuration according to the procedure described in17.4.1 How to start the cold standby configuration.
(2) When the cold standby configuration cannot be restarted
If a failure has occurred in the active system or the standby system, remove the system resulting in the failure from the cold standby configuration. Then, restart the cold standby configuration according to the procedure described in17.4.1 How to start the cold standby configuration.
For any other cause, eliminate the cause of the error according to the corrective action given for the message that was output. Then, restart the cold standby configuration according to the procedure described in17.4.1 How to start the cold standby configuration.
(3) When the cold standby configuration cannot be terminated
Eliminate the cause of the error according to the corrective action provided for the message that was output. Then, terminate the cold standby configuration according to the procedure described in17.4.2 How to terminate the cold standby configuration.
(4) When the HADB server cannot be started after hot standby processing
The following table lists and describes possible reasons why the HADB server cannot be started after hot standby processing and the corrective actions to take.
|
No. |
Possible cause |
Action to take |
|---|---|---|
|
1 |
The DB directory has not been mounted. |
Re-evaluate the values of the following operands specified in HA Monitor's servers file: • disk operand • fs_name operand • fs_mount_dir operand • fs_mount_opt operand |
|
2 |
The HADB server definitions do not match between the active system and the standby system. |
Ensure that the HADB server definitions match between the active system and the standby system. If the HADB server in the active system is terminated forcibly or abnormally, the HADB server's startup mode is restart. In this case, the restart processing fails if the number of threads and the size of the memory for the HADB server to be started are smaller than those of the HADB server in the active system before hot standby processing. |
|
3 |
When a DB area is expanded, a block special file that cannot be referenced by the standby system was specified. |
Take the following corrective action:
|
|
4 |
When a DB area is expanded, the path of the specified block special files differs from that specified in the standby system. |
We recommend that you use WWNs in such a manner that the paths are the same in both the active system and the standby system. DB area files in the DB directory are symbolic links to block special files. Manually change the links so that WWNs are used in paths. |
If the cause is other than the above, eliminate the cause of the error according to the corrective action provided for the message that was output. Then, restart the cold standby configuration according to the procedure described in17.4.1 How to start the cold standby configuration.