Skip to Content
author's profile photo Former Member
Former Member

PLM TREX indexing error while preparing


Hi all,

We are on ECC6.0 EHP6 sp5 with PLM ESH - indexing enabled.

TREX is on 7.1 version 56.

We are trying to re index the PLM connectors and running to issues with PLM Status managment & Plants assigned to material .

Out of 17 connectors 14 are active and searchable three objects has these errors.

An exception has occurred

19.02.2014 19:50:54 Join index ESH:201~x201~PLM_SAM_STATUS~~DEFAULT could not be created

19.02.2014 19:50:54 TREX call terminated with TREX engine error. Error code: 2434

19.02.2014 19:50:54 Error message: join index inconsistent;index=esh:201~201~plm_sam_status~~default,location&#x3d

Object type DOCUM_INFO_REC, node DOCUMENT:

19.02.2014 19:50:54 Response fields DOKNR_EXT_1 and DOKNR_EXT refer to the same node field

19.02.2014 19:50:54 Object type DOCUM_INFO_REC, node DOCUMENT, UI type CRM, target navigation DISPLAY DIR:

19.02.2014 19:50:54 Response field doknr of URL in target operation does not exist

19.02.2014 19:50:54 Response field doktl of URL in target operation does not exist

19.02.2014 19:50:54 Response field dokvr of URL in target operation does not exist

19.02.2014 19:50:54 Object type DOCUM_INFO_REC, node DOCUMENT:

19.02.2014 19:50:54 Response fields DOKNR_EXT and DOKNR_EXT_1 refer to the same node field

19.02.2014 19:50:54 Object type DOCUM_INFO_REC, node DOCUMENT, UI type CRM, target navigation DISPLAY DIR:

19.02.2014 19:50:54 Response field doknr of URL in target operation does not exist

19.02.2014 19:50:54 Response field doktl of URL in target operation does not exist

Please guide me how to fix this.

Thanks,

Subhash.G

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Mar 13, 2014 at 09:08 AM

    I experience the same error (DOKNR_EXT / DOKNR_EXT_1). Have you found a solution for this?

    Thanks.

    It actually is only a warning message. The error was to be found somewhere else - another attribute that wasn't ok.

    My solution was to delete the search connector and then create it again afterwards - including a full index run. Now everything works again.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello,

      The first problem should be for the index: esh:201~201~plm_sam_status~~default, search for this index in TREXADMIN->INDEX LANDSCAPE and here type the index esh:201~201~plm_sam_status~~default. If this index is corrupted then you must recreate this index and then it will work.

      Thanks and regards,

      Florin

  • Posted on Mar 18, 2014 at 12:58 PM

    Hi,

    the error is related to:

    19.02.2014 19:50:54 Join index ESH:201~x201~PLM_SAM_STATUS~~DEFAULT could not be created

    19.02.2014 19:50:54 TREX call terminated with TREX engine error. Error code: 2434

    19.02.2014 19:50:54 Error message: join index inconsistent;index=esh:201~201~plm_sam_status~~default,location&#x3d

    My suggestion is to delete all search connectors. Check if on TREX side as well all indexes are deleted. Check if on OS side of the TREX a well all index folders are deleted.

    Re-create the indexes.

    Best regards

    Frank

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Robert,

      Our issues with TREX-7.1 on ECC6-EHP7 has been resolved by SAP Support team.

      Following notes were suggested by SAP Support team in our case.

      ---------------------------------------------------------------------------------------------------------------

      1965028 SAPKB74005: Composite SAP Note 1
      1963778 Report for composite SAP Note 1965028
      1982413 SAPKB74005: Composite SAP Note 2
      1982392 Report for composite SAP Note 1982413

      Please implement note 1963778 and execute the report.
      Then implement composite note 1965028.
      The notes describe the details and there may be some manual work.
      You could test again at this point (similar problems were resolved by these composite notes).

      Additionally we recommend implementing the second composite note too:
      Please implement note 1982392 and execute the report.
      Then implement composite note 1982413.

      Disable the indexusage collector in trex explicitly by setting active = no in the indexserver.ini file.
      The note below is for BWA but applies also to TREX.
      1448964 - BWA 7.00: Index Usage Collector Leads to Memory Issues

      ----------------------------------------------------------------------------------------------------------------

      Regards,

      Prasanna

  • Posted on May 19, 2014 at 12:37 PM

    Hi Community,

    just for your information: If someone should come accross the same error with the new SRM shopping cart user interface (SRM User Interface Add-On 1.0 = SRM UI5) with SRM 7 EhP 3, basis 7.40 (SP04/SP05) while setting up the TREX search connectors, the following (above mentioned) notes solved the issue:

    • 1869986
    • 1870311
    • 1916864

    Best,

    Christian

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 12, 2014 at 07:18 AM

    Hi, Apply 2057219

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.