There is an overnight auto-purge job failure every day by throwing “ORA-12751: cpu time or run time policy violation” error.
Extracted trace file from slave process ( m001 ) of Manageability Monitor Process ( MMON) :
*** 2017-02-01 01:11:39.393 *** SESSION ID:(9.3069) 2017-02-01 01:11:39.393 *** CLIENT ID:() 2017-02-01 01:11:39.393 *** SERVICE NAME:(SYS$BACKGROUND) 2017-02-01 01:11:39.393 *** MODULE NAME:(MMON_SLAVE) 2017-02-01 01:11:39.393 *** ACTION NAME:(Auto-Purge Slave Action) 2017-02-01 01:11:39.393 ... .. ----- START DDE Action: 'ORA_12751_DUMP' (Sync) ----- CPU time exceeded 300 seconds Time limit violation detected at: ksedsts()+465<-kspol_12751_dump()+145<-dbgdaExecuteAction()+1065<-dbgerRunAction()+109<-dbgerRunActions()+4134<-dbgexPhaseII()+1873<-dbgexProcessError()+2680<-dbgeExecuteForError()+88<-dbgePostErrorKGE()+2136<-dbkePostKGE_kgsf()+71<-kgeselv()+276<-ksesecl0()+162 <-ksucin()+147<-delrow()+13790<-qerdlFetch()+1822<-delexe()+1001<-opiexe()+10315<-kpoal8()+2380<-opiodr()+917<-kpoodrc()+36<-rpiswu2()+1776<-kpoodr()+636<-upirtrc()+2436<-kpurcsc()+98<-kpuexec()+10790<-OCIStmtExecute()+39<-kewrose_oci_stmt_exec()+55<-kewrgwxf1_gwrsql_exft_1()+317 <-kewrgwxf_gwrsql_exft()+496<-kewrdsr1_delete_snaprange_1()+476<-kewrdsr_delete_snapshot_range()+133<-kewrpanp_purge_all_nonpts()+923<-kewrpdc_periodic_cleanup()+41<-kewrsnrm_snapshot_removal()+169<-kewrpsr_purge_snapshot_range()+116<-kewrapad_auto_purge_all_dbids()+682 <-kewraps_auto_purge_slave()+942<-kebm_slave_main()+586<-ksvrdp()+1766<-opirip()+674<-opidrv()+603<-sou2o()+103<-opimai_real()+250<-ssthrdmain()+265<-main()+201<-__libc_start_main()+253Current Wait Stack: ... .. . *** 2017-02-01 01:15:05.083 *** KEWROCISTMTEXEC - encountered error: (ORA-12751: cpu time or run time policy violation ) *** SQLSTR: total-len=351, dump-len=240, STR={delete from WRH$_SYSMETRIC_HISTORY tab where (:beg_snap <= tab.snap_id and tab.snap_id <= :end_snap and dbid = :dbid) and not exists (select 1 from WRM$_BASELINE b where (tab.dbid = b.dbid) and }
We can see there is a 300 seconds ( 5 minutes ) CPU time limitation resource violation.
Subscribe to get access
Read more of this content when you subscribe today.