17.14.3 Command related problems (in the case of the cold standby configuration)
If an command-related problem occurs, first take the appropriate corrective action as explained in 15.2 Command-related problems. If this does not resolve the problem, read the information provided in this subsection.
- Organization of this subsection
(1) Steps to take when a command cannot be executed
The following table describes the possible reasons why the following commands cannot be executed, and the steps that can be taken:
-
adbimport
-
adbidxrebuild
-
adbmergechunk
-
adbunarchivechunk
-
adbreorgsystemdata
-
adbsyndict
|
No. |
Possible cause |
Action to take |
|---|---|---|
|
1 |
The file system storing the input data files that are used in data import processing has not been mounted. |
Re-examine the settings for the file systems that are shared. Share file systems in such a manner that their paths are the same between the active system and the standby system. |
|
2 |
The following file systems have not been mounted:
|
Re-evaluate the values of the following operands specified in HA Monitor's servers file:
If specified values are invalid, mount the file system manually and then re-execute the command. |
|
3 |
The path of the file system mount point differs between the active system and the standby system. |
Re-evaluate the values of the following operands specified in HA Monitor's servers file:
If specified values are invalid, mount the file system manually and then re-execute the command. If hot standby processing has occurred during command execution, but the following file systems can be referenced using the same paths in both the active system and the standby system, the command can be re-executed from the point where the processing was interrupted:
|