I'm not sure. I couldn't reproduce that behavior with a long-running inter-db copy operation (although the copy operation is likely continuing, and it's probably not a good idea to try to do anything in the database during the copy operation anyway). What triggered it?
|