Hitachi

Hitachi Advanced Database Setup and Operation Guide


11.18.6 Action to be taken if the maintenance processing is not performed

The maintenance processing is not performed when any of the following conditions are met:

If the maintenance processing is not performed for 24 hours, the KFAA51277-I message is output. The KFAA51277-I message will be output every 24 hours unless the maintenance processing is performed.

The following explains the action to be taken for each of the preceding conditions.

Organization of this subsection

(1) If a transaction or a command that connects to the HADB server is running

If a transaction or a command that connects to the HADB server is running, the maintenance processing is not performed to prevent the processing performance of the transaction or command from being affected. If a transaction or command is started while the maintenance processing is in progress, the maintenance processing is interrupted.

If the maintenance processing is not performed for a long time or if you expect that the maintenance processing will not be performed for a long time, periodically check whether reorganization of the column store table is necessary. If reorganization is necessary, perform reorganization. For details about how to check whether reorganization of the column store table is necessary, see the following subsections:

(2) If the HADB server is operating in quiescence mode

If the HADB server is operating in quiescence mode, the maintenance processing is not performed, because a database update is suppressed. The maintenance processing will be performed if you change the HADB server operation mode from quiescence mode to another mode.

For details about how to check the operation mode and how to change it, see 10.2.3 HADB server operation modes.

(3) If a node is returning to a multi-node configuration (if the multi-node function is used)

The maintenance processing is not performed while a node is returning to a multi-node configuration. The maintenance processing is performed when the node has returned to a multi-node configuration. For details about the process in which a node returns to a multi-node configuration, see 16.15.3 Returning a node to the multi-node configuration.