Incorrect Search Instance Is Prefilled On Class Search Index Manager And Browse Catalog Index Manager when Having Multiple Search Instances. (Doc ID 3017714.1)

Last updated on APRIL 19, 2024

Applies to:

Symptoms

Having multiple search instances configured with different priorities such as ELASTICSEARCH1 as Priority 1, ELASTICSEARCH2 as priority 50 and PSFT_DEFAULT as priority 100.

A user attempted to update the class search index from the Class Search Index Manager page and succeeded.

The next day, the same user tried to update the index again and was timed out. User noticed that the search instance was selected as "PSFT_DEFAULT", which is incorrect. When user updated the page to ELASTICSEARCH1, which is Search Inst Priority 1, it worked.

When navigating to the Class Search Index Manager, for another user it defaulted to the correct search instance, but when an admin user navigated to the Catalog Search Index Manager, it defaulted to the PSFT_DEFAULT search instance.

The issue can be reproduced at will with the following steps:

1. Navigate to Main Menu > PeopleTools > Search Framework > Administration > Define Search Instances.
2. Add 3 more, INSTANCE_20, INSTANCE_30, & INSTANCE_40.  Just copy the same info from PTSF_DEFAULT.
3. Navigate to Main Menu > PeopleTools > Search Framework > Administration > Prioritize Search Instances.
4. Change PTSF_DEFAULT priority to 5.
5.  Navigate to Main Menu > Curriculum Management > Fluid Class Search > Class Index Full Build.
6.  Build the index using INSTANCE_20. When viewing the Process Monitor page, the process will fail but that's okay.
7. Navigate back to Class Index Full Build and it can be seen that it will default to a different search instance, not the the lowest priority.

Cause

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