Diagnose and repair cloud objects that are in an undesirable state.
You must have the following privileges:
To diagnose an object, you must have the corresponding StartStop privilege
To repair an object, you must have the Administrator privilege
To repair a tenant database, the cloud server it is located on must be running. To repair a cloud server, the host it is located on must be running.
If there are numerous cloud objects being created, started, or repaired, repairing a cloud object can take a significant amount of time.
If you are repairing a cloud server that has numerous tenant databases running on it, restarting all the databases may take a significant amount of time.
If the parent object is not running properly, repairing an object fails. For example, attempting to repair a database fails if the database is on a cloud server that is not running.
The status of the object is updated to show the results of the diagnosis on the Overview panel of the object.
The cloud object is repaired to its desired state.
If the object could not be repaired to its desired state, but the object it is running on is in a good state, you can either delete the object, or, if the object cannot be deleted, you can forget the object. If the object is a tenant database, try restoring the database from a backup first. Forgetting a cloud object removes the object's metadata and makes it inaccessible in the cloud, but does not affect the object's system resources.