Absent Member.. Pamela Harrod Absent Member..
Absent Member..
173 views

(OO) Support Tip: Database deadlock

Encountering persistent database issue:
Transaction (Process ID XX) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

How to resolve?

In the OO 10.20 Database Guide, page 14, the following eight mandatory configuration options/values are indicated for Microsoft SQL Server 2008R2 and 2012:
- Network Libraries
- Concurrent Connections
- Max Server Memory
- Collation
- Allow Snapshot Isolation
- Is Read Committed Snapshot On
- Auto Shrink
- Auto Create Statistics

Ensure that the DBA alter the DB to set it up for OO 10 as out of the following required parameters, only two are correct by default:
ALTER DATABASE [DBNAME] SET ALLOW_SNAPSHOT_ISOLATION ON
ALTER DATABASE [DBNAME] SET READ_COMMITTED_SNAPSHOT ON
ALTER DATABASE [DBNAME] SET AUTO_CREATE_STATISTICS ON
ALTER DATABASE [DBNAME] SET AUTO_SHRINK OFF
ALTER DATABASE [DBNAME] COLLATE SQL_Latin1_General_CP1_CS_AS

SQL query to validate the status of each value:
SELECT name
, s.snapshot_isolation_state
, snapshot_isolation_state_desc
, is_read_committed_snapshot_on
FROM sys.databases s

Please see the knowledgebase document at http://support.openview.hp.com/selfsolve/document/KM01849237

Labels (2)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.