ITADM111E Database Deadlock detected for user (null) (Deadlock found when trying to get lock; try restarting transaction

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

ITADM111E Database Deadlock detected for user (null) (Deadlock found when trying to get lock; try restarting transaction

L7 Applicator

Has anyone seen below error?

 

This happened when trying to reconcile a domain account. I could not reproduce the same error again. Checked vaultdb logs and ITAlog and cannot seem to find the root cause.

ImmediateTask. Failure Description: CACPM124E Error modifying Password Object (error: ITADM111E Database Deadlock detected for user (null) (Deadlock found when trying to get lock; try restarting transaction) )

 

Any taught ?

16 REPLIES 16

L7 Applicator

Hey @vinay vasanth​ 

What version did you see this occur on?

 

A deadlock is generally when a transaction is attempted and cannot be completed for some reason. I've seen a few related bugs with similar errors on older versions.

 

-Matt

@Matt Jennison​ This occurred on 10.4

@vinay vasanth​ 

doesn't sound like the bug I'm thinking, then. Could have just been a random deadlock. Have you seen it since?

 

-Matt

@Matt Jennison​ I am not seeing this error again . Probably you are right might be a random deadlock.

What could be the reason for this based on your experience?

@vinay vasanth​ 

The usual explanation I get is along the lines of 'The Vault is still a database, and these things happen when working within a database'. So your guess is as good as mine, really.

 

-Matt

Thanks @Matt Jennison​ 

A good thing to note is whether it affected something. There are different reasons for a deadlock but as long as the system is running OK and it didn't reoccur everything is good 🙂

A good thing to note is whether it affected something. There are different reasons for a deadlock but as long as the system is running OK and it didn't reoccur everything is good 🙂

L1 Bithead

Hi @vinay vasanth​  @Matt Jennison​ how to resolve the Error message. One of my client is using 9.8 version and they are facing this issues. Kindly assist if you have any workaround to resolve this deadlock error.

hey @Hemanth Kumar Rachamadugu​ 

Is the error causing any problems for the customer?

When do they plan to upgrade to a supported version?

 

-Matt

@Matt Jennison​  They were planning to migrate from 9.8 to 11.3. They built a new 2016 server and installed 9.8 vault. Once the configurations were working properly they will take the data backup to the new vault and upgrade the environment.

 

thanks @Hemanth Kumar Rachamadugu​ 

Are they seeing a problem? or just the error?

 

It's possible they can just ignore this if it's not causing an actual issue.

 

-Matt

L2 Linker

O faced same error on my vault which is on 12.1 it stop the vault and move it to DR mode​

hey @Amit Gautam​ 

Can you advise on what activities may have been on-going with your Vault that might have caused this?

 

Generally a deadlock is because a task could not be completed. Did this only occur once? Or is it on-going?

 

-Matt

  • 3888 Views
  • 16 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!