Here is an example of the ORA-60 as you will see it in /home/oracle/wildfly-8.2.0.Final/standalone/log/aveksaServer.log (V7 path) of an ACM installation:
10/17/2016 09:12:16.452 ERROR (Worker_jobq#JobQ1#WPDS_94) [com.aveksa.server.workflow.scripts.nodes.BaseWorkflowNode] Exception :
com.aveksa.server.db.PersistenceException: java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource
ORA-06512: at "AVUSER.ACCESS_REQUEST_PKG", line 212
ORA-06512: at line 1
The ORA-60 usually points to an application design issue, where locking of objects is not fine grained enough..
However, it may also be caused by some other id in the database blocking one ACM session, not allowing it to finish, and thus impeding another session needing the same locks to issue the ORA-60.
The trace files issued by Oracle in /u01/app/oracle/diag/rdbms/avdb/AVDB/trace will tell you the statements that collided, but not if another process had its hand in the incident.
In order to know if there was some sort of hang situation involved to create the ORA-60, you can enable an event in the database that will produce more information to analyze.
This will only produce a trace file if and when when the ORA-60 happens and does not have any other effect on the database.
This setting will disappear when you restart the database.
sqlplus / as sysdba
SQL> alter system set events 'deadlock trace name hanganalyze level 4';
Wed Oct 19 19:07:16 2016
OS Pid: 4527 executed alter system set events 'deadlock trace name hanganalyze level 4'
When it triggers, you would see something similar to this in the alert log:
Wed Oct 19 19:12:11 2016
ORA-00060: Deadlock detected. See Note 60.1 at My Oracle Support for Troubleshooting ORA-60 Errors. More info in file /u01/app/oracle/diag/rdbms/avdb/AVDB/trace/AVDB_ora_4938.trc
RSA Support needs that trace file that is listed in the alert_AVDB.log ( it will have a different name on each customer system).
The hanganalyze will show if there was another condition that led to the ORA-60.