Job Management Partner 1/Integrated Management - Manager Administration Guide

1.2.3 Re-creating a database and changing its settings

Organization of this subsection

(1) Re-creating the command execution log

(2) Procedure for re-creating the monitored object database and the host information database

(3) Procedure for re-creating the event database

(4) Procedures for expanding the IM database size

(5) Procedure for changing the IM database port

(6) Procedure for rebuilding the IM database following a host name change

(1) Re-creating the command execution log

To re-create the command execution log:

1. Stop JP1/IM - Manager.
2. Stop JP1/Base.
3. Delete the command execution log file, the action information file, and the action hosts file shown in the table below.
   

   In Windows:

   Table 1-7 Files to delete (Windows)

   Information type	Files to delete
   Command execution log file	All files under Base-path\log\COMMAND\
   	All files under shared-folder\jp1base\log\COMMAND
   Action information file	Console-path\log\action\actinf.log
   	shared-folder\jp1cons\log\action\actinf.log
   Action hosts file	Console-path\log\action\acttxt{1|2}.log
   	shared-folder\jp1cons\log\action\acttxt{1|2}.log

   In UNIX:

   Table 1-8 Files to delete (UNIX)

   Information type	Files to delete
   Command execution log file	All files under /var/opt/jp1base/log/COMMAND/
   	All files under shared-directory/jp1base/log/COMMAND/
   Action information file	/var/opt/jp1cons/log/action/actinf.log
   	shared-directory/jp1cons/log/action/actinf.log
   Action hosts file	/var/opt/jp1cons/log/action/acttxt{1|2}.log
   	shared-directory/jp1cons/log/action/acttxt{1|2}.log

4. Start JP1/Base.
5. Start JP1/IM - Manager.

Restarting JP1/Base and JP1/IM - Manager and executing a command from JP1/IM - View or an automated action re-creates the command execution log.

(2) Procedure for re-creating the monitored object database and the host information database

To re-create the monitored object database and the host information database:

1. Stop JP1/IM - Manager.
2. Back up the files.
   Back up the Scope-path\database\ folder.
   
3. Re-create the monitored object database.
   Executing the jcsdbsetup -f command deletes the existing monitored object database, and then re-creates the object database.
   
4. Re-create the host information database.
   First, delete the files from the Scope-path\database\jcshosts\ folder, and then execute the following command:
   jcshostsimport -r host-information-file (jcs_hosts)
   
5. Start JP1/IM - Manager.

(3) Procedure for re-creating the event database

The procedure differs depending on the version of JP1/Base that is installed on the target host whose event database you are re-creating.

(a) Manager and Agent (JP1/Base 07-51 or later)

Using the jevdbinit command of JP1/Base, initialize the event database. There is no need to delete and re-create the event database.

For details about the procedure, in the Job Management Partner 1/Base User's Guide, see the chapter that explains Event Service environment setup, and see Procedure for initializing Event Service in the Event Service troubleshooting section.

(b) Agent (JP1/Base 07-00 or earlier)

When an event database is re-created, the following problem occurs:

• At the JP1 event forwarding destination host, the processing performance for accepting, registering, and acquiring JP1 events deteriorates.

This is because re-creation initializes the event database at the forwarding source, creating a mismatch with the management information in the event database at the forwarding destination.

To prevent this problem from occurring, re-create event databases using the following procedure.

To re-create event databases:

1. Stop JP1/Base.
2. Stop JP1/Base at all forwarding destination hosts defined in the forwarding setting file (forward) of the JP1/Base you stopped in Step 1.
   If data is forwarded from the JP1/Base at the forwarding destination host to yet another host, stop this forwarding destination as well. If JP1/IM - Manager has been installed on the host that is to be stopped, stop JP1/IM - Manager beforehand.
   For details about the forwarding setting file (forward), see the chapter that explains Event Service environment setup and setup of JP1 event forwarding in the Job Management Partner 1/Base User's Guide.
   
3. Delete the event databases of the JP1/Bases you stopped in Steps 1 and 2.
   If you need to view the content of the event databases, use the jevexport command of JP1/Base to output this content to a CSV file. Note that you cannot re-create an event database from an output CSV file.
   For details about the jevexport command, see the chapter on commands in the Job Management Partner 1/Base User's Guide.
   
4. Start the JP1/Base (and JP1/IM - Manager) that you stopped in Step 2.
5. Start the JP1/Base that you stopped in Step 1.

Starting JP1/Base in Steps 4 and 5 re-creates the event databases.

For this example, assume that event databases will be re-created in the system configuration shown in the following figure.

Figure 1-1 Example showing hosts and forwarding destination hosts on which event databases are to be re-created

To re-create (delete) the event database of host A, it is necessary to delete the event databases of Hosts C and F, which are the forwarding destination hosts for JP1 events.

(4) Procedures for expanding the IM database size

This subsection explains how to expand the IM database size on a physical host, and in a cluster environment.

(a) Procedure for expanding the IM database size on a physical host

To expand the IM database size on a physical host:

1. Switch the database being used by Central Console.
   During database size extension, if you need to continue system monitoring via Central Console (although its functionality is somewhat more limited), switch the database being used by Central Console to the JP1/Base event database.
   
2. Stop the JP1/IM - Manager service.
   If you switched the database being used by Central Console to the JP1/Base event database of JP1/Base, there is no need to stop the JP1/IM - Manager service.
   
3. Back up the database.
   Execute the jimdbbackup command with the -m EXPAND option specified.
   For details about the jimdbbackup command, see jimdbbackup (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
   
4. Unset up both the integrated monitoring database and the IM Configuration Management database.
   Unset up only those databases that have been set up.
   
5. Edit the setup information file.
   Change the size specified in the database size (IMDBSIZE) of the setup information file.
   
6. Set up both the integrated monitoring database and the IM Configuration Management database.
   Set up only those databases that were unset up in Step 4.
   During setup, you need to specify a database size that is larger than the backup size and the same database directory that was used during the backup.
   
7. Recover the database.
   Execute the jimdbrecovery command with the -m EXPAND option specified.
   For details about the jimdbrecovery command, see jimdbrecovery (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
   
8. Start the JP1/IM - Manager service.
   If you switched from the integrated monitoring database to the JP1/Base event database in Step 1, switch the database to be used to the integrated monitoring database.
   

(b) Procedure for expanding the IM database size in a cluster environment

To expand the IM database size in a cluster environment:

1. Switch the database being used by Central Console.
   During database size extension, if you need to continue system monitoring via Central Console (although its functionality is somewhat more limited), switch the database being used by Central Console to the JP1/Base event database.
   
2. Stop the JP1/IM - Manager service and the cluster database service.
   If you switched the database being used by Central Console to the JP1/Base event database in Step 1, there is no need to stop the JP1/IM - Manager service.
   Additionally, stop the cluster database service registered in the cluster software.
   
3. Back up the database.
   Execute the jimdbbackup command with the -m EXPAND option specified.
   For details about the jimdbbackup command, see jimdbbackup (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
   
4. Unset up the integrated monitoring database and the IM Configuration Management database.
   Unset up only those databases that have been set up.
   
5. Edit the cluster setup information file.
   Change the size specified in the database size (IMDBSIZE) of the cluster setup information file.
   
6. Set up the integrated monitoring database and the IM Configuration Management database.
   Set up only those databases that were unset up in Step 4.
   During setup, you need to specify a database size that is larger than the backup size and the same database directory that was used during the backup.
   
7. Recover the database.
   Execute the jimdbrecovery command with the -m EXPAND option specified.
   For details about the jimdbrecovery command, see jimdbrecovery (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
   
8. Start both the cluster database service and the JP1/IM - Manager service.
   Start the cluster database service and the JP1/IM - Manager service that were stopped in Step 2.
   If you switched from the integrated monitoring database to the JP1/Base event database in Step 1, switch the database to be used to the integrated monitoring database.
   

(5) Procedure for changing the IM database port

To change the IM database port:

1. Stop JP1/IM - Manager.
2. Back up the database.
   Execute the jimdbbackup command with the -m MAINT option specified.
   For details about the jimdbbackup command, see jimdbbackup (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
   
3. Unset up both the integrated monitoring database and the IM Configuration Management database.
   Unset up only those databases that have been set up.
   
4. Edit the setup information file.
   Change the port number described in the setup information file.
   
5. Set up both the integrated monitoring database and the IM Configuration Management database.
   Set up only those databases that were unset up in Step 3.
   
6. Recover the database.
   Execute the jimdbrecovery command with the -m MAINT option specified.
   For details about the jimdbrecovery command, see jimdbrecovery (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
   
7. Start JP1/IM - Manager.

(6) Procedure for rebuilding the IM database following a host name change

After you change the host name of a physical or logical host, you need to rebuild the IM database. The rebuilding procedure is described below. Note that when the host name of a logical host is changed, you need to re-register the service created in this procedure in the IM database service to be registered in the cluster software.

To rebuild the IM database following a host name change:

1. Stop JP1/IM - Manager.
2. Back up the database.
   Execute the jimdbbackup command with the -m MAINT option specified.
   For details about the jimdbbackup command, see jimdbbackup (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
   
3. Unset up both the integrated monitoring database and the IM Configuration Management database.
   Unset up only those databases that have been set up.
   
4. Change the JP1/IM - Manager host name.
5. Set up both the integrated monitoring database and the IM Configuration Management database.
   Set up only those databases that were unset up in Step 3.
   
6. Recover the database.
   Execute the jimdbrecovery command with the -m MAINT option specified.
   For details about the jimdbrecovery command, see jimdbrecovery (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
   
7. Start JP1/IM - Manager.
   Start the JP1/IM - Manager of the host to be changed. When you are setting up a logical host, you need to edit the logical host name in the cluster setup information file.
   

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.