Strange Error message 2437 when Preparing TREX search connectors

[lothar_bittner]

Hello,

we are trying to re-create our TREX (version 7.10.61) search connectors for SAP PLM.

We had the search connectors all set up in our pre-go-live environment, but had to delete them all due to a massive number of wrong data.

We deleted the connectors in ESH_COCKPIT as well asl all the indexes in TREXADMIN (Index Landscape tab).

When trying to newly crate the search connectors in ESH_COCKPIT we get these error messages for nearly all connectors:

Error Messages (56)

23.12.2014 10:02:42 An exception has occurred

23.12.2014 10:02:42 Join index ESH:EP3100~EP3100~CLES_CLF_MARA~~$PV could not be created

23.12.2014 10:02:42 TREX call terminated with TREX engine error. Error code: 2437

23.12.2014 10:02:42 Error message: join index part does not exist;change_order_id esh:ep3100~ep3100~cles_clf_mara&#

23.12.2014 10:02:42 An exception has occurred

23.12.2014 10:02:42 Join index ESH:EP3100~EP3100~CLES_CLF_AENR~~$PV could not be created

23.12.2014 10:02:42 TREX call terminated with TREX engine error. Error code: 2437

23.12.2014 10:02:42 Error message: join index part does not exist;change_order_id esh:ep3100~ep3100~cles_clf_aenr&#

They all have in common the bit about "joind index part does not exist;change_order_id" - but I have no clue as to what this means and how to fix this...

Any helpful ideas are greatly appreciated!

Thank you

Lothar Bittner

[former_member217429 · Accepted solution]

Hi Lothar,

the error message means that some of the necessary physical indexes don't exist on the TREX side
when the application tries to create the Join  ESH:EP3100~EP3100~CLES_CLF_AENR~~$PV , or the attributes definied in the physical indexes don't match with the attribute definitions in the Join.
As it's very difficult to find out the exact reason of such issue without to check your system directly I would like to ask you to create an OSS incident for this issue.

Best regards,
Mikhail

[lothar_bittner · Accepted solution]

Hello Mikhail,

thank you for your reply.

In the meantime we were able to successfully create the Indexes by deleting all search connectors with Report ESH_ADM_INDEX_ALL_SC and freshly creating them afterwards. Apparently there were some leftovers from earlier attempts to manually delete the connectors and Indexes...

Best regards

Lothar Bittner