Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
In EnterpriseOne there is a process to submit a Clear build, which will use the Delete Data Source API in SES to remove entries associated to the EnterpriseOne business view source.
We also have a process to clear the sources and schedules on the SES side. This is done by calling the Delete Data Source API on SES. However on subsequent runs of the same crawler we notice that the database continues to grow as if the tables were not cleared when calling the Delete Data Source API. The expectation is that all data associated to the deleted data sources would be purged from the SES database.
However observed results show that every few times the crawler runs and indexes data, SES will allocate more disk space as the local Oracle database grows. Expectation is that upon re-indexing the same data source, data in the database should increment only by the amount of NEW data found by the crawler. Instead it seems an entire new set of indexed data is added every time the crawler runs.
This behaviour causes continuous growth of the local Oracle database used by SES to store indexed data. This can lead the database to exceed the maximum quota set during SES install.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms