My Oracle Support Banner

E-ES: PTSF_GENFEED Process Failing With Error ""status":404,"error":{"type":"index_not_found_exception","reason":"no such index [indexname_dbname]"" (Doc ID 2964306.1)

Last updated on JULY 31, 2023

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.56 and later
Information in this document applies to any platform.

Symptoms

When attempting to build an Elasticsearch index by running the PTSF_GENFEED process, the following error is shown in the PTSF_GENFEED trace file:

Elasticsearch Raw Response strResp: {"took":0,"errors":true,"items":[{"delete":{"_index":"indexname_dbname","_type":"_doc","_id":"URL?ModType=REPORTS&PrcsInstance=xxxxxxxx&ContentId=xxxxxxx","status":404,"error":{"type":"index_not_found_exception","reason":"no such index [ptsearchreports_csp]","resource.type":"index_expression","resource.id":"indexname_dbname","index_uuid":"_na_","index":"ptsearchreports_csp"}}}

This issue can be reproduced with the following steps:
1) Navigate to PeopleTools -> Search Framework -> Administration -> Deploy Search Object page.
2) Deploy a search definition.
3) In the same navigation, go to Schedule Search Index page and run the Index build process PTSF_GENFEED.
4) Check the trace file generated by the PTSF_GENFEED process in the Process Monitor.   

Cause

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
Symptoms
Cause
Solution


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