cancel
Showing results for 
Search instead for 
Did you mean: 

PLM TREX indexing error while preparing

Former Member
0 Kudos


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

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi, Apply 2057219

0 Kudos

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

frank_friedrich
Contributor
0 Kudos

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

PrasannaGunji
Participant
0 Kudos

Hi Frank,

I am facing similar issue while creating search connector for Material Master. I tried deleting the index and recreating the same, but it's not working for me.

Any help/advice will be highly appreciated.

Below is a snapshot of the error log.

03/27/2014 16:46:54 Process Step: Update Search Runtime Storage

Information Messages (1)

03/27/2014 16:47:14 Prepare search object connector (COMRUNTIME)

Error Messages (8)

03/27/2014 16:47:14 An exception was raised

03/27/2014 16:47:14 Join index ESH:R31200~R31200~0MATERIAL~0MATERIAL_TEXT~$TN could not be created

03/27/2014 16:47:14 TREX call terminated with TREX engine error. Error code: 2434

03/27/2014 16:47:14 Error message: join index inconsistent;unknown joincondition j005,index=esh:r31200~r31200~

03/27/2014 16:47:14 An exception was raised

03/27/2014 16:47:14 Join index ESH:R31200~R31200~0MATERIAL~~MATL_NAV could not be created

03/27/2014 16:47:14 TREX call terminated with TREX engine error. Error code: 2434

03/27/2014 16:47:14 Error message: join index inconsistent;unknown joincondition j003,index=esh:r31200~r31200~

Regards,

Prasanna

Former Member
0 Kudos

Hello Prasanna,

Fot this case I think the only posibility is to delete and recreate the Material Connector, in ESH_COCKPIT and to recreate it. Do you have a big number for Material Master? Normally if you will delete the Material Connector, you will have dependecies with other Connectors.

This corruption of the index should come from the missing memory. In TREXADMIN you have some alerts regarding the Physical Memory?

Hope this helps,

Florin

Former Member
0 Kudos

Hi all,

SAP replied to check he program -> RODPS_ODP_IMG and set the Trex RFC & Client before indexing this need to checked .

We  have reset the client and recreated the indexes , all connectors are active now.


PrasannaGunji
Participant
0 Kudos

Hello Florin,

I tried creating a new Search Connection for Material Master (Connector Name-"0MATERIAL") after deleting all existing indexes (physical and join) from TREXADMIN, but still getting the same error.

We are running on "SAP ERP 6.0 -  EHP7".

Please let me know if there is anything else that I need to look at.

Appreciate your help!

PrasannaGunji
Participant
0 Kudos

Hi Subhash,

I deleted all the existing indexes from TREXADMIN and executed the program - RODPS_ODP_IMG to set the Modeling Client and TREX RFC Destination.

Then I tried re-creating the Search Connector object for Material Master, but it ran into same errors. We are doing this in ECC6-EHP7 (SAP_BASIS-740).

Do I need to select all the models under SAP_APPL SWC to create all the connectors at one go?

Error message: join index inconsistent;unknown joincondition j003,index=esh:r31200~r31200~0material~~matl_nav,location=ersbxdb1:30003

TREX call terminated with TREX engine error. Error code: 2434

Join index ESH:R31200~R31200~0MATERIAL~~MATL_NAV could not be created

An exception was raised

Error message: join index inconsistent;unknown joincondition j005,index=esh:r31200~r31200~0material~0material_text~$tn,location=ersbxdb1:30003

TREX call terminated with TREX engine error. Error code: 2434

Join index ESH:R31200~R31200~0MATERIAL~0MATERIAL_TEXT~$TN could not be created

An exception was raised

Process Step: Rollback

Process Step: Update Search Runtime Storage

Process Step: Change inactive Connector Metadata

Environment Details: TREX Version 7.10.58.00, Destination: TREX_R31, SAP Release 740

Prepare search object connector  (COMRUNTIME)

Thanks for your prompt response!

Regards,

Prasanna

Former Member
0 Kudos

Hi,

I suggest to remove the esh folder from OS level and restart the master & Slave servers and do the indexing .

Thanks,

Subhash.G

frank_friedrich
Contributor
0 Kudos

Hi All,

the root issue can be within Embedded Search or within your TREX environment.

For Embedded Search:

See SAP Note 1764978 - Error when activating ESH connectors without ODP

This is the bug and solved in NW AS 7.31 SP06 the workaround is to execute RODPS_ODP_IMG.

Still mentioned in this thread.

Or Embedded Search is not able to create the indexes on TREX side because there are already exists.

Workaround:

1) Delete all indexes via program: ESH_ADM_INDEX_ALL_SC

2) Check and Delete all indexes in TREXADMIN or the TREX-Admin Tool

3) Check and delete all indexes on operation system level

4) restart TREX demon / service

all of theses 4 steps must be done.

Best regards

Frank


PrasannaGunji
Participant
0 Kudos

Hi Frank,

I did the four steps adviced by you, but still I am unable to create Search Connector for Material Master object (0MATERIAL under SAP_APPL). It ran into same error.

On the other hand I am able to create a Search Connector for Company Code (0COMP_CODE). I scheduled indexing for the same. But when I try to run the search function for the Company Code search connector, it doesn't display any records.

Do I need to run any extractor program(s) to exctract data from database tables? Kindly advice.

Appreciate your help.

Regards,

Prasanna

former_member217429
Active Contributor
0 Kudos

Hi Prasanna,

the issue could be caused either by mistake in the data model on the application/ESH side or it could be also possible that you still have some inconsistencies in the index information on the TREX side  (f.e. indexes still exist on the file system level or in topology). I would like to recommend to open an OSS ticket as it usually very difficult to identify the root cause of the problem without to check the system (ABAP and TREX) remotely.

Best regards,
Mikhail

PrasannaGunji
Participant
0 Kudos

Hi Mikhail,

We have opened an OSS ticket with SAP. And per their advice we implemented below OSS notes.

1870311 Join index cannot be created

1869986 The join index cannot be created

1861144 The join index cannot be created

Post implementation of the above OSS notes, we deleted the existing Service Connector objects (with error) and index file at OS level - " \usr\sap\<SID>\TRX<nn>\index". But we are still facing the same issue.

SAP Support team is going to look into our system. I am waiting for their response and shall post the updates/solution soon.

Thank you.

Regards,

Prasanna

Former Member
0 Kudos

Hello Gunji

did you got a repsonse ? I also have an open message at SAP since 3 weeks and no solution.

Best regards,

Robert

former_member217429
Active Contributor
0 Kudos

Hi Prasanna,

could you please tell me what's the number of your OSS message.

Best regards,
Mikhail

former_member217429
Active Contributor
0 Kudos

Hi Robert,

could you please let me know what's the number of your message?

Thanks,
Mikhail

Former Member
0 Kudos

Hi Mikhail

258770 / 2014


Thank you

former_member217429
Active Contributor
0 Kudos

Hi Robert,

could you please apply the note 1916864.

Thanks and best regards,
Mikhail

former_member217429
Active Contributor
0 Kudos

Hi Robert,

one more thing - it looks like you use a very old version of the TREX - 710 REV 45. Could you please update this to REV 58.

Thanks and best regards,
Mikhail

Former Member
0 Kudos

Hi

24.04.2014 09:46:12 Process Step: Preparation

Information Messages (1)

24.04.2014 09:46:12 Environment Details: TREX Version 7.10.58.00, Destination: TREX_M74_100, SAP Release 740

Regards,

Robert

Former Member
0 Kudos

Hi

this note seems to be for HANA, it has Undefined Implementation State.

On which steps should I be more carefull ?

Best regards,

Robert

former_member217429
Active Contributor
0 Kudos

Hi,

sorry, I took an other RFC  destination to look into TREX. The TREX is REV 58 , so the update isn't reuired. Could you please check if the folder d:\usr\sap\T11\TRX00\index\esh\m74100~m74100~material%%d9f735c4 exists and delete this if necessary.

The mentioned note 1916864 is also valid for TREX. You need to  implement the coding corrections from this note and the coding corrections of the prerequisite notes.

The manual corrections should be covered by the report for the    collective note implementation (report from note 1963778)

Best regards,
Mikhail

Former Member
0 Kudos

Hello

I implemented note 1916864 with all manual activities from side notes.

Now Error code is 8, not 2434.

24.04.2014 13:23:02 Process Step: Update Search Runtime Storage

Information Messages (1)

24.04.2014 13:24:35 Prepare search object connector (COMRUNTIME)

Error Messages (8)

24.04.2014 13:24:35 Index ESH:M74100~M74100~MATERIAL%%D9F735C4 could not be created

24.04.2014 13:24:35 TREX call terminated with TREX engine error. Error code: 8

24.04.2014 13:24:35 Error message: Index is corrupted. Must be deleted/repaired by hand;index=esh:m74100~

24.04.2014 13:24:35 Could not update index TREX_INDEX_ID

24.04.2014 13:24:35 Index ESH:M74100~M74100~MATERIAL%%D9F735C4 could not be created

24.04.2014 13:24:35 TREX call terminated with TREX engine error. Error code: 8

24.04.2014 13:24:35 Error message: Index is corrupted. Must be deleted/repaired by hand;index=esh:m74100~

24.04.2014 13:24:35 Error occured on adjusting authorization indexes

In Trex Admin Tool from Index -> Landscape I selected all Indexes and ran a consistency check.

No errors were found.

Thank you so far.

Best wishes,

Robert Eberle

former_member217429
Active Contributor
0 Kudos

Hi Robert,

I have asked you to  check if the folder d:\usr\sap\T11\TRX00\index\esh\m74100~m74100~material%%d9f735c4 exists and delete this if necessary. Could you please delete the material connector again, check if this folder still exists on the FS level . The consistency check doesn't show such inconsistencies some times. If the folder doesn't exist, it's still possilble that the data still loaded by the IndexServer . So please restart TREXIndexServer and recreate the connector.

Best regards,
Mikhail

Former Member
0 Kudos

Hi

used report ESH_ADM_INDEX_ALL_SC to delete all search connectors.

This deleted also the indexes from TREX and OS-level.

No ESH:M74100~xxxxx Indexes nor in TREX neither in filesystem d:\usr\sap\T11\TRX00\index\esh

Restarted the Service of Trex in Windows.

Created the connector again and the error while preparing:

24.04.2014 13:56:47 Job started
24.04.2014 13:56:47 Step 001 started (program ESH_SE_CONNECTOR_MOD_BGD, variant &0000000000050, user ID REBERLE)

24.04.2014 13:56:48 Process Step: Preparation
Information Messages (1)
24.04.2014 13:56:48 Environment Details: TREX Version 7.10.58.00, Destination: TREX_M74_100, SAP Release 740

24.04.2014 13:56:48 Process Step: Change inactive Connector Metadata
Warning Messages (24)
24.04.2014 13:58:21 Object type ACCESS_CONTROL_CTX, node ACC_ADMIN:
24.04.2014 13:58:21 Node ACC_ADMIN has no response fields but is flagged for subquery
24.04.2014 13:58:21 Object type ENGIN_CHANGE_ORDER, node CHANGEOBJECTTYPE:
24.04.2014 13:58:21 Node CHANGEOBJECTTYPE has no response fields but is flagged for subquery
24.04.2014 13:58:21 Object type MATERIAL, node MATERIAL_SALES:
24.04.2014 13:58:21 Node MATERIAL_SALES has no response fields but is flagged for subquery
24.04.2014 13:58:21 Object type ACCESS_CONTROL_CTX, node ACC_HDR, UI type WD, target navigation DISPLAY:
24.04.2014 13:58:21 Response field ACCID_EXT of URL in target operation does not exist
24.04.2014 13:58:21 Object type DOCUM_INFO_REC, node DOCUMENT, UI type CRM, target navigation DISPLAY DIR:
24.04.2014 13:58:21 Response field doknr of URL in target operation does not exist
24.04.2014 13:58:21 Response field doktl of URL in target operation does not exist
24.04.2014 13:58:21 Response field dokvr of URL in target operation does not exist
24.04.2014 13:58:21 Object type ENGIN_CHANGE_ORDER, node CHANGEOBJECTTYPE:
24.04.2014 13:58:21 Node CHANGEOBJECTTYPE has no response fields but is flagged for subquery
24.04.2014 13:58:21 Object type MATERIAL, node MATERIAL_SALES:
24.04.2014 13:58:21 Node MATERIAL_SALES has no response fields but is flagged for subquery
24.04.2014 13:58:21 Object type ACCESS_CONTROL_CTX, node ACC_ADMIN:
24.04.2014 13:58:21 Node ACC_ADMIN has no response fields but is flagged for subquery
24.04.2014 13:58:21 Object type ACCESS_CONTROL_CTX, node ACC_HDR, UI type WD, target navigation DISPLAY:
24.04.2014 13:58:21 Response field ACCID_EXT of URL in target operation does not exist
24.04.2014 13:58:21 Object type DOCUM_INFO_REC, node DOCUMENT, UI type CRM, target navigation DISPLAY DIR:
24.04.2014 13:58:21 Response field doknr of URL in target operation does not exist
24.04.2014 13:58:21 Response field doktl of URL in target operation does not exist
24.04.2014 13:58:21 Response field dokvr of URL in target operation does not exist

24.04.2014 13:58:21 Process Step: Update Search Runtime Storage
Information Messages (1)
24.04.2014 14:00:41 Prepare search object connector (COMRUNTIME)
Error Messages (84)
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~ACCESS_CONTROL_CTX~ACC_ADMIN~$TN could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~access_control_ctx~acc_admin~$tn
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~ACCESS_CONTROL_CTX~ACC_DESCR~$TN could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~access_control_ctx~acc_descr~$tn
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~ACCESS_CONTROL_CTX~~DEFAULT could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~access_control_ctx~~default,location&
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~CLES_PROPERTY~~DEFAULT could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~cles_property~~default,location=
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~DOCUM_INFO_REC~STATUS_PROTOCOL~$ could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~docum_info_rec~status_protocol~$
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~DOCUM_INFO_REC~DESCRIPTION~$TN could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~docum_info_rec~description~$tn,l
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~DOCUM_INFO_REC~~DEFAULT could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~docum_info_rec~~default,location&#x3d
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~DOCUM_INFO_REC~~PLM could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~docum_info_rec~~plm,location=bcs
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~DOCUM_INFO_REC~~PLM_MAT_CLASS could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~docum_info_rec~~plm_mat_class,locatio
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~ENGIN_CHANGE_ORDER~CHANGEOBJECTT could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~engin_change_order~changeobjecttype~&
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~ENGIN_CHANGE_ORDER~~DEFAULT could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~engin_change_order~~default,location&
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~ENGIN_CHANGE_ORDER~~PLM could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~engin_change_order~~plm,location&#x3d
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~MATERIAL~MATERIAL_SALES~$TN could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~material~material_sales~$tn,loca
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~MATERIAL~MATERIAL_PLANT~$TN could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~material~material_plant~$tn,loca
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~MATERIAL~MATERIAL_DESCRIPTION~$T could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~material~material_description~$t
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~MATERIAL~~DEFAULT could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~material~~default,location=bcsw-
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~MATERIAL~~PLM could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~material~~plm,location=bcsw-sap0
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~PRODUCTION_MBOM~PRODUCTION_MBOM_ could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~production_mbom~production_mbom_item~
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~PRODUCTION_MBOM~PRODUCTION_MBOM_ could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~production_mbom~production_mbom_hist~
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~PRODUCTION_MBOM~~DEFAULT could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~production_mbom~~default,location&#x3
24.04.2014 14:00:41 An exception was raised
24.04.2014 14:00:41 Join index ESH:M74100~M74100~PRODUCTION_MBOM~~PLM could not be created
24.04.2014 14:00:41 TREX call terminated with TREX engine error. Error code: 2434
24.04.2014 14:00:41 Error message: join index inconsistent;index=esh:m74100~m74100~production_mbom~~plm,location=bc

24.04.2014 14:00:41 Process Step: Rollback
Error Messages (1)
24.04.2014 14:00:48 An exception was raised
24.04.2014 14:00:48 Error(s) occurred during connector creation
24.04.2014 14:00:48 Job cancelled after system exception ERROR_MESSAGE

What am I doing wrong ?

Regards,

Robert

former_member217429
Active Contributor
0 Kudos

Hi,

looks like you changed the default language on the ESH side. Could you please run the ESH_IDX_SET_DEFAULT_LANGUAGE  and set the language back to EN (note 1770500). Please recreate the connectors again after this change.

Thanks ,
Mikhail


Former Member
0 Kudos

Hi Mikhail

it worked !

Read solution above from Mikhail Sirotkine.

Best wishes

Robert

former_member217429
Active Contributor
0 Kudos


Hi,

I created a new one OSS note  for this - 2009345.

Best regards,
Mikhail

PrasannaGunji
Participant
0 Kudos

Dear SCN members,

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

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

Thanks so much for your time/efforts/help!!!

Best Regards,

Prasanna

PrasannaGunji
Participant
0 Kudos

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

Former Member
0 Kudos

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.

Former Member
0 Kudos

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