manage restart

Restart the specified components and any dependencies. The component will be restarted after the dependencies are restarted.

Extended description

The components are restarted after the dependencies are restarted. When you restart a service, any instances that were forcibly shut down are automatically restarted.

Syntax

cpd-cli manage restart \
--components=<comma-separated-list-of-component-names> \
--cpd_instance_ns=<project-name> \
[--tethered_instance_ns=${PROJECT_CPD_INSTANCE}]

Arguments

The restart command has no arguments.

Options

Option Description
--components The components to restart. If the component has any dependencies, they will also be restarted.
Status
Required.
Syntax
--components=<comma-separated-list-of-component-names>
Default value
No default.
Valid values
For the list of components, see Component IDs.
--cpd_instance_ns The project (namespace) where the component is installed.
Status
Required.
Syntax
--cpd_instance_ns=<project-name>
Default value
No default. User-defined.
Valid values
The project (namespace) where the component is installed.
--tethered_instance_ns A tethered project (namespace) where the restart command will restart installed service instances.
Status
Optional.
Syntax
--tethered_instance_ns=${PROJECT_CPD_INSTANCE}
Default value
No default. User-defined.
Valid values
When the service allows tethered namespaces, a tethered Cloud Pak for Data namespace.
-v
-vv
-vvv
Display verbose output.

Options are listed from least verbose to the most verbose.

Status
Optional.
Syntax
Verbose output
-v
Very verbose output
-vv
Most verbose output
-vvv
Default value
Not applicable.
Valid values
Not applicable.

Examples

The following example restarts the Db2® service.

cpd-cli manage restart \
--components=db2oltp \
--cpd_instance_ns=${PROJECT_CPD_INSTANCE}