Bug 26726154: INV-LU Graph Uses Massive Amount Of Disk Space For It's Indexes
(Doc ID 2319400.1)
Last updated on OCTOBER 19, 2017
Applies to:Oracle Warehouse Management - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Endeca Integration (v5 and lower)
We have EBS 12.1.3 with Endeca Information Discovery V5. The INV-LU graph will regularly, but randomly use nearly 300G of disk space for it's indexes files in the directory:
This causes the disk space to completely fill up, crashing the Endeca processes and causing emergency action to be taken in the middle of the work day. The size of these indexes makes no sense, since there isn't even 300G of total data in our entire EBS database, let alone in the INV tables.
Some analysis from one of our consultants seems to indicate that INV-LU is gathering much more data than necessary with it's queries:
The component "Insert into INV_EID_TASK_DATE_TMP" and "Read from DB View INV_EID_TASKS_INCR_V" has queries and views but these do not have conditions on dates(aging). This is wrong and fetching huge volumes of data. Latest run showing that INV_EID_TASKS_INCR_V fetched around 82K records though we are running inv-lu for every 2 hours.
We will NOT be adding a huge amount of disk space to our server for this issue. That's not the solution and I am not going to waste the hardware. The issues with INV-LU using massive amounts of RAM and disk needs to be addressed. No other graphs have any issues at all and use only a tiny fraction of the disk and RAM. Generally less than 1% of what INV-LU uses.
In another SR, SR# 3-13187163521, INV-LU was using all the available RAM on the server. Also, in that SR running a full load was not the solution. It only delayed the issue for a short time. The solution was that we added a bunch more RAM to our server (which goes wasted 99% of the time). Oracle needs to actually fix the obvious issues with INV-LU.
Expect INV-LU to run, without using massive amounts of disk space and without using up all of the RAM.
The issue can be reproduced at will with the following steps:
Run the INV-LU graph.
The issue has the following business impact:
Due to this issue, crashing the Endeca processes and causing emergency action to be taken in the middle of the work day.
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