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

RFC Communication error when doing initial indexing

Hello Everyone,

I have a quick question, when doing the initial index rollup for a BIA index the job is failing with RFC communication error.

We currently have the setting related to " TREXRfcServer threads" set to "Automatic Changes" in order to avoid the RFC Communication errors when loading big loads in BI system.

We currently are on Revision 49.

I also have referred to OSS Note 1138603.

The issue is when I am rolling up the BIA Index the rollup job is failing with RFC Communication errors.

The Global parameters within BIA are:

BATCHPARA - 2

NUMPROC - 5

PKGSIZE - 10000000

SUBPKGSIZE - 20000

We have two app servers with 52 Dialog processes and 25 Background processes.

Any help would be really appreciated.

Thanks

Dharma.

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Apr 22, 2009 at 03:39 PM

    Hi, a few more checks : run the system check from the rsddbiamon2 transaction in your BI system. All entries should be green. Have also a check on the parameter CPIC_MAX_CONV as specified in sapnote 1070034. There is also a check possible through the local TREXAdmin-program to check that your rfc-trheads are in sync with the amount of processes on BI side (not sure if this can be done nowadays through the rsddbiamon2 -> trexadmin tx).

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hello Sharma,

      Yes the issue was resolved. The issue was due to a hardware mismatch we had between the blade center hosts. Our hardware vendor rearranged them with proper slots and things started working fine.

      Thanks

      Dharma.

  • author's profile photo Former Member
    Former Member
    Posted on Apr 21, 2009 at 07:29 PM

    Hi Dharma

    What is the exact error message please?

    Cheers

    Tansu

    Edited by: tansuaksu on Apr 21, 2009 9:29 PM

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      We used the get this once in a while before ver 48/49 - with no apparent reason. Try doing a refresh in the TREX admin tool u2013 under connectivity u2013 and make sure all servers are seen u2013 both BIA and BW. If it shows u201Ctrashu201D u2013 do the refresh until it goes away.

      Cheers

      Tansu

  • author's profile photo Former Member
    Former Member
    Posted on Aug 14, 2009 at 06:33 AM

    The issue got fixed.

    Thanks

    Dharma.

    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.