BATCHPARA ??

Question about BatchPara and what is going on here.
I went to index cube ZBM_C021 in BWA (ver 53) and see the following in the Job output:
12/08/2009 14:00:15 INFOCUBE: ZBM_C021
12/08/2009 14:00:15 Statistics UID of indexing job: '4G3O2H296L13RHNVBY7HLQQ4I' (RSDDSTATTREX/RSDDSTATTREXSERV)
12/08/2009 14:00:15 Parameter BATCHPARA during indexing: '3'
12/08/2009 14:00:15 '6' different values in column 'DIMID' of table '/BIC/DZBM_C021T'
12/08/2009 14:00:15 WHERE clause: OPT ='BT', LOW = '', HIGH = '0000000004' (field: 'DIMID')
12/08/2009 14:00:15 Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BITRP_4G3O2KWINVVV2RDY8ZDMMQ30I with ID 14001500
12/08/2009 14:00:15 WHERE clause: OPT ='BT', LOW = '', HIGH = '0000000006' (field: 'DIMID')
12/08/2009 14:00:15 Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BITRP_4G3O2KWINVVV2RDY8ZDMMQ30I with ID 14001501
I noticed that my global setting (tcode: rsddbiamon) was indeed 3
BATCHPARA     Number of Processes for Batch Parallel Processing of Initial Indexing     3
So my questions are:
a) What is Batchpara and do I need to change it to something else?
b) It spun off some other jobs ... what's going on there?
Mike

Hi Mike,
BATCHPARA has always been there. It defined how many parallel processes can be used for intial indexing of cube's fact table to speed up this processing step.
Please have a look at: http://help.sap.com/saphelp_nw70/helpdata/en/43/e2ac21778002d3e10000000a1553f7/frameset.htm for details.
Regards,
-Vitaliy

Similar Messages

  • BATCHPARA  NUMPROC Parameter in BWA

    Hi All,
    Please let me know where to check BATCHPARA and NUMPROC parameter in SAP BWA and also let me know  how to change the values of those parameters.
    Regards,
    Asim

    Hi Asim,
    please post your query in BWA space!!
    Regards,
    Harish

  • ERROR in the RFC communication when parabatch is set to more 3 (default)

    Hi experts,
    We have a 10 blades BIA system connecting to our BW Production. When we set the parabatch to more than the default 3 (we set to 4 or 5), We keep getting 'Batchpara Error' and 'Error in the RFC Communication: Error when opening an RFC Connection' during the initial index build. Here are what we do and what we see:
    1. set parabatch to 5 and build 1 initial index (cube is 46 mil rows, 22 GB in size) - Failed with the above errors
    2. set parabatch back to 3 and build 1 initial index (same cube as above)- successful but slow
    3. set parbatch back to 3 and build 2 initial indexes simultaneously (16 mil rows/4GB and 6 mil rows/2 GB) - Failed with the above errors.
    In the BIA index log I see the following error:
    Error in the RFC communication: Error when opening an RFC connection (TREX_BIP)
    Message no. STREX005
    In SM37 in one of the logs I see the followings:
    Parabatch Error
    Any light you can shed on why we are encountering this issue will be much appreciated. Also, I observed that there is a long idle time in all systems (BIA, DB2, BW) and seemed like their respective resources were not utilized at all. Once in a while I do see surge of cpu/memory usage in all systems but not too terrible. I'm puzzled by why there is such long interval of idle time in all systems while the initial index build is going on.
    BTW...we did the same thing (set parabatch to 5, and run parallel initial builds) in our non-prod BIA (2 blades) and QA BW landscape and do not have any issue at all.
    Thanks!
    Kee

    Hello
    PLease check the sapnotes and check the developer trace for more information.
    Note 314530 - Number of RFC/CPIC connections for external clients
    Note: 1070034
    It can also be because your system has reached it its max gateway connections...also check whether you are getting error message "Communication error, CPIC return code 017, SAP return code 450
    " in sm21  ???
    Regards
    Karthikeyan.K

  • 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.

    Removing references to systems and ports
    Issue:
    When the initial indexing is being carried out for an InfoCube to
    create the BIA Index and there is more than one application server in
    the system the job is failing with the http error.
    Hello Everyone,
    Thanks for the input, after the automatic changes was configured for concurrent requests the error is different right now.
    The error message is,
    "Remote communication failure with partner http://<Removed>:<removed>/indexCellTable"
    Overview/Background:
    When the indexing job is triggered as a background job the failure happens when the S table index is being filled.
    In our system where we are trying to do the stress testing we currently have two app servers and one central instance.
    When I limit the RFCGROUP in RSDDTREXADMIN table to one App server in terms of logon group the job finishes fine.
    Whereas, when I do not limit the RFCGROUP and all app servers are open for access the background job finishes with the error message
    Remote communication failure with partner http://<Removed>:<removed>/indexCellTable.
    We have looked into the OSS Note 1102652 and our BASIS team confirmed that they were able to ping from BI App servers into BIA blades and vice versa.
    We also confirmed if the local gateway was used for connectivity.
    The above issue was not in other systems where we only had one server.
    We currently are at Revision 49 and SP 13 in BI.
    We have E5345 Clowertown blades (2 x 4) 16GB blades.
    Please let us know if you need additional information.
    Thanks in advance for the input.
    Dharma.
    Edited by: Arun Varadarajan on Apr 24, 2009 1:36 AM

Maybe you are looking for