14.3.17 deleteesd (deletes store data files)
- Organization of this subsection
(1) Description
This subcommand deletes specified store data files from the cluster.
(2) Rules
-
This subcommand can be executed only when the status of the cluster is one of the following:
-
Cluster available (AVAILABLE)
-
Cluster partially available (PARTIALLY_AVAILABLE)
-
-
The target of this subcommand is the EADS servers whose cluster participation status is online. This subcommand cannot be executed if the cluster contains any EADS server whose cluster participation status is standby. You can determine the cluster participation status with the eztool status command.
-
This subcommand can be executed when the target EADS servers are in the following status:
-
Initialized
-
Running
-
Closed
-
(3) Format
eztool deleteesd [-d path-name-of-store-data-file-storage-location]
store-data-file-key
(4) Options and arguments
(a) -d path-name-of-store-data-file-storage-location or --directory path-name-of-store-data-file-storage-location
This option specifies the path name of the store data file storage location.
Specify this option to delete only the store data files located in the specified directory.
The path name cannot be a directory that contains an asterisk (*), double quotation mark ("), question mark (?), vertical bar (|), less-than sign (<), or greater-than sign (>).
If you specify a relative path for the path name of the store data file storage location, the path is relative to the management directory of each EADS server.
(b) store-data-file-key
This option specifies the store data file key of the store data file (or files) to be deleted from the cluster.
Specify the store data file key of a store data file that was output by the eztool export or eztool stop command.
A store data file key is expressed as a maximum of 32 single-byte characters. The permitted characters are alphanumeric characters (0 to 9, A to Z, and a to z), underscores (_), and hyphens (-).
(5) Return code
The following table lists the return codes that this subcommand returns.
|
No. |
Return code |
Description |
|
|---|---|---|---|
|
eads.command.compat parameter omitted in the command properties |
0300 specified in the eads.command.compat parameter in the command properties |
||
|
1 |
0 |
0 |
Command execution was successful. |
|
2 |
101 |
101 |
Initialization of the command failed. |
|
3 |
110 |
Connection establishment failed. |
|
|
4 |
111 |
The command failed due to a communication timeout. |
|
|
5 |
120 |
The command failed due to a syntax error. |
|
|
6 |
130 |
The command failed because it could not be executed. |
|
|
7 |
131 |
The command failed because another command was executing. |
|
|
8 |
150 |
The command failed during execution. |
|
|
9 |
200 |
The command failed due to a timeout. |
|
(6) Notes
All store data files with the specified store data file key are deleted.
For example, if this subcommand is executed with 20111101130203 specified as the store data file key, the subcommand deletes all files named eads_20111101130203_[EADS-server-ID].esd from each EADS server.