Home > Documentation   Administrator guide   Repairing databases and workspaces During the course of normal operation errors can occur such as communications failures and hardware breakdown.  CodeMatrix software must respond to such conditions by returning the managed data to a consistent state. However if the error is sufficiently serious the recovery process itself might fail. In this situation CodeMatrix will take the affected data offline in order to ensure the continued integrity of the data. Under these circumstances  any subsequent requests to access the affected area will receive one of the following messages, indicating a server side or client side problem respectively; A repository affected by the request is offline pending a repair A workspace affected by the request is offline pending a repair This indicates that one or more transactions need to be completed or rolled back. It does not mean there is physical or logical database corruption. The repair function allows the user to initiate the transaction completion. If the problem is of a short term nature simply running repair should be all that is needed. If both repository and workspace are in this state you will need to run repair twice. If the repair function fails a report of what the server tried to do is given. This should point to the problem area. Correct the problem and try again. If the problem solution is not apparent, or appears to indicate that database or workspace files should be changed in anyway contact CodeMatrix support giving details of the failure message.