ELM 9.2: SES Full Index Rebuild Does Not Allow Users to Query Catalog While Full Index Jobs are Executing

(Doc ID 1958571.1)

Last updated on OCTOBER 19, 2016

Applies to:

PeopleSoft Enterprise ELM Enterprise Learning Management - Version 9.2 and later
Information in this document applies to any platform.


Question 1: Why Users cannot query catalog while FULL Index jobs are running?
Question 2: SES has an incremental maintainence process that just adds/deletes changes that have occurred. I would assume after running the incremental X amount of times, the SES optimization job should run. 9.2 Vanilla is set to run weekly on SatNight/SunMorn by default. Therefore, we assume Oracle is recommending an SES optimization run weekly?

Question 3: The optimization process could allow the incrementally updated index to perform well for a long period of time? (i.e., 6 months or a year?)

Question 4: Does incremental do both adds & deletes & updates? IF so, why would anyone ever do FULL re-build (except for initial creation purposes, or problem resolution, etc.)?
This assumes we are doing incrementals every 30 minutes and optimizations every week.
If ELM has a problem with SES and the index is suspect, and we need to rebuild it fully, then we would have to bring down the application for 2 hours to rebuild the index.

Question 5: Can the optimization process job (for SES) can run during catalog use, without user errors? Requesting the official Oracle position.


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