Null Out Action Type Component In ONT/graph/LoadDataIncr.grf Causes Massive Archive Logs On Database

(Doc ID 2118829.1)

Last updated on APRIL 11, 2016

Applies to:

Oracle Order Management - Version 12.2.4 and later
Information in this document applies to any platform.


On : version, Endeca Integration (v5)

Null out Action Type component in ONT/graph/LoadDataIncr.grf causes massive archive logs on database

We have had an influx of orders in our UAT environment during testing that
has caused the incremental graph for ONT to not finish in a timely manner.
We have attributed this to the NULL_OUT_ACTION_TYPE component in this
graph. It is performing an update on oe_endeca_temp table to set action_type
and hold_name to null.

UPDATE oe_endeca_temp SET action_type = NULL, hold_name = NULL

The screenshot attached will show that the READ_ONLY_HEADER_HOLDS_TO_BE_RELEASED
component has read around 60,000 records. This is about 12 times more than
our normal hourly incremental job has been handling. When it was around 4,000
records per load it was taking around 9 minutes.

We found that this update statement was generating archive logs on the database
at the rate of about 3 GB per minute, which quickly filled up DB disk space. Once
we would kill the graph from Integrator Server or kill the query from the DB, the
archive logging would slow way down, thus preventing the database server from
filling up.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms