ORA-12751: Cpu Time Or Run Time Policy Violation
(Doc ID 2712862.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterInformation in this document applies to any platform.
Symptoms
- ORA-12751: cpu time or run time policy violation:
----- Current SQL Statement for this session (sql_id=a1xgxtssv5rrp) -----
select sum(used_blocks), ts.ts# from GV$SORT_SEGMENT gv, ts$ ts where gv.tablespace_name = ts.name and ts.bitmapped <> 0 group by ts.ts#
.
----- START DDE Action: 'ORA_12751_DUMP' (Sync) -----
Runtime exceeded 540 seconds
Time limit violation detected at:
ksedsts()+346<-kspol_12751_dump()+170<-dbgdaExecuteAction()+354<-dbgerRunAction()+108<-dbgerRunActions()+3719<-dbgexPhaseII()+1688<-dbgexProcessError()+2531<-dbgePostErrorKGE()+1767<-dbkePostKGE_kgsf()+90<-kgeade()+432<-kgeselv()+96<-ksesecl0()+189<-ksucin()+202
<-qerfxFetch()+7478<-rwsfcd()+140<-qerhnFetch()+7688<-qerscFetchBuffer()+1288<-qerscFetch()+218<-qerjotFetch()+566<-qerjotFetch()+566<-rwsfcd()+140<-qerhnFetch()+446<-qergsFetch()+892<-opifch2()+3267<-kpoal8()+3490<-opiodr()+1229<-kpoodrc()+42<-rpiswu2()+627
<-kpoodr()+656<-upirtrc()+2390<-kpurcsc()+102<-kpuexec()+11351<-OCIStmtExecute()+41<-ktte_monitor_tsth_main()+1711<-ktte_monitor_tsth()+38<-ktte_threshold_slave()+238<-kebm_slave_cb()+64<-kebm_slave_main()+775<-ksvrdp_int()+2010<-opirip()+602<-opidrv()+602
<-sou2o()+145<-opimai_real()+202<-ssthrdmain()+417<-main()+262<-__libc_start_main()+256Current Wait Stack:
Not in wait; last wait ended 3.031582 sec ago
Wait State:
fixed_waits=0 flags=0x21 boundary=(nil)/-1
Session Wait History:
elapsed time of 3.031614 sec since last wait
0: waited for 'PGA memory operation'<<<
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |