1.2.1 Database reorganization
- Organization of this subsection
(1) Reorganization of the command execution log
There is no need to reorganize the command execution log.
(2) Reorganization of the monitored object database and the host information database
There is no need to reorganize the monitored object database or the host information database.
(4) Reorganization of the file for accumulated response-waiting events
There is no need to reorganize the file for accumulated response-waiting events.
(5) Reorganization of the IM databases
This subsection explains the procedure for reorganizing the IM databases.
Among the IM databases, when data is repeatedly added to and deleted from the IM Configuration Management database, the free space in the IM database can become fragmented. This can prevent additional items from being registered before the maximum number of hosts or properties has been reached. In addition, registering, updating, and deleting database entries might take extra time.
To prevent such occurrences, reorganize the IM databases at times such as the following.
-
When JP1/IM - Manager is stopped for regular backup operations
-
During annual creation and implementation of a reorganization execution plan
-
When the message KFPH00212-I or KFPH00213-W is output to the Windows Event Log (syslog)
When issues like the above occur, use the procedure below to release free space in the database. To release the free space in the database:
-
In Windows, check whether the IM database service (JP1/IM2 - Manager DB Server) is running.
-
Using the jimdbreclaim command, release the free space in the database.
-
Check whether any host information or profiles registered in the IM database are unnecessary, and delete those that are not needed.
If this procedure does not eliminate the occurrence of problems, you need to reorganize the IM database. The following describes the procedures for reorganizing the IM database on a physical host, and in a cluster environment.
(a) Reorganizing the IM database on a physical host
To reorganize the IM database on a physical host:
-
Check the service status.
-
In Windows, check whether the IM database service (JP1/IM2 - Manager DB Server) is running.
-
Check whether the JP1/IM-Manager service is stopped.
-
If JP1/IM - MO is being used, check whether the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source is stopped.
-
-
Stop the JP1/IM - Manager service.
If JP1/IM - MO is being used, also stop the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source.
-
Using the jimdbrorg command, reorganize the database.
For details about the jimdbrorg command, see jimdbrorg (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
-
Start the JP1/IM - Manager service.
If JP1/IM - MO is being used, also start the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source.
(b) Reorganizing the IM database in a cluster environment
In a cluster environment, execute the reorganization process on the executing host. Furthermore, the shared directory must be accessible.
To reorganize the IM database in a cluster environment:
-
Check the service status.
-
In Windows, check whether the IM database service (JP1/IM2 - Manager DB Server_logical-host-name) is running.
-
Check whether the JP1/IM-Manager service and the cluster service (JP1/IM2 - Manager DB Cluster Service_logical-host-name) of the IM database are stopped.
-
If JP1/IM - MO is being used, check whether the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source is stopped.
-
-
Using the jimdbrorg command, reorganize the database.
For details about the jimdbrorg command, see jimdbrorg (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
-
Start the JP1/IM - Manager service and the cluster service (JP1/IM2 - Manager DB Cluster Service_logical-host-name) of the IM database that was stopped in Step 1.
If JP1/IM - MO is being used, also start the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source.