Summary
After update to IDM 4.8.6 and having Finnish language configured as additional language, the catalina.out shows an error message "Unrecoverable error during creation of Permission Index"

Products
Identity Manager (IDM)

Environment
Identity Manager 4.8.6

Situation
Catalina.out shows:

10:48:18.475 [RBPM pool-1-permindex executor-ND-thread-1] ERROR com.netiq.idm.cis.PermIndex - Unrecoverable error during creation of Permission Index
com.netiq.cis.spi.IndexException: org.apache.solr.core.SolrCoreInitializationException: SolrCore 'fi' is not available due to init failure: Could not load conf for core fi: Can't load schema /opt/netiq/idm/apps/tomcat/temp/permindex/fi/conf/schema.xml: Plugin init failure for [schema.xml] fieldType "text_fi": Multiple [schema.xml] fieldType registered to the same name: text_fi ignoring: text_fi{class=org.apache.solr.schema.TextField,analyzer=org.apache.solr.analysis.TokenizerChain,args=null}
at com.netiq.cis.permindex.PermissionIndex.initializeIndexes(PermissionIndex.java:213) ~[cis-perm-1.8.0.0.jar:?]
at com.netiq.cis.permindex.PermissionIndex.initialize(PermissionIndex.java:123) ~[cis-perm-1.8.0.0.jar:?]
at com.netiq.idm.cis.PermIndex.initialize(PermIndex.java:305) ~[IDMcis.jar:?]
at com.netiq.idm.cis.PermIndex.access$100(PermIndex.java:77) ~[IDMcis.jar:?]
at com.netiq.idm.cis.PermIndex$1.run(PermIndex.java:177) ~[IDMcis.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_342]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_342]
at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_342]
Caused by: org.apache.solr.core.SolrCoreInitializationException: SolrCore 'fi' is not available due to init failure: Could not load conf for core fi: Can't load schema /opt/netiq/idm/apps/tomcat/temp/permindex/fi/conf/schema.xml: Plugin init failure for [schema.xml] fieldType "text_fi": Multiple [schema.xml] fieldType registered to the same name: text_fi ignoring: text_fi{class=org.apache.solr.schema.TextField,analyzer=org.apache.solr.analysis.TokenizerChain,args=null}
at org.apache.solr.core.CoreContainer.getCore(CoreContainer.java:1977) ~[solr-core-8.11.2.jar:8.11.2 17dee71932c683e345508113523e764c3e4c80fa - mdrob - 2022-06-13 11:27:54]
at org.apache.solr.core.CoreContainer.getCore(CoreContainer.java:1950) ~[solr-core-8.11.2.jar:8.11.2 17dee71932c683e345508113523e764c3e4c80fa - mdrob - 2022-06-13 11:27:54]
at org.apache.solr.client.solrj.embedded.EmbeddedSolrServer.request(EmbeddedSolrServer.java:194) ~[solr-core-8.11.2.jar:8.11.2 17dee71932c683e345508113523e764c3e4c80fa - mdrob - 2022-06-13 11:27:54]
at org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:214) ~[solr-solrj-8.11.2.jar:8.11.2 17dee71932c683e345508113523e764c3e4c80fa - mdrob - 2022-06-13 11:27:56]
at org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:177) ~[solr-solrj-8.11.2.jar:8.11.2 17dee71932c683e345508113523e764c3e4c80fa - mdrob - 2022-06-13 11:27:56]
at org.apache.solr.client.solrj.SolrClient.addBean(SolrClient.java:285) ~[solr-solrj-8.11.2.jar:8.11.2 17dee71932c683e345508113523e764c3e4c80fa - mdrob - 2022-06-13 11:27:56]
at org.apache.solr.client.solrj.SolrClient.addBean(SolrClient.java:267) ~[solr-solrj-8.11.2.jar:8.11.2 17dee71932c683e345508113523e764c3e4c80fa - mdrob - 2022-06-13 11:27:56]
at com.netiq.cis.permindex.PermissionSearchEngine.addPermission(PermissionSearchEngine.java:85) ~[cis-perm-1.8.0.0.jar:?]
at com.netiq.cis.permindex.PermissionIndex.initializeIndexes(PermissionIndex.java:200) ~[cis-perm-1.8.0.0.jar:?]
... 7 more

Resolution
Edit the /opt/netiq/idm/apps/tomcat/temp/permindex/fi/conf/schema.xml file.
Comment out the following section:
<!-- <fieldType name="text_${xx}" class="solr.TextField" positionIncrementGap="100">
<analyzer>
<tokenizer class="solr.StandardTokenizerFactory" />
<filter class="solr.LowerCaseFilterFactory" />
</analyzer>
</fieldType>
-->

Restart the tomcat service: systemctl restart netiq-tomcat.service

Additional Information
This works fine until for some reason the permindex folder has to be deleted. The initial situation will be back again after restarting the tomcat service and the same change need to be re-applied.

Knowledge Base Article Link

20-Oct-2022•Knowledge
URL Name
KM000011363