NPE When Using IdcAnalyzer To Check ElasticSearch Index (Doc ID 2981929.1)

Last updated on JULY 20, 2024

Applies to:

Symptoms

On : 12.2.1.4.0 version, Content Server

When attempting to use IdcAnalyze to check the search index for an ElasticSearch index,
the following error occurs.

ERROR
-----------------------
>searchquery/6 06.15 09:51:24.702 Thread-8 query(live): ("must":{"range" : {"dID" : {"gte" : "1"}}} ES_AND "must":{"range" : {"dID" : {"lt" : "501"}}}) [1,500] sort(dID Asc)
>elasticsearch/7 06.15 09:51:24.702 Thread-8
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.common.DefaultTraceImplementor.appendStackTrace(DefaultTraceImplementor.java:348)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.common.DefaultTraceImplementor.dumpException(DefaultTraceImplementor.java:412)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.common.DefaultReportHandler.message(DefaultReportHandler.java:507)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.common.DefaultReportDelegator.message(DefaultReportDelegator.java:140)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.common.Report.messageInternal(Report.java:172)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.common.Report.message(Report.java:145)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.common.Report.debug(Report.java:193)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.elasticsearch.search.ElasticSearchImplementor.doQuery(ElasticSearchImplementor.java:188)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.search.CommonSearchConnection.doQuery(CommonSearchConnection.java:158)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.server.SearchManager.retrieveSearchInfoAsBinder(SearchManager.java:233)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.server.SearchService.retrieveSearchInfo(SearchService.java:2036)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.server.SearchService.doLocalSearch(SearchService.java:1504)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.apputilities.idcanalyze.IndexCheck.retrieveSearchResults(IndexCheck.java:506)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.apputilities.idcanalyze.IndexCheck.retrieveSearchResults(IndexCheck.java:476)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.apputilities.idcanalyze.IndexCheck.doTask(IndexCheck.java:233)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.apputilities.idcanalyze.IdcAnalyzeApp$1.run(IdcAnalyzeApp.java:275)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at java.lang.Thread.run(Thread.java:750)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 Caused by: java.lang.NullPointerException
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.shared.SecurityUtils.determineGroupsAccessible(SecurityUtils.java:377)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.shared.SecurityUtils.getUserGroupsWithPrivilege(SecurityUtils.java:88)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.elasticsearch.search.ElasticSearchImplementor.getSearchEndPoint(ElasticSearchImplementor.java:1520)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 at intradoc.elasticsearch.search.ElasticSearchImplementor.doQuery(ElasticSearchImplementor.java:170)
 elasticsearch/7 06.15 09:51:24.702 Thread-8 ... 9 more
Error checking index:


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Use IdcAnalyze to check an ElasticSearch index
2. Observe error
NOTE: This is something this customer can reproduce, but not Support.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, admin users cannot use IdcAnalyze to check an ElasticSearch index.

Cause

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