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

Real Time Indexing takes a long time

Hello Guru's.

I am trying to schedule the Real Time Indexing for the data in the system and its taking a very long time that expected.

What could be reason for this.

Below is the Job Log.

Kindly advice on what needs to be done.

Thanks & Regards

Jo Pz

05/13/2015 11:51:56 Job started
05/13/2015 11:51:56 Step 001 started (program ESH_SE_CONNECTOR_MOD_BGD, variant &0000000000007, user ID XXXXXXX&#x29

05/13/2015 11:51:57 Process Step: Preparation
Information Messages (1)
05/13/2015 11:51:57 Environment Details: TREX Version 7.10.57.00, Destination: TREX_RFC, SAP Release 740

05/13/2015 11:51:57 Process Step: Change inactive Connector Metadata
Warning Messages (46)
05/13/2015 11:53:34 Object type MATKL, node MATKL:
05/13/2015 11:53:34 There is a field with the same name as the alias MATKL
05/13/2015 11:53:34 Object type ENGIN_CHANGE_ORDER, node ENGINEERINGCHANGEORD, request PLM:
05/13/2015 11:53:34 Request fields have been removed
05/13/2015 11:53:34 Object type ENGIN_CHANGE_ORDER, node CHANGEOBJECTTYPE:
05/13/2015 11:53:34 Node CHANGEOBJECTTYPE has no response fields but is flagged for subquery
05/13/2015 11:53:34 Object type ACCESS_CONTROL_CTX, node ACC_ADMIN:
05/13/2015 11:53:34 Node ACC_ADMIN has no response fields but is flagged for subquery
05/13/2015 11:53:34 Object type ENGIN_CHANGE_REC, node ECR_CASE_ATTR:
05/13/2015 11:53:34 Node ECR_CASE_ATTR has no response fields but is flagged for subquery
05/13/2015 11:53:34 Object type ACCESS_CONTROL_CTX, node ACC_HDR, UI type WD, target navigation DISPLAY:
05/13/2015 11:53:34 Response field ACCID_EXT of URL in target operation does not exist
05/13/2015 11:53:34 Object type DOCUM_INFO_REC, node DOCUMENT, UI type CRM, target navigation DISPLAY DIR:
05/13/2015 11:53:34 Response field doknr of URL in target operation does not exist
05/13/2015 11:53:34 Response field doktl of URL in target operation does not exist
05/13/2015 11:53:34 Response field dokvr of URL in target operation does not exist
05/13/2015 11:53:34 Authorization check PLMB_USER_WITHDRAW:
05/13/2015 11:53:34 Path-based authorization check PLMB_USER_WITHDRAW has wrong data
05/13/2015 11:53:34 Authorization check PLMB_USER_GROUP:
05/13/2015 11:53:34 Path-based authorization check PLMB_USER_GROUP has wrong data
05/13/2015 11:53:34 Authorization check PLMB_USER_GRANT:
05/13/2015 11:53:34 Path-based authorization check PLMB_USER_GRANT has wrong data
05/13/2015 11:53:34 Authorization check ESH_CONN_AUTH, auth. obj. field assignments:
05/13/2015 11:53:34 Not all authorization fields are mapped to node fields or constants
05/13/2015 11:53:34 Object type MATKL, node MATKL:
05/13/2015 11:53:34 There is a field with the same name as the alias MATKL
05/13/2015 11:53:34 Object type ENGIN_CHANGE_ORDER, node CHANGEOBJECTTYPE:
05/13/2015 11:53:34 Node CHANGEOBJECTTYPE has no response fields but is flagged for subquery
05/13/2015 11:53:34 Object type ACCESS_CONTROL_CTX, node ACC_ADMIN:
05/13/2015 11:53:34 Node ACC_ADMIN has no response fields but is flagged for subquery
05/13/2015 11:53:34 Object type ENGIN_CHANGE_REC, node ECR_CASE_ATTR:
05/13/2015 11:53:34 Node ECR_CASE_ATTR has no response fields but is flagged for subquery
05/13/2015 11:53:34 Object type ACCESS_CONTROL_CTX, node ACC_HDR, UI type WD, target navigation DISPLAY:
05/13/2015 11:53:34 Response field ACCID_EXT of URL in target operation does not exist
05/13/2015 11:53:34 Object type DOCUM_INFO_REC, node DOCUMENT, UI type CRM, target navigation DISPLAY DIR:
05/13/2015 11:53:34 Response field doknr of URL in target operation does not exist
05/13/2015 11:53:34 Response field doktl of URL in target operation does not exist
05/13/2015 11:53:34 Response field dokvr of URL in target operation does not exist
05/13/2015 11:53:34 Authorization check PLMB_USER_WITHDRAW:
05/13/2015 11:53:34 Path-based authorization check PLMB_USER_WITHDRAW has wrong data
05/13/2015 11:53:34 Authorization check PLMB_USER_GROUP:
05/13/2015 11:53:34 Path-based authorization check PLMB_USER_GROUP has wrong data
05/13/2015 11:53:34 Authorization check PLMB_USER_GRANT:
05/13/2015 11:53:34 Path-based authorization check PLMB_USER_GRANT has wrong data
05/13/2015 11:53:34 Authorization check ESH_CONN_AUTH, auth. obj. field assignments:
05/13/2015 11:53:34 Not all authorization fields are mapped to node fields or constants

05/13/2015 11:53:34 Process Step: Update Search Runtime Storage
Information Messages (1)
05/13/2015 11:55:35 Prepare search object connector (COMRUNTIME)

05/13/2015 11:55:35 Process Step: Change active Connector Metadata

05/13/2015 11:55:52 Process Step: Finalization
Information Messages (24)
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~ACCESS_CONTROL_CTX~%EE4B75F9 Runtime: 423msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~DOCUM_INFO_REC~%A8ACFB20 Runtime: 377msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~DOCUM_INFO_REC~%4C316347 Runtime: 319msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~DOCUM_INFO_REC~%69F782E0 Runtime: 320msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~ENGIN_CHANGE_ORDER~%F1C7515E Runtime: 348msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~ENGIN_CHANGE_ORDER~%275AD940 Runtime: 313msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~ENGIN_CHANGE_ORDER~%41D5B2CD Runtime: 321msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~ENGIN_CHANGE_ORDER~%01DEEE48 Runtime: 272msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~ENGIN_CHANGE_REC~%7A11E5AC Runtime: 255msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~ENGIN_CHANGE_REC~%FA3159C4 Runtime: 263msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~ENGIN_CHANGE_REC~%BAC59EA4 Runtime: 355msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~ESH_CATEGORY~%D9632530 Runtime: 374msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~ESH_CONNECTOR~%52CAED9F Runtime: 360msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~MATERIAL~%610FEFF8 Runtime: 236msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~MATERIAL~%F01E277D Runtime: 261msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~MATERIAL~%8D4FF51E Runtime: 277msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~MATERIAL~%1AEDF8D4 Runtime: 278msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~MATERIAL~%D9F735C4 Runtime: 277msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~PRODUCTION_MBOM~%3DDB82AA Runtime: 300msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~PRODUCTION_MBOM~%F04BB54B Runtime: 239msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~PRODUCTION_MBOM~%713EE174 Runtime: 257msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~VENDOR~%2A175641 Runtime: 496msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~VENDOR~%840CEE3D Runtime: 311msec
05/13/2015 11:55:59 ESH:ERQ450~ERQ450~VENDOR~%A733DF61 Runtime: 260msec
05/13/2015 11:56:15 Job finished

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on May 20, 2015 at 12:11 PM

    Hi Jo,

    based on the Job log the job needs less than 5 min to be completed. So it looks fine.
    What's the TREX version you use? Probably you can improve little bit performance when increase
    the value of the tmpx_threads parameter in TREXIndexServer.ini (you can set this to the same
    value as the number of CPU cores on the TREX server). Are the memory deltas active and the
    merge is set to be executed as cron job?

    Best regards,
    Mikhail

    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.