Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Configuration Guide


1.4.1 Preparations for creating IM databases (for Windows)

You must prepare a setup information file that specifies the size of the database area required in order to create an IM database and information about the database storage directory.

To prepare for IM database creation:

  1. Edit the setup information file

    The following shows an example of the settings:

    #IM DATABASE SERVICE - DB Size

    IMDBSIZE=S

    #IM DATABASE SERVICE - Data Storage Directory

    IMDBDIR=Manager-path\database

    #IM DATABASE SERVICE - Port Number

    IMDBPORT=20700

    #IM DATABASE SERVICE - DB Install Directory

    IMDBENVDIR=Manager-path\dbms

    If JP1/IM - MO is being used and JP1/IM - Manager and JP1/IM - MO are located on separate hosts, you must add the item IMDBHOSTNAME in the setup information file. For details about the setup information file, see Setup information file (jimdbsetupinfo.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.

  2. Check the settings in the setup information file.

    Make sure of the following:

    • Network drives, Windows reserved device files, and paths containing symbolic links are not specified for IMDBENVDIR and IMDBDIR.

  3. In case of existing the Application Experience service, verify that the startup type of the Application Experience service is not disabled.

    If you specify Disabled for the service, executing the jcodbsetup command or jcfdbsetup command might result in the IM database setup failing with the following message:

    KNAN11141-E An error occurred during the creation of a system database area. (Error code: -1073741811)

    Important
    • Do not specify a path of 200 or more bytes for the system environment variable TEMP. If a path is 200 bytes or more, a setup or unsetup of the IM database might fail. If setup fails, revise the value of the system environment variable TEMP, and then unsetup the integrated monitoring database and the IM Configuration Management database. Then, set them up again. If unsetup fails, revise the value of system environment variable TEMP, and then perform unsetup for the integrated monitoring database and the IM Configuration Management database.

    • Make sure that there are sufficient disk space allocated under Manager-path while executing the jcodbsetup or jcfdbsetup command. If disk space is not enough, the jcodbsetup or jcfdbsetup command outputting the following message and terminating abnormally:

      KNAN11053-E An attempt to read a file failed. (file name = instdb.log)