jimdbupdate

Function

This command updates an IM database that has already been set up. Execute this command after upgrading JP1/IM - Manager.

To Page Top

Format

jimdbupdate [-h logical-host-name] [-i] [-q]

To Page Top

Execution permission

In Windows: Administrator permissions (if the Windows UAC feature is enabled, the command is executed from the administrator console)

In UNIX: Superuser permissions

To Page Top

Storage directory

In Windows:

Manager-path\bin\imdb\

In UNIX:

/opt/jp1imm/bin/imdb/

To Page Top

Arguments

-h logical-host-name

When you are operating in a cluster system, this option specifies the name of the logical host where this command is to be executed. Execution of the command updates the IM database for the specified logical host. If you do not use a cluster system, specification of this option is not needed. Note that JP1_DEFAULT cannot be specified for the logical host name. In addition, the logical host name is case sensitive. For the logical host name, specify a logical host name set in JP1/Base in the correct form, especially case.

-i

Specify this option to update the IM database. If this option is omitted, a message asking whether the IM database needs to be updated is displayed.

-q

Specify this option to execute the command without requiring user confirmation.

To Page Top

Return values

To Page Top

Notes

• Before executing this command, make sure that the following execution conditions for this command are satisfied.

  Execution conditions

  • When this command is executed on the active server, the shared disk must be online and the logical host name must be able to be resolved.

  • In Windows, the IM database must be started.

    For a physical host:

    - JP1/IM - Manager DB Server

    For a logical host:

    - JP1/IM - Manager DB Server _logical-host-name

    In addition, the JP1/IM-Manager service and the cluster server of the IM database indicated below must be stopped. Note, however, that if the integrated monitoring database and the IM configuration management database are not used, it is not necessary to stop the JP1/IM - Manager service.

    For a physical host:

    - JP1/IM-Manager service (JP1/IM2-Manager)

    - Cluster service for the IM database (JP1/IM2-Manager DB Cluster Service)

    For a logical host:

    - JP1/IM-Manager service (JP1/IM2-Manager_logical-host-name)

    - Cluster service for the IM database (JP1/IM2 - Manager DB Cluster Service_logical-host-name)

  • In UNIX, the JP1/IM-Manager service must be stopped. Note, however, that if the integrated monitoring database and the IM configuration management database are not used, it is not necessary to stop the JP1/IM - Manager service.

• If the command is stopped during execution by pressing the Ctrl and C keys or the Ctrl and Break keys, re-execute the command after making sure that the pdeinstall process is not being executed.

• After executing the jimdbupdate command, you will not be able to recover the expansion backup from the previous execution of the jimdbupdate command. We recommend that you make another expansion backup after executing the jimdbupdate command.

• After executing the command, do not attempt to recover backup data from the existing IM database that was acquired before this command was executed. We recommend that you use the jimdbbackup command to make another backup after executing this command.

• During execution of the jimdbupdate command, do not execute jimdbstatus or other commands related to the IM database. If you do, you might not be able to uninstall the IM database.

• Before executing the command in Windows, in case of existing the Application Experience service, make sure that the startup type of the Application Experience service is not set to Disabled.

To Page Top