My Oracle Support Banner

D1-IMDCL Threads Throw An IO Socket Error And Times Out (Doc ID 2568917.1)

Last updated on AUGUST 02, 2019

Applies to:

Oracle Utilities Meter Data Management - Version and later
Information in this document applies to any platform.


On : version, Undetermined

D1-IMDCL threads throw an IO Socket Error and times out

When running the D1-IMDCL ILM batch job to perform ILM lifecycle management on our D1_INIT_MSRMT_DATA table, due to the number of partitions / data volume that exist prior to the ILM Retention cutoff, experiencing an increasing volume of timeouts.

Is there a way to specify not only a ILM Retention "Cutoff" date, but also give it a boundary date that the query doesn't go past?

For example, ILM Retention date is currently 950 days which is currently mid-January 2017. Have data in the table all the way back to May 2015. As a result, when the D1-IMDCL crawler runs, it has to select all the data from May 2015 to Jan 2017 to process.
Is there a way to force it to only query Jan 2017 back XX # of days - i.e. 180 days back to July 2016?

NOTE: Once you start dropping the old partitions that have been already processed by the crawler, this problem will go away. However, currently don't have a timeline on when will be doing that, so looking for the next best choice.


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

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