You are viewing limited content. For full access, please sign in.

Question

Question

Numerous "ORA-00060: Deadlock detected" errors occurring on database server. Related to 9.1 upgrade?

Version 9 Laserfiche
Updated February 10, 2014
asked on February 5, 2014 • Show version history

Recently upgraded Laserfiche server to 9.1 and had run into several Oracle errors which sounds like they will be addressed in an upcoming release (9.1.1).  However it has recently been discovered that an error message "ORA-00060: Deadlock detected" has been occuring on the database server, with the following message pulled from a trace file:

 

*****

MODULE NAME:(lfs.exe)

 

[Transaction Deadlock]
 
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL.

 

user: 80/ED_HR_DBA  <this is the repository schema>

 

----- Information for the OTHER waiting sessions -----
O/S info: user: ADMIN\ITS-EDM-service, term: EC-EDM-LASER
machine: ADMIN\EC-EDM-LASER program: lfs.exe
   

application name: lfs.exe

 

current SQL:
update toc set toc_flags = bitand(bitor(toc_flags, 1), bitnot(8192)) where tocid = :tocid1

Information for THIS session:


 ----- Current SQL Statement for this session (sql_id=08w3a5zbpsagf) -----

UPDATE TOC SET ACL_TOCID = :B2 WHERE TOCID = :B1 OR TOCID IN ( SELECT TOCID FROM TOC START WITH TOCID = :B1 CONNECT BY PARENTID = PRIOR TOCID AND (ACL_TOCID IS NULL OR ACL_TOCID <> TOCID))

 

----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
0000000435C82208        27  procedure ED_HR_DBA.SET_ACL_TOCID

Current Wait Stack:
     0: waiting for 'enq: TX - row lock contention'

 

**********

 

The second update command (in bold above) is related to version 9.1 functionality as it is updating the new ACL_TOCID column.

 

I'm not an expert in Oracle, but for those of you in the community who are, what is this error referring to?  Users have been complaining of oddities occurring after the upgrade (searches not returning properly, general slowness, SQL command errors) and wondering if the above error has anything to do with the symptoms?

 

Thanks for any input.

0 0

Answer

APPROVED ANSWER
replied on February 10, 2014

Travis, you have submitted a case with technical support , the case was submitted on 2/10/2014. We are currently in the process of investigating the issue, we would appreciate if in the case note ,you submit as much information as you did in this post. The deadlock might be related to resources being busy , in this case another session updating or deleting data from tables. Case is in the process to get updated with the files we need to start the troubleshooting issue. I will update the case first, with the important notes you have posted in this forum. Important: With the above information I believe we have a better idea on what it is happening. Information will be posted in your case.

2 0

Replies

replied on February 5, 2014 • Show version history

This KB Article does not specifically mention this problem, but have you applied it to your Oracle database?

 

The TOC ID your error references is the ROOT FOLDER and not the recycle bin, so I don't know if the above KB Article will fix your problem or not.

1 0
replied on February 5, 2014

Yes, actually that hotfix came as a result of the support case created when we first upgraded to 9.1.0.

0 0
replied on February 5, 2014

The deadlock error as it appears in the application log on the Laserfiche server, if it helps any:

 

********

Database statement execution error encountered.  Session ID: 16; Dialog ID: 338044; Repository: 'HRS'; CLI routine: SysIndexSetFlagBatch; Message: ORA-00060: deadlock detected while waiting for resource
; SQL Statement: 'update toc set toc_flags = bitand(bitor(toc_flags, 1), bitnot(8192)) where tocid = :tocid<int>'; SQL variable: ''; SQL State: .

 

*********

The error points to the CLI routine "SysIndexSetFlagBatch", so hopefully this helps direct some focus on the primary cause.

0 0
replied on February 7, 2014

Hey Travis,

 

I'm not familiar with this error message, so I did some digging around.  All the references I could find to this problem are for version 8.0, and were resolved years ago.  We are not aware of any problems with 9.1.  If this issue continues to pop up, I'd recommend opening a Support case.

0 0
replied on February 7, 2014

Thanks Brett, do you happen to have a link to a white paper or any other material that describes the resolution that was made back in 8.0?  I wasn't able to find a reference of this error on the support site.  Perhaps it will apply to what we're experiencing now.

0 0
APPROVED ANSWER
replied on February 10, 2014

Travis, you have submitted a case with technical support , the case was submitted on 2/10/2014. We are currently in the process of investigating the issue, we would appreciate if in the case note ,you submit as much information as you did in this post. The deadlock might be related to resources being busy , in this case another session updating or deleting data from tables. Case is in the process to get updated with the files we need to start the troubleshooting issue. I will update the case first, with the important notes you have posted in this forum. Important: With the above information I believe we have a better idea on what it is happening. Information will be posted in your case.

2 0
replied on February 10, 2014

Thank you Shule.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...