We know how to flash all shared pool by :
SQL>alter system flush shared_pool;
Sometime, we only want to flush certain objects, like a cursor for testing purpose to want the cursor to have different execution plan.
Read more of this content when you subscribe today.
Duplicate test RAC database from prod RAC database using overnight tape RMAN backups.
This post demonstrates how to refresh RAC TEST database from source RAC PROD database without connecting to source RAC PROD database by using overnight tape backups.
Read more of this content when you subscribe today.
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.
Read more of this content when you subscribe today.
Apply some hidden parameters into emd.properties file, then bounce the agent. It might fix some internal issues.
In OEM 13c, a couple of OEM agents reported some internal errors like :
Internal error detected: oracle.sysman.gcagent.task.TaskZombieException:oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask:620
Internal error detected: oracle.sysman.gcagent.task.TaskZombieException:oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask:621
From: oracle Sent: Monday, 13 February 2017 10:41 AM To: Subject: EM Event: Critical:ractest:3872 - Internal error detected: oracle.sysman.gcagent.task.TaskZombieException:oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask:620. Host=ractest Target type=Agent Target name=ractest:3872 Categories=Diagnostics Message=Internal error detected: oracle.sysman.gcagent.task.TaskZombieException:oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask:620. Severity=Critical ... .. . Update Details: Internal error detected: oracle.sysman.gcagent.task.TaskZombieException:oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask:620.
Extracted from gcagent.log :
2017-02-13 10:10:00,329 [256:7761FFD4] WARN - IntervalSchedule: Skip schedule [rac_database:RACTEST:observer_11g] - skipping due to execution time exceeding interval 2017-02-13 10:10:00,329 [257:B85D2018:GC.Executor.6 (oracle_database:RACTEST:Response)] WARN - IntervalSchedule: Skip schedule [oracle_database:RACTEST:Response] - skipping due to execution time exceeding interval 2017-02-13 10:10:00,329 [258:5A4306F7:GC.Executor.7 (rac_database:RACTEST:observer_11g)] WARN - Action result processing failure rac_database.RACTEST::observer_11g java.lang.InterruptedException at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1302) ... .. . oracle.sysman.gcagent.task.TaskZombieException: task declared as a zombie at oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.accountedCall(TaskFutureImpl.java:620) at oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.call(TaskFutureImpl.java:643) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at oracle.sysman.gcagent.task.TaskFutureImpl.run1(TaskFutureImpl.java:380) ... .. . at java.lang.Thread.run(Thread.java:662) 2017-02-13 10:10:00,331 [257:GC.Executor.6] ERROR - Critical error: oracle.sysman.gcagent.task.TaskZombieException: task declared as a zombie at oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.accountedCall(TaskFutureImpl.java:620) at oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.call(TaskFutureImpl.java:643)
Read more of this content when you subscribe today.
This error is caused by crsd not running, while both cssd and evmd processes are running. Also all the database instances are running.
Environment is 12.1.0.2 GI and 11.2.0.4 databases.
$ crsctl check crs
CRS-4638: Oracle High Availability Services is online
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
$ps -eaf|grep crsd No process found
Try to start up CRS:
# crsctl start crs CRS-4640: Oracle High Availability Services is already active CRS-4000: Command Start failed, or completed with errors.
Read more of this content when you subscribe today.
Make DBA Life Easy 