Rollback command
You can use the rollback command-line interface (CLI) to roll back the Registry Services database schema from one version to another.
If you must roll back Registry Services application, use the update CLI command. For example, frs.bat update -type container. Before you run the update CLI, ensure that the EAR file that is deployed in the application server is from the GA version.
For more information, see Update application command.
Command syntax
The rollback CLI syntax varies according to the environment in which it is run:- frs.bat rollback -type db -target v.r.m.f [-properties properties_file]
- ./frs.sh rollback -type db -target v.r.m.f [-properties properties_file]
Parameters
Table 1 lists the parameters that are used with the rollback CLI and provides their description.
| Parameter | Value | Description |
|---|---|---|
| -type | db | This value defines that the rollback command must roll back the Registry Services database that is deployed into a supported RDBMS from one version to another. |
| -target | v.r.m.f | This value defines the version, release, and modifier, for example, 1.1.0.1, of the target runtime or artifacts that Registry Services leaves after the rollback process completes. |
| [-properties] | properties_file | This value defines that the properties file must act as the source of the rollback properties. This parameter is optional. If you do not specify this parameter, the default REGISTRY_HOME\etc\CLI.properties file is used as the source of updating properties. |
Sample
frs.bat rollback -type db -target 1.1.0.1 -properties C:/etc/db.properties
./frs.sh rollback -type db -target 1.1.1.5
Return codes
The rollback command prints a return code when it finishes running so you can have details about the result achieved. Table 2 provides the return codes that you can get by the end of the rollback run and their respective descriptions.
| Return code | Description |
|---|---|
| 0 | The rollback command ran the operation successfully. |
| 1 | The rollback command failed to run because of a missing -type parameter. |
| 2 | The rollback command failed to run because of a properties file not found. |
| 3 | The rollback command failed to run because of an invalid -type parameter that is specified in the command line. |
| 4 | The rollback command failed to run because of a rollback error. |
98 |
The rollback command failed to run because Registry Services is unable to determine the current operation mode. |
99 |
The rollback command failed to run because the readonly operation mode is active. |