My Oracle Support Banner

PURGE_HISTORY_TABLES_JOB Causing CORBA Timeouts (Doc ID 2562242.1)

Last updated on AUGUST 02, 2019

Applies to:

Oracle Utilities Network Management System - Version and later
Oracle Network Management for Utilities - DMS - Version and later
Information in this document applies to any platform.



Roughly 75 million rows are being generated daily in the SCADA_ANALOG_HISTORY table.

When the table is purged weekly via 'PURGE_HISTORY_TABLES_JOB' (Action any.DDService purge_history), an estimated 525 million rows are deleted.

When looking at the corbagateway logs during the time of execution, long execution times on most operations are observed.
06/16/19 00:18:33: corbagateway InterSysImpl::getPartitions" wall=528.264657
06/16/19 00:18:33: corbagateway InterSysImpl::getMeasures" wall=1082.455779
06/16/19 00:18:33: corbagateway InterSysImpl::getMeasures" wall=902.438369
06/16/19 00:18:33: corbagateway InterSysImpl::getDeviceInfo"wall=888.355688

The symptoms last for about ~18 minutes.

In an attempt to clear the data in smaller chunks, we scheduled the purge to run nightly. There is still a ~1-3 minute impact however.

During that time, user sessions lock with corba timeouts showing as a symptom in the Weblogic logs.
Sunday 02 Jun 2019 00:10:11 - org.omg.CORBA.TIMEOUT: Response timed out after: '180000' milliseconds.
Sunday 09 Jun 2019 00:08:18 - org.omg.CORBA.TIMEOUT: Response timed out after: '180000' milliseconds.
Sunday 16 Jun 2019 00:12:31 - org.omg.CORBA.TIMEOUT: Response timed out after: '180000' milliseconds.


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
 Fix Description

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.