A cloud object has an expected status and a current status. The expected status reflects the state the object is expected to be in, and the current status reflects the state that the object is actually in.
If the current status and the expected status do not match, then the object is in an undesirable state. For example, if the expected status of the object is run, but its current status is starting, then the object is not in its expected state, and it must be diagnosed and repaired.
Generally, an object's current status shows either running, stopped, or disconnected. Diagnosing a cloud object by running the relevant diagnose task provides a more specific status. For example, diagnosing an object that has the current status disconnected may show a status of failed if the object is not running.
If an object is in an undesirable state when it is being started or stopped, it is automatically repaired. However, you can repair cloud objects manually by running the relevant repair task.
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 object cannot be repaired to a desirable state, and cannot be dropped from the cloud, you have the option of forgetting the object. Forgetting a cloud object does not delete its corresponding files but removes the metadata from the object and makes the object inaccessible from the cloud.
Forgetting a cloud object should only be done if the object cannot be repaired or dropped from the cloud. Whenever possible, use the Delete button in the Console to remove the object from the cloud.
Discuss this page in DocCommentXchange.
|Copyright © 2013, SAP AG or an SAP affiliate company - SAP Sybase SQL Anywhere, on-demand edition 1.0 Support Package 3|