If your ATG Content Administration environment uses an MS SQL Server database that employs clustered primary keys for repository tables, locking errors might occur when you initialize your targets:

Warning /atg/deployment/DeploymentManager Transaction (Process ID 164) was
deadlocked on lock resources with another process and has been chosen as
the deadlock victim. Rerun the transaction.

These errors can occur if READ_COMMITTED_SNAPSHOT is not enabled for the database, as described in the Platform Installation and Configuration Guide. Check all recommended settings.

If deadlock persists, reduce the number of threads by setting the following property values in the /atg/deployment/DeploymentManager component:

phaseCompletePollingInterval=30000
maxThreads=5
transactionBatchSize=5

If the errors still occur, try the following settings:

phaseCompletePollingInterval=60000
maxThreads=1
transactionBatchSize=1

Reducing the number of threads can adversely affect performance. If this occurs, contact Oracle Support for further help.