14.3.14 deletecache (deletes a cache)
- Organization of this subsection
(1) Description
This subcommand deletes a cache.
When executed, this subcommand deletes a specified cache and the data contained in it.
(2) Rules
-
You can execute this subcommand when the cluster's status is 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
-
Closed
-
-
To prevent a full garbage collection (FullGC) from occurring while operations are underway, each EADS server performs FullGC when this subcommand terminates.
-
While this subcommand has obtained a lock from the EADS server, the EADS server is not isolated. However, if a process is shut down or the EADS server terminates while the subcommand has the lock, the lock is released, and then the EADS server is isolated.
(3) Format
eztool deletecache cache-name [--with_deleteecf]
(4) Options and arguments
(a) cache-name
Specify the name of cache you want to delete.
The following characters are permitted for a cache name:
-
If cache property files were not used to create caches
A maximum of 32 single-byte characters in ASCII codes 0x20 to 0x7E
-
If cache property files were used to create caches
A maximum of 32 single-byte alphanumeric characters (0 to 9, A to Z, and a to z)
(b) --with_deleteecf
If you are deleting a disk cache or two-way cache, specify this option to also delete the cache files.
(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. |