Unregister a DataBlade module
unregister module_name database_name
In the preceding example, module_name represents the name of the DataBlade module directory. These names typically follow the form of the DataBlade module name followed by the version number. If BladeManager is not currently connected to the database specified in the unregister command, it connects to the new database, prepares all available DataBlade modules, and displays a message about the success or failure of the preparation before continuing with the unregister command.
If the unregistration of a module fails, BladeManager returns the database to its prior state. To see the SQL statements that failed, look at the corresponding log file (see View log files) and see Troubleshooting registration problems, for possible solutions.