[ZBX-14686]  ORA-00060: deadlock detected while waiting for resource Created: 2018 Aug 03  Updated: 2018 Dec 05  Resolved: 2018 Dec 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: clayton roberto da silva Assignee: Zabbix Support Team
Resolution: Unsupported version Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Microsoft Word query.xlsx    

 Description   

I'm with this error below.

syddba said that this error, it is bursting filesystem /oracle.

is there any configuration that can be done?

I do not know if these errors were caused by a massive update

sorry for my English.

20011:20180803:142410.675 [Z3005] query failed: [-1] ORA-00060: deadlock detected while waiting for resource [select null from hosts where hostid=10812 for update]

20011:20180803:142410.676 slow query: 22.848106 sec, "select null from hosts where hostid=10812 for update"

20016:20180803:142410.903 [Z3005] query failed: [-1] ORA-00060: deadlock detected while waiting for resource [select null from hosts where hostid=10822 for update]

20016:20180803:142410.903 slow query: 6.856941 sec, "select null from hosts where hostid=10822 for update"

19979:20180803:142410.948 [Z3005] query failed: [-1] ORA-00060: deadlock detected while waiting for resource [update ids set nextid=nextid+1 where table_name='items' and field_name='itemid']
 
[oracle@MZ-CL-BD-071:/oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace [CDBBRA] $ df -hP /oracle

Filesystem                       Size  Used Avail Use% Mounted on

/dev/mapper/oracle_vg-oracle_lv   99G   40G   55G  43% /oracle

 

alert.log

ZBCORP(4):ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file /oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace/CDBBRA_ora_25740.trc.

ZBCORP(4):ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file /oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace/CDBBRA_ora_25926.trc.

ZBCORP(4):ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file /oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace/CDBBRA_ora_25780.trc.

ZBCORP(4):ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file /oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace/CDBBRA_ora_25792.trc.

ZBCORP(4):ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file /oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace/CDBBRA_ora_25682.trc.

ZBCORP(4):ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file /oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace/CDBBRA_ora_25796.trc.

ZBCORP(4):ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file /oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace/CDBBRA_ora_25922.trc.

ZBCORP(4):ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file /oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace/CDBBRA_ora_25624.trc.

ZBCORP(4):ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file /oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace/CDBBRA_ora_25776.trc.

ZBCORP(4):ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file /oracle/app/oracle/diag/rdbms/cdbbra/CDBBRA/trace/CDBBRA_ora_25948.trc.

 

deadlock:

DEADLOCK DETECTED ( ORA-00060 )

See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors

[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. The following

information may aid in determining the deadlock:

  

Deadlock graph:

                                          -----------Blocker(s)---------  ------------Waiter(s)-----------

Resource Name                             process session holds waits serial  process session holds waits serial

TM-000059BE-00000000-2F87D304-00000000        342     597    SX        34886     584     806    SX   SSX   6707

TX-00300001-00004B70-2F87D304-00000000        584     806     X         6707     342     597           X  34886

 
2018-08-03T08:22:37.193245-03:00 (ZBCORP(4))
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=1, mask=0x0)

----- Error Stack Dump -----

Current SQL Statement for this session (sql_id=akmjxxu866qa5) -----*
select null from hosts where hostid=10672 for update

 



 Comments   
Comment by Glebs Ivanovskis [ 2018 Aug 06 ]

What is the version of Zabbix server you are using?

What can you tell about hosts with hostid's 10812 and 10822? Are they involved in network discovery or low-level discovery?

Comment by Alexey Pustovalov [ 2018 Aug 06 ]

Please execute the following SQL queries:

select * from hosts where hostid in (10812, 10822, 10672);
Comment by clayton roberto da silva [ 2018 Aug 07 ]

What is the version of Zabbix server you are using?

3.4.11

What can you tell about hosts with hostid's 10812 and 10822? Are they involved in network discovery or low-level discovery?

LLD, I'm deleting and clearing a template from a group of hosts and including another template, both with prototype items.

I'm monitoring routers.

the zabbix server and frontend are on a server, oracle in other server.

i just use the template Template Module Interfaces SNMPv2 and one item icmp ping.

 

Zabbix is running Sim localhost:10051
Number of hosts (enabled / disabled / templates) 802 678 / 0 / 124
Number of items (enabled / disabled / not supported) 432065 390133 / 153 / 41779
Number of triggers (enabled / disabled [incident / ok]) 195154 195154 / 0 [170 / 194984]
Number of users (online) 24 1
Required server performance, new values per second    

 

Comment by clayton roberto da silva [ 2018 Aug 07 ]

 

dotneft

 
I attached the query to this incident

Comment by Aigars Kadikis [ 2018 Dec 05 ]

Hello Clayton,

Sorry, I must close this issue due to an unsupported version. If you receiving "deadlock detected" on 4.0 please reopen a new ticket.

Kind regards,

Generated at Sun Apr 27 09:39:58 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.