jcodbunsetup
- Organization of this page
Function
This command cancels setup of the integrated monitoring database that stores JP1 events.
Execute this command when you stop using the integrated monitoring database, uninstall JP1/IM - Manager, re-create the integrated monitoring database, or expand the database size.
In an environment in which an IM Configuration Management database has been set up, the IM Configuration Management database is still available even after execution of this command.
In Windows, if this command is executed in an environment where the IM Configuration Management database is not set up, the following services are deleted:
-
When removing setup of a physical host: JP1/IM-Manager DB Server, JP1/IM-Manager DB Cluster Service
-
When removing setup of a cluster configuration: JP1/IM-Manager DB Server_logical-host-name, JP1/IM-Manager DB Cluster Service_logical-host-name
In UNIX, if this command is executed in an environment where the IM Configuration Management database is not set up, entries in the /etc/inittab file registered by the jcodbsetup or jcfdbsetup command are deleted. The entries that are deleted are only those for processing related to the physical and logical hosts on which the command was executed.
Format
jcodbunsetup [-h logical-host-name -c {online|standby}] [-q]
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
Storage directory
- In Windows:
-
Console-path\bin\
- In UNIX:
-
/opt/jp1cons/bin/
Arguments
- -h logical-host-name
-
When you are operating in a cluster system, this option specifies the logical host name of the host that executes the command. The command cancels setup of the integrated monitoring database for the specified logical host. If you do not use a cluster system, specification of this option is not needed. Note that this logical host name cannot be JP1_DEFAULT. 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.
- -c {online|standby}
-
Specifies the type of setup being canceled in the cluster configuration (primary node or secondary node). If you have specified the -h option, you must specify this option.
-
online: Specify this value if you specified online during setup of the integrated monitoring database.
-
standby: Specify this value if you specified standby during setup of the integrated monitoring database.
If you specify online, mount the shared disk and establish a connection to the logical host. In addition, if you perform unsetup of the integrated monitoring database on a logical host running in a non-cluster environment, specify online.
-
- -q
-
Specifies that the command is to be executed without requesting confirmation from the user.
Return values
0 |
Normal termination |
1 |
Abnormal termination |
Notes
-
If you expand the database size in an environment in which the IM Configuration Management database has been created, you must execute the command that cancels setup of IM Configuration Management database after you've executed this command.
-
If you execute the command with the -c option specified, do not switch servers during execution. If you switch servers during execution, re-execute the command after the command has terminated.
-
If you have canceled the command's execution by pressing Ctrl + C or Ctrl + Break, make sure that the pdirst process is not executing, and then re-execute this command.
-
In Windows, the service must be in the following status:
- For a physical host:
-
The cluster service for the IM database (JP1/IM3-Manager DB Cluster Service) must be stopped, and the IM database service (JP1/IM3-Manager DB Server) must be started. In addition, if the IM Configuration Management database is set up and the IM database is being used, the JP1/IM - Manager service (JP1/IM3-Manager) must be stopped.
- For a logical host:
-
The cluster service for the IM database (JP1/IM3-Manager DB Cluster Service_logical-host-name) on the logical host must be stopped, and the IM database service (JP1/IM3-Manager DB Server_logical-host-name) on the logical host must be started. In addition, when the IM Configuration Management database is set up and the IM database is being used, the JP1/IM - Manager service (JP1/IM3-Manager_logical-host-name) must be stopped.
-
In UNIX, when the IM Configuration Management database is set up, and the IM database is being used, the JP1/IM-Manager service must be stopped.
-
If you are using JP1/IM - MO, the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source must be stopped.
-
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.