IBM FileNet P8, Version 5.2.1            

Deadlock errors on SQL Server

Deadlock errors result with high concurrency on SQL Server.

Symptoms

Database operations fail because of transaction deadlock errors.

Causes

High concurrency blocks readers' access to database resources by writers, resulting in deadlocks.

Resolving the problem

READ_COMMITTED_SNAPSHOT is required on SQL Server to reduce deadlocks.

To enable Read-Committed Snapshot Isolation on SQL Server:
  1. Shut down all of the servers and clients, and make sure there are no other connections to SQL Server.
  2. Connect to SQL Server and issue the following command:
    ALTER DATABASE dbName SET READ_COMMITTED_SNAPSHOT ON
  3. Restart SQL Server and verify that the Read-Committed Snapshot Isolation setting takes effect for new connections.


Last updated: March 2016
p8pct039.htm

© Copyright IBM Corporation 2016.