DR database goes into Loading state

Symptom

SOLUTION:
?Solution Recommended to Customer : The underlying root cause of the IO performance degradation has to be identified and fixed by the customer

?There disks where the DB's files are located seems to be overloaded causing IO requests to take longer time. This is causing the loading of the logs to slowdown which gives an impression that the DB is left in loading state

?In the worst case scenario, due to this performance degradation, SQL server fails in loading of the logs and leaves the DB in loading state.

?The underlying root cause of the IO performance degradation has to be identified and fixed by the customer and until then this problem will continue to happen and Panaces does not have any control over this.

?Hint:
?Customer can look at this above mentioned two time period and investigate whether any bulk operations or any other IO intensive operations were going on during this time period.

?Searching for the error message in the web gives a lot of information about how to identify and fix the IO requests problem

?DR database goes to loading/restoring state. Increase in time intervals of transaction log dump/apply may help to resolve this.