1.3.1 Managing the IM database capacity

The integrated monitoring databases used by JP1/IM are designed not to increase invalid areas, even during continued use. As long as the required capacity is secured, there is no need to check the database during operations.

Because data is written to the database created at setup, you basically do not have to consider capacity increase if the capacity is properly estimated at setup.

For details about increasing the log file size, see 1.3.2 Managing the log file size.

When the number of JP1 events exceeds the storage limit of the integrated monitoring database, JP1 events are automatically deleted. Therefore, you need to output and save JP1 event information regularly to prevent data loss.

To manage the disk capacity using the output-and-save operation:

1. View the information related to output-and-save operations.

   Executing the jcoevtreport -showsv command displays the information related to output-and-save operations. Based on this information, estimate the output-and-save frequency and the free space required for outputting and saving information.

   The following table shows the items that are displayed.

   Table 1‒11: Displayed items

   Displayed item	Description
   Percentage of events that have not been saved	Shows the percentage of JP1 events within the integrated monitoring database that have not been output or saved (the ratio relative to the maximum number of entries in the integrated monitoring database).
   Size of events that are have not been saved	Shows the data size of JP1 events within the integrated monitoring database that have not been output or saved (in megabytes). The size displayed is the size within the integrated monitoring database. CSV output will require 1.2 times the size of the displayed events that have not been output.
   Settings for deletion warning notification	Shows the value set as the deletion warning notification level. If the deletion warning notification is set to OFF, a hyphen (-) is displayed.

2. Output and save the events that have not been output.

   Executing the jcoevtreport -save command outputs to a CSV file all JP1 events that have not been output and saved.

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

If too many JP1 events occurred and regular output-and-save operations were too late for them, you can issue a deletion warning notification event. A deletion warning notification event reports when the percentage of JP1 events that have not been output and saved exceeds the deletion warning notification level.

To set up a deletion warning notification:

1. Enable the issuance of deletion warning notification events.

   Executing the jcoimdef -dbntc ON command enables the function that issues a deletion warning notification event when the percentage of JP1 events not output and saved within the integrated monitoring database exceeds the deletion warning notification level. This percentage is the ratio relative to the maximum number of entries in the integrated monitoring database. The default for the deletion warning notification event is OFF.

2. Specify a deletion warning notification level.

   Executing the jcoimdef -dbntcpos 70 command sets the percentage of JP1 events for issuing a deletion warning notification event to 70%.

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.

For details about when the IM Configuration Management database is used, see 1.2.1(5) Reorganization of the IM databases.

To Page Top