Errors in file /u01/app/oracle/diag/diag/rdbms/ebsprod/EBSPROD/trace/EBSPROD_m001_804.trc:
ORA-12751: cpu time or run time policy violation
Tue Aug 23 21:32:42 2016
Errors in file /u01/app/oracle/diag/diag/rdbms/ebsprod/EBSPROD/trace/EBSPROD_ora_501.trc (incident=250203):
ORA-00494: enqueue [CF] held for too long (more than 900 seconds) by 'inst 1, osid 5938'
Incident details in: /u01/app/oracle/diag/diag/rdbms/ebsprod/EBSPROD/incident/incdir_250203/EBSPROD_ora_501_i250203.trc
Killing enqueue blocker (pid=5938) on resource CF-00000000-00000000 by (pid=501)
by killing session 1202.1
Killing enqueue blocker (pid=5938) on resource CF-00000000-00000000 by (pid=501)
by terminating the process
USER (ospid: 501): terminating the instance due to error 2103
Tue Aug 23 21:32:49 2016
System state dump requested by (instance=1, osid=501), summary=[abnormal instance termination].
System State dumped to trace file /u01/app/oracle/diag/diag/rdbms/ebsprod/EBSPROD/trace/EBSPROD_diag_5926_20160823213249.trc
Tue Aug 23 21:32:54 2016
Instance terminated by USER, pid = 501

Solution 1: This is a case of CPU exhaustion where the runqueue exceeds the number of CPU's on the server.
The solution to this problem is to reduce CPU consumption by either tuning SQL statements, or by adding additional CPU's to the server. If this error persists, contact Oracle Support Services.

You can also look for Oracle metalink:
Troubleshooting ORA-12751 "cpu time or run time policy violation" Errors (Doc ID 761298.1)
OERR: ORA-12751 "cpu time or run time policy violation" Reference Note (Doc ID 2008171.1)