1.2.3 Re-creating a database and changing its settings

(a) Manager (JP1/Base 09-00 or later)

The procedure differs depending on whether the integrated monitoring database is used.

If the integrated monitoring database for JP1/IM - Manager is not used

Using the jevdbinit command of JP1/Base, initialize the event database.

For details about how to initialize the event database of JP1/Base, see the description about initializing the event database in the chapter that explains how to set up the Event Service environment in the JP1/Base User's Guide.

If you changed the serial numbers by executing the jevdbinit command with the -s option, you must re-create the command execution log.

For details about how to re-create the command execution log, see 1.2.3(1) Re-creating the command execution log.

If the integrated monitoring database for JP1/IM - Manager is used

You can use the following procedure to initialize the event database:

1. Stop JP1/IM - Manager.

2. Execute the JP1/Base jevdbinit command without the -s option.

   If you execute the jevdbinit command without the -s option, the serial numbers in the pre-initialization event database are inherited.

If you changed the serial numbers by executing the jevdbinit command with the -s option, you must set up the integrated monitoring database again and re-create the command execution log.

Before setting up the integrated monitoring database again, unset up the database by executing the jcodbunsetup command.

For details about how to re-create the command execution log, see 1.2.3(1) Re-creating the command execution log.

For details about the jevdbinit command, see the chapter on commands in the JP1/Base User's Guide.

Note that if you execute the jevdbinit command with the -s option specified, you must use Central Scope to select the root monitoring node, change the status, and delete the status change event logs.

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

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 how to initialize the event database of JP1/Base, see the description about initializing the event database in the chapter that explains how to set up the Event Service environment in the JP1/Base User's Guide.

Important

If an agent initializes the event database, JP1/Base discards the events without registering them in the event database. Consequently, if the correct procedure is not followed, it might become impossible to transfer some of the events after the event database is initialized.

(c) 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.

Important

If an agent initializes the event database, JP1/Base discards the events without registering them in the event database. Consequently, if the correct procedure is not followed, it might become impossible to transfer some of the events after the event database is initialized.

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 sections that describe the settings for JP1 event forwarding in the chapter that explains how to set up an Event Service environment in the JP1/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 JP1/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.

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

The procedure for expanding the IM database size differs depending on whether you need to continue system monitoring without using the IM database during the expansion process. The procedure for each scenario is described below.

• Procedure when monitoring events without using the IM database during the expansion process

1. Isolate the integrated monitoring database and the IM Configuration Management database.

   Isolate the integrated monitoring database and the IM Configuration Management database so that Central Console only uses the JP1/Base event database.

   Execute the following command, and then restart JP1/IM - Manager:

   jcoimdef -db OFF

   For details about the jcoimdef command, see jcoimdef (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

   If JP1/IM - MO is being used, also stop the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source.

2. Back up the database.

   Execute the jimdbbackup command with the -m EXPAND option specified.

   For details about the jimdbbackup command, see jimdbbackup (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API 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 size specified in the database size (IMDBSIZE) of the setup information file.

5. Stop JP1/IM - Manager.

6. Stop JP1/Base.

7. Restart the OS.

8. Start JP1/Base.

9. Start JP1/IM - Manager.

10. 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.

    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.

11. Recover the database.

    Execute the jimdbrecovery command with the -m EXPAND option specified.

    For details about the jimdbrecovery command, see jimdbrecovery (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

12. Restart the JP1/IM - Manager service.

    Execute the following command and then restart JP1/IM - Manager:

    jcoimdef -db ON

    For details about the jcoimdef command, see jcoimdef (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

    If JP1/IM - MO is being used, also start the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source.

13. When you are using the Intelligent Integrated Management Base, execute the jddupdatetree command in new and rebuilding mode.

    For details about the jddupdatetree command, see jddupdatetree in Chapter 1. Commands in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

• Procedure when stopping system monitoring via Central Console

1. Stop the JP1/IM - Manager service.

2. Back up the database.

   Execute the jimdbbackup command with the -m EXPAND option specified.

   For details about the jimdbbackup command, see jimdbbackup (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

3. Unset up 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 size specified in the database size (IMDBSIZE) parameter in the setup information file.

5. Stop JP1/Base.

6. Restart the OS.

7. Start JP1/Base.

8. Set up the integrated monitoring database and the IM Configuration Management database.

   Set up only those databases that you unset up in Step 3.

   During setup, you need to specify a database size that is larger than the size of the database you backed up, and the same database directory that was used during the backup.

9. Recover the database.

   Execute the jimdbrecovery command with the -m EXPAND option specified.

   For details about the jimdbrecovery command, see jimdbrecovery (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

10. Start the JP1/IM - Manager service.

11. When you are using the Intelligent Integrated Management Base, execute the jddupdatetree command in new and rebuilding mode.

    For details about the jddupdatetree command, see jddupdatetree in Chapter 1. Commands in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

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

The procedure for expanding the database size differs depending on whether you need to continue system monitoring via Central Console during the expansion process. The procedure for each scenario is described below.

• Procedure when continuing system monitoring via Central Console (with limited functionality)

1. Isolate the integrated monitoring database and the IM Configuration Management database.

   Isolate the integrated monitoring database and the IM Configuration Management database so that Central Console only uses the JP1/Base event database.

   Execute the following command, and then restart JP1/IM - Manager:

   jcoimdef -db OFF -h logical-host-name

   For details about the jcoimdef command, see jcoimdef (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

   If JP1/IM - MO is being used, also stop the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source.

2. Stop the cluster service (JP1/IM2 - Manager DB Cluster Service_logical-host-name) of the IM database.

   Stop the cluster service (JP1/IM-Manager DB Cluster Service_logical-host-name) of the IM database 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 (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API 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. Stop JP1/IM - Manager.

7. Stop JP1/Base.

8. Restart the OS.

9. Start JP1/Base.

10. Start JP1/IM - Manager.

11. 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.

12. Recover the database.

    Execute the jimdbrecovery command with the -m EXPAND option specified.

    For details about the jimdbrecovery command, see jimdbrecovery (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

13. Start the cluster service (JP1/IM2 - Manager DB Cluster Service_logical-host-name) of the IM database.

    Start the cluster service (JP1/IM2 - Manager DB Cluster Service_logical-host-name) of the IM database you stopped in Step 2.

14. Restart the JP1/IM - Manager service.

    Execute the following command and then restart JP1/IM - Manager:

    jcoimdef -db ON -h logical-host-name

    For details about the jcoimdef command, see jcoimdef (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

    If JP1/IM - MO is being used, also start the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source.

15. When you are using the Intelligent Integrated Management Base, execute the jddupdatetree command in new and rebuilding mode.

    For details about the jddupdatetree command, see jddupdatetree in Chapter 1. Commands in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

• Procedure when stopping system monitoring via Central Console

1. Stop the JP1/IM - Manager service and the cluster service (JP1/IM2 - Manager DB Cluster Service_logical-host-name) of the IM database.

   Stop the JP1/IM - Manager service and the cluster service (JP1/IM2 - Manager DB Cluster Service_logical-host-name) of the IM database registered in the cluster software.

2. Back up the database.

   Execute the jimdbbackup command with the -m EXPAND option specified.

   For details about the jimdbbackup command, see jimdbbackup (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

3. Unset up the integrated monitoring database and the IM Configuration Management database.

   Unset up only those databases that have been set up.

4. Edit the cluster setup information file.

   Change the size specified in the database size (IMDBSIZE) parameter in the cluster setup information file.

5. Stop JP1/Base.

6. Restart the OS.

7. Start JP1/Base.

8. Set up the integrated monitoring database and the IM Configuration Management database.

   Set up only those databases you unset up in Step 3.

   During setup, you need to specify a database size that is larger than the size of the database you backed up, and the same database directory that was used during the backup.

9. Recover the database.

   Execute the jimdbrecovery command with the -m EXPAND option specified.

   For details about the jimdbrecovery command, see jimdbrecovery (in Chapter 1. Commands) in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

10. Start the JP1/IM - Manager service and the cluster service (JP1/IM2 - Manager DB Cluster Service_logical-host-name) of the IM database.

    Start the JP1/IM - Manager service and cluster service (JP1/IM2 - Manager DB Cluster Service_logical-host-name) of the IM database you stopped in Step 1.

11. When you are using the Intelligent Integrated Management Base, execute the jddupdatetree command in new and rebuilding mode.

    For details about the jddupdatetree command, see jddupdatetree in Chapter 1. Commands in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.