My Oracle Support Banner

OAAM Cannot Connect To MS SQL Database using JNDI (Doc ID 1207535.1)

Last updated on JANUARY 24, 2019

Applies to:

Oracle Adaptive Access Manager - Version 10.1.4.5 and later
Information in this document applies to any platform.

Symptoms

When starting the OAAM application, an error message is shown indicating OAAM connect using JNDI to the MSSQL database.  OAAM log file shows the following exception:


Internal Exception: java.sql.SQLException: [IBM][SQLServer JDBC Driver][SQLServer]Transaction (Process ID 62) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.Error Code: 1205

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.