• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 95 subscribers
  • Views 805 views
  • Users 0 members are here
Options
Related

In V9.0 LTS profileHasAuthObjectField step, while synching SAP authorization details from Target System it is not synching the data when records are huge

supriya avvaru
over 1 year ago

In V9.0 LTS profileHasAuthObjectField step, while synching SAP authorization details from Target System it is not synching the data when records are huge.

This step at first instance was supposed to fetch around 80 millions of records which is not able to pull the data. It is working fine for less amount of data. 

Also, as soon as this step starts, CPU memory is reaching to 100% and this stops the job services automatically and affecting  rest of all other jobs running in the synch.

Not able to synch the data with this step for larger SAP systems.

Please suggest how can I make is possible in 1st instance? On 2nd instance will it synch data properly if we use revision filter? 

Both sapnco.dll & sapnco_utils.dll are of V 3.0.24.0.

Please suggest how to fetch such huge data.


Thanks in advance.

Parents
  • 0 over 1 year ago

    Hi Supriya,

    do you see any error messages in the job service log?

    regards, Tino

  • 0 over 1 year ago in reply to tlindner

    Thanks for your reply.

    I could see only below in the RFC logs.

    SAP.Middleware.Connector.RfcCommunicationException:
    LOCATION SAP-Gateway on host XXX.XX.com / sapgw02
    ERROR Conversation 06947021 not found
    TIME Tue Apr 4 09:10:45 2023
    RELEASE 753
    COMPONENT SAP-Gateway
    VERSION 2
    RC 728
    MODULE /bas/753_REL/src/krn/si/gw/gwxxconn.c
    LINE 954
    COUNTER 2579862

    >> Info entry 2023-04-04 11:37:12.339 [Thread 32]
    Ignoring invalid LZ-compressed data block
    >> Info entry 2023-04-04 11:39:28.505 [Thread 4]
    Ignoring invalid LZ-compressed data block
    >> Info entry 2023-04-04 11:40:11.762 [Thread 32]
    Ignoring invalid LZ-compressed data block
    >> Info entry 2023-04-04 11:40:19.996 [Thread 4]

Reply
  • 0 over 1 year ago in reply to tlindner

    Thanks for your reply.

    I could see only below in the RFC logs.

    SAP.Middleware.Connector.RfcCommunicationException:
    LOCATION SAP-Gateway on host XXX.XX.com / sapgw02
    ERROR Conversation 06947021 not found
    TIME Tue Apr 4 09:10:45 2023
    RELEASE 753
    COMPONENT SAP-Gateway
    VERSION 2
    RC 728
    MODULE /bas/753_REL/src/krn/si/gw/gwxxconn.c
    LINE 954
    COUNTER 2579862

    >> Info entry 2023-04-04 11:37:12.339 [Thread 32]
    Ignoring invalid LZ-compressed data block
    >> Info entry 2023-04-04 11:39:28.505 [Thread 4]
    Ignoring invalid LZ-compressed data block
    >> Info entry 2023-04-04 11:40:11.762 [Thread 32]
    Ignoring invalid LZ-compressed data block
    >> Info entry 2023-04-04 11:40:19.996 [Thread 4]

Children