The server detected a deadlock situation between a number of processes attempting to access database information. A lock request for one of the processes will be denied to resolve the database deadlock. When the server processes encounter a database deadlock, they usually try to run the function that was in progress when the deadlock was encountered again. Not all process can explicitly try an operation again. For example, migration and reclamation will eventually try again. However, something like a delete volume run in a macro will only be tried again if the delete command is reissued either in the macro or the command line.
A lock request fails for one of the deadlocked processes. Server operation continues.
If a process can be retried (like migration), monitor the retry effort to see if it succeeds. If the process or command cannot be retried, reissue the command or macro that caused the action.
Consider what other processes are running at the time the deadlock is reported. For example, if a process is started manually, as opposed to running as part of your regularly scheduled server maintenance tasks, that process may have caused the deadlock. You might have to adjust the scheduling of your server maintenance tasks to avoid the problem.