The database server detected a deadlock situation and rolled back the outstanding work on this statement handle. When server processes encounter a database deadlock, they usually reattempt the work that was in progress when the deadlock was encountered. Not all processes can explicitly try an operation again. For example, migration and reclamation will eventually be tried again. However, something such as 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.
The work being done on the statement handle is rolled back. Some processes will attempt to retry the request. Others will just stop. Server operation continues.
If a process can retry (like migration), then monitor the re-try attempt to see if it succeeds or not. If the process or command is not able to retry on it's own, then reissue the command or macro that caused the action to occur.