Packet size in SAP 4.7

BW experts,
I need data packages from SAP 4.7 to get 50000 rows at one in a single packet. Right now in BW it is set to get 20000 max per packet. Where can I change it to get more per packet. I am not able to do it on BW side as it say the maximum source system will allow is 20000, where in the source system (SAP 4.7) can I make this change?
Thanks
Ashwin

Hi..
Configuring ROIDOCPRMS table
Transaction SBIW
General Settings->Maintain Control Parameters for Data Transfer
Refer OSS Note : 417307
About ROIDOCPRMS
It is an IDOC parameter source system. This table contains the details of the data transfer like the source system of the data, data packet size, maximum number of lines in a data packet, etc. The data packet size can be changed through the control parameters option on SBIW i.e., the contents of this table can be changed.
with regards,
harikv

Similar Messages

Data packets/size - Generic extractor

Hi all,
We built a custom function module based datasource and it is extracting data to BW in one big packet of 900,000+ records and the load is taking about 18 hours. We are trying to spilt the BW extraction into smaller data packets to improve performance but unable to do so. Following is our extraction program...
Please let me know where we are doing it wrong...
This Program fetches/build e_t_data. The issue is, program does not splitting into packets as the SAP standard program does.
""Local interface:
*" IMPORTING
*" VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*" VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*" VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
*" VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*" VALUE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*" VALUE(I_DATAPAKID) TYPE SBIWA_S_INTERFACE-DATAPAKID OPTIONAL
*" TABLES
*" E_T_DATA STRUCTURE Z0333W OPTIONAL
*" I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT
*" I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS
*" EXCEPTIONS
*" NO_MORE_DATA
DATA: lr_range_name TYPE rsselect-fieldnm.
DATA: st_e_t_data TYPE z0333w.
STATICS: l_cursor TYPE cursor.
STATICS: called(1) TYPE c VALUE 'N'.
Maximum number of lines for DB table
STATICS: l_maxsize TYPE sbiwa_s_interface-maxsize.
FIELD-SYMBOLS: <l_range> TYPE ANY,
 <l_t_range> TYPE STANDARD TABLE.
IF i_initflag = 'X'.
Initialization: check input parameters
 buffer input parameters
 prepare data selection
Fill parameter buffer for data extraction calls
 g_s_interface-requnr = i_requnr.
 g_s_interface-isource = i_dsource.
 g_s_interface-maxsize = i_maxsize.
 g_s_interface-initflag = i_initflag.
 g_s_interface-datapakid = i_datapakid.
 g_flag_interface_initialized = sbiwa_c_flag_on.
 REFRESH g_t_select.
 REFRESH g_t_fields.
 APPEND LINES OF i_t_select TO g_t_select.
 APPEND LINES OF i_t_fields TO g_t_fields.
ELSE.
first data package of first table -> open cursor
 IF g_counter_datapakid = 0.
*--Get selection ranges
 LOOP AT i_t_select.
 MOVE-CORRESPONDING i_t_select TO <l_range>.
 APPEND <l_range> TO <l_t_range>.
 ENDLOOP.
 l_maxsize = g_s_interface-maxsize.
fetch plants for the company code
 PERFORM get_plants.
fetch mast data into internal table as we will be using MAST for validation
of whether BOM exist or not.
 SELECT * FROM mast INTO TABLE it_mast
 WHERE stlan = '1' OR stlan = '6'.
 SORT it_mast BY matnr werks stlan.
Material BOM information
First data package -> OPEN CURSOR
 OPEN CURSOR WITH HOLD l_cursor FOR
 SELECT mast~matnr
 mast~werks
 mast~stlnr
 mast~stlan
 mast~stlal
 stko~stlty
 FROM mast INNER JOIN stko
 ON stkostlnr = maststlnr AND
 stkostlal = maststlal
 FOR ALL entries IN gt_werks
WHERE mast~matnr IN gr_matnr AND
 mast~werks IN gr_werks AND
 mast~stlan IN gr_stlan AND
 mast~werks = gt_werks-werks AND
 mast~stlal = '01' AND
 stko~stlty = 'M' AND "Material BOM only
 ( maststlan = '1' OR maststlan = '6' ).
 ENDIF.
Fetch records into interface table.
named E_T_'Name of extract structure'.
 REFRESH: gt_mat_bom,gt_mat_bom1.
 FETCH NEXT CURSOR l_cursor
 APPENDING CORRESPONDING FIELDS
 OF TABLE gt_mat_bom
 PACKAGE SIZE i_maxsize.
 IF sy-subrc <> 0.
 CLOSE CURSOR l_cursor.
 RAISE no_more_data.
 ELSE.
get BOM data and fill E_T_DATA
 PERFORM get_bom_data TABLES e_t_data.
 ENDIF.
Increment Package
 g_counter_datapakid = g_counter_datapakid + 1.
ENDIF.
ENDFUNCTION
Thanks,
Anirudh.

I'm not sure, but this might help:
* Fetch records into interface table.
* named E_T_'Name of extract structure'.
DO.
 REFRESH: gt_mat_bom,gt_mat_bom1.
 FETCH NEXT CURSOR l_cursor
 APPENDING CORRESPONDING FIELDS
 OF TABLE gt_mat_bom
 PACKAGE SIZE i_maxsize.
 IF sy-subrc <> 0.
 EXIT.
 ELSE.
* get BOM data and fill E_T_DATA
 PERFORM get_bom_data TABLES e_t_data.
 ENDIF.
* Increment Package
 g_counter_datapakid = g_counter_datapakid + 1.
ENDDO.
CLOSE CURSOR l_cursor.
RAISE no_more_data.
Rob

Configuring Packet size for IDOCS on outbound Side

Folks,
Can we configure the packet size for idocs on the onutbound side of the Adapter ?
Manish

Hi Manish,
It is posible if all 1000 idocs are of same Idoc type.
Jus go and change the occurene of Idoc in the XSD as 1..Unbounded. SO that your the message can hold multiple Idocs.
But let me clarify here, if you send 1000 idocs from R3 , it will come to XI as one-by-one. There is no mechanism to get 1000 idocs at a time. So you need to collec all the idocs and then send it.
Just have quick look into this
Packaging IDOCs - SAP R3(IDOCs) -> XI -> Flat File
Regards,
Moorthy

How u will set the external parameters like packet size and number

How u will set the external parameters like packet size and number of parallel process.

Dear Karthik,
ALE:
Use Transaction UPSC02 - ALE Distribution Unit: Packet Types.
Performance Optimization for ODS Objects:
To ensure a good ODS object loading performance, take the following into account:
 1. Creating SIDs
The creation of SIDs takes a long time and can be avoided in the following cases by:
 Not setting the indicator for BEx Reporting if you are using the ODS object only as a data store. If you do set this indicator, SIDs are created for all new characteristic values.
 If you use line items (for example, document number or time stamp) as characteristics in the ODS object, in the characteristic maintenance, indicate these as Attribute Only.
SIDs are created in parallel if parallel activation is switched on (see last point). They are then created with the same number of parallel processes as created for the activation.
However, if you specify a server group or a special server in customizing, these specifications are not only valid for the activation, but also for the SID creation. The creation of SIDs runs on the application server on which the batch job also runs.
 2. DB partitioning in active data tables (technical A table)
By partitioning by database level, you can delete data from the ODS object much more quickly. As a partitioning criterion, choose the characteristic by which you want to delete. For more information on partitioning database tables, see the database documentation (DBMS-CD). Partitioning is supported by the following databases: Oracle, DB2/390, Informix.
 3. Indexing
Use selection criteria for queries for ODS objects. If the key fields are specified, the existing primary index is used. The more frequently accessed characteristic should appear on the left-hand side.
If you did not specify the key fields completely in the selection criteria (visible in the SQL trace), you improve the run time of the query by creating additional indexes. You can create these secondary indexes in the ODS object maintenance.
 4. Activation of data in an ODS object
To improve system performance when activating data in the ODS object, you can make the following entries in Customizing under SAP Customizing Implementation Guide -> SAP NetWeaver -> Business Information Warehouse -> General BW Settings -> ODS Object Settings:
 the maximum number of parallel processes when activating data in the ODS object as when moving SIDs
 the minimum number of data records for each data package when activating data in the ODS object, meaning you define the size of the data packages that are activated
 the maximum wait time in seconds when activating data in the ODS object. This is the time when the main process (batch process) waits for the dialog process that is split before it classifies it as having failed.
 the server group that needs to be used when activating the data in ODS objects in parallel You have to create the server groups beforehand using the following path: Tools -> Administration -> Network -> RFC Destination, RFC -> RFC Groups. If you do not specify anything here, then the activation runs on the server on which the batch process was started for activation. If a server from the server group is not active, then the activation is cancelled.
 5. Loading unique data records
If you only load unique data records (meaning data records with nonrecurring key combinations) into the ODS object, then the loading performance is improved when you set the indicator Unique Data Records in the ODS object maintenance.
The records are then updated more quickly because the system no longer needs to check whether the record already exists. You do have to be sure that there duplicate records are definitely not being loaded, because this will lead to termination.
Regards,
Naveen.

Regrd the data packet size

Hi
i have two questions
1) where can i set the data packet size in BW and R3 and also in BI how and where can we set .
2)by what method/logic we will select the key fields in dso.
ex: i have 5 tables in the sourse and each table will have primary keys, now how do we know that particular primary keys should be kept in KEY FIELDS folder in DSO.
full points will be assigned.

HI,
Data package settings for the data to be extracted from R3 to BI can be done through :
1) SBIW>General Settings> Maintain Control Parameters for Data Transfer
These settings are common for all the info packages which extract data from R3.
2) If u want to do settings relevent to specific Infopackage then :
RSA1>Click On the Specific Infopackage>Scheduler(in the Menu Bar)-->DataS Default Data Transfer.
3) And if you want to do DSO Package settings then:
Got to Transaction RSODSO_SETTINGS
Here u can do package settings for DSO activation ,paramenter for SID generation ect.
And selection of Key fileds depends upon the requirement.
Based on the key fields what all the data fileds u want to overwrite or add the corespomding data fields
Regards,
Chaitanya.

How do I change packet size for a single load

All,
I need to change the packet size for a single load I'm doing. How do I set that?
Thanks.
Dave

Hi..........
For this u hav to go to the infopackage scheduler........
If u r in Process chain >> Right click on the infopackage >> Maintain variant..........then it will come to the IP scheduler..................In the Top Scheduler Tab >> Click on it and select DataS. Default data transfer .......Now there may be a delta IP and Full upload IP for the same datasource.......check ur IP .....it is full or delta..........if full change the packet size for full upload..............otherwise for delta upload........
If the IP is not a part of any Process chain..........then go to RSA1 >> Find the IP..........and double click on it........then the IP scheduler screen will open..........
You can make global settings for all datasources...... in the transaction SBIW in the area General Settings >> Maintain control Parameter for Data transfer......... The parameters that you maintain here are valid as global standard values, and thus apply to all DataSources.
Hope this helps.....
Regards,
Debjani........
Edited by: Debjani Mukherjee on Nov 13, 2008 2:19 PM

Where would i get Batch Size in SAP BI and what is the cocept of Batch Size

<heading 4>
Dear Experts,
I have to create a report on batch size adherence i.e. Actual Vs. Standard Batch Size Deviation,but i am unable to find batch size in sap R/3 AFKO & APPO tables and was unable to find it in material master too.
Please suggest me what is the concept of batch size?where can i get batch size in sap R/3? and in what cube there are chnaces that i will get it on Bi side.
Regards,
Beginer
</heading 4>

Hi,
The dswsbobje web application (war file) is mentioned in SAP IK XI 3.1 install guide to explain how to get the SAP authentication option available in Business Objects products such as Live Office, which use web services to log on to BusinessObjects Enterprise.
The source files for various Business Objects web applications are available in "businessobjects_root\BusinessObjects Enterprise 12.0\java\applications\" folder. Refer to "Deploying the web applications using wdeploy" section in SAP IK XI 3.1 install guide to see how to repackage those web apps and deploy them using wdeploy tool.
Regards,
Boris

Change font size in sap script

hallow
i wont to change the font size in sap script to larger fonts how i do that?
regards

Hi,
Try the following:
Go to Tcode SE71.
Provide the script name & Selct the 'Character Format" Radipobutton from the Subobject tab.
Now go for Change.
There is a Font Button on the rght hand side. select it & here you have Size field. Provide the size of font you want to change.
Same thing you can do for Paragraph format.
Reward points for helpful answers.
Ashvender

DNS after reducing the advertised EDNS UDP packet size to 512 octets

hello
There is something wrong with my DNS server, it open internet webs so slow,and i have no idea with this .
04-Mar-2011 14:31:57.264 zone 0.0.127.in-addr.arpa/IN/com.apple.ServerAdmin.DNS.public: loaded serial 1997022700
04-Mar-2011 14:31:57.264 zone 15.0.168.192.in-addr.arpa/IN/com.apple.ServerAdmin.DNS.public: loaded serial 2011030204
04-Mar-2011 14:31:57.265 zone ******/IN/com.apple.ServerAdmin.DNS.public: loaded serial 2011030404
04-Mar-2011 14:31:57.265 zone localhost/IN/com.apple.ServerAdmin.DNS.public: loaded serial 42
04-Mar-2011 14:31:57.265 running
04-Mar-2011 14:32:00.066 host unreachable resolving 'b.dns-sd.udp.0.0.168.192.in-addr.arpa/PTR/IN': 2001:7fd::1#53
04-Mar-2011 14:32:00.261 host unreachable resolving 'r.dns-sd.udp.0.0.168.192.in-addr.arpa/PTR/IN': 2001:500:2f::f#53
04-Mar-2011 14:32:00.261 host unreachable resolving 'r.dns-sd.udp.0.0.168.192.in-addr.arpa/PTR/IN': 2001:503:c27::2:30#53
04-Mar-2011 14:32:00.261 host unreachable resolving 'r.dns-sd.udp.0.0.168.192.in-addr.arpa/PTR/IN': 2001:503:ba3e::2:30#53
04-Mar-2011 14:32:00.261 host unreachable resolving 'r.dns-sd.udp.0.0.168.192.in-addr.arpa/PTR/IN': 2001:7fd::1#53
04-Mar-2011 14:32:00.261 host unreachable resolving 'r.dns-sd.udp.0.0.168.192.in-addr.arpa/PTR/IN': 2001:dc3::35#53
04-Mar-2011 14:32:00.361 host unreachable resolving 'dr.dns-sd.udp.0.0.168.192.in-addr.arpa/PTR/IN': 2001:500:1::803f:235#53
04-Mar-2011 14:32:00.361 host unreachable resolving 'dr.dns-sd.udp.0.0.168.192.in-addr.arpa/PTR/IN': 2001:7fd::1#53
04-Mar-2011 14:32:00.361 host unreachable resolving 'dr.dns-sd.udp.0.0.168.192.in-addr.arpa/PTR/IN': 2001:dc3::35#53
04-Mar-2011 14:32:00.361 host unreachable resolving 'dr.dns-sd.udp.0.0.168.192.in-addr.arpa/PTR/IN': 2001:503:ba3e::2:30#53
04-Mar-2011 14:32:00.866 host unreachable resolving './NS/IN': 2001:7fd::1#53
04-Mar-2011 14:32:01.005 success resolving './NS' (in '.'?) after reducing the advertised EDNS UDP packet size to 512 octets
04-Mar-2011 14:32:01.408 success resolving 'local/SOA' (in '.'?) after disabling EDNS
04-Mar-2011 14:32:01.533 host unreachable resolving 't.arin.net/AAAA/IN': 2001:503:ba3e::2:30#53
04-Mar-2011 14:32:01.534 host unreachable resolving 'v.arin.net/AAAA/IN': 2001:500:1::803f:235#53
04-Mar-2011 14:32:01.534 host unreachable resolving 'v.arin.net/AAAA/IN': 2001:7fd::1#53
04-Mar-2011 14:32:01.534 host unreachable resolving 'v.arin.net/AAAA/IN': 2001:503:ba3e::2:30#53
04-Mar-2011 14:32:01.534 host unreachable resolving 'w.arin.net/A/IN': 2001:500:1::803f:235#53
anyone help!! Thanks a lot.
Message was edited by: leo.xue

also interesting, when setting DNS servers IPs in Network Settings for your host,
it is important that the IPs are not doubled.
in example if you have Networksettings like
automatic DHCP given from router or server.
IP-Adress: 192.168.2.2
Subnetmask: 255.255.255.0
Router IP: 192.168.2.1
DNS-Server: 127.0.0.1, 192.168.2.2
wich means localhost and again same machine, just different IP..
then your lookup mechanism has to walk thru this steps to know if there is nothing inside to resolve adresses.
which means in this example it would take double the time if DNS-Server would be just 127.0.0.1
you can see if there is a lot to work thru in your logs.
look for something like "sizing zone task pool based on 9 zones".
this mount of zones will change if you set the correct DNS server IP.
more zones are slower than less, very logical!
but this will not solve your problem with packet size at all, it just reduces circles after dns resolves not known adresses even with packet size change.

T3/RMI packet size very large

In order to determine our bandwidth requirements, we recently placed a
sniffer on our network to analyze our message packets. We've noticed
that
our packets are very large and it appears that much of the overhead is
in
the overhead of RMI or T3.
Here are some sample numbers for similar message between a single client
and our WLS server.
T3: 3500 bytes
T3 w/ HTTP tunneling: 5500 bytes
IIOP: 1250 bytes (using VisiBroker ORB talking to Smalltalk ORB)
As you can see the T3 packet size is 65% larger than the same packet
sent
via Corba/IIOP. It also appears that with RMI, all of the full class
names
and variable names are also being passed along within the packet. Are we
missing something or is this an understood fact? Is there anything we
can
do to fix this problem? As it stands, our bandwidth requirements to
support
the larger T3 packet size are astronomical and this would not be
feasible
in a production environment. Does anyone know what is the typical
percentage
overhead increase per packet. It appears to be about 400%.
Our WLS environment is described below.
Edwin Marcial
Continental Power Exchange
Weblogic Environment
WLS Server
WLS 4.51 w/ Service Pack 7
NativeIO = true
ExecuteThreadCount = 40
readTimeoutMillis=5000
readTimeoutMillisSSL=10000
Dell Pentium III 600 w/ 512 MB memory
JavaSoft 1.2.2
-ms128 -mx350
WLS Client
Java Application
t3s and https (using WLS RMI)
JavaSoft 1.1.7b
typically Pentium 200 MHz or better w/ 64MB or more

I think you are kind of stuck with this. RMI is a heavyweight protocol in
comparision to IIOP. If the message sizes really bother you that much you
may want to look into and a EJB implementation that maps RMI to IIOP such as
the Inprise Application Server which sits atop the VisiBroker ORB.
-paul
Edwin Marcial <[email protected]> wrote in message
news:[email protected]..
In order to determine our bandwidth requirements, we recently placed a
sniffer on our network to analyze our message packets. We've noticed
that
our packets are very large and it appears that much of the overhead is
in
the overhead of RMI or T3.
Here are some sample numbers for similar message between a single client
and our WLS server.
T3: 3500 bytes
T3 w/ HTTP tunneling: 5500 bytes
IIOP: 1250 bytes (using VisiBroker ORB talking to Smalltalk ORB)
As you can see the T3 packet size is 65% larger than the same packet
sent
via Corba/IIOP. It also appears that with RMI, all of the full class
names
and variable names are also being passed along within the packet. Are we
missing something or is this an understood fact? Is there anything we
can
do to fix this problem? As it stands, our bandwidth requirements to
support
the larger T3 packet size are astronomical and this would not be
feasible
in a production environment. Does anyone know what is the typical
percentage
overhead increase per packet. It appears to be about 400%.
Our WLS environment is described below.
Edwin Marcial
Continental Power Exchange
Weblogic Environment
WLS Server
WLS 4.51 w/ Service Pack 7
NativeIO = true
ExecuteThreadCount = 40
readTimeoutMillis=5000
readTimeoutMillisSSL=10000
Dell Pentium III 600 w/ 512 MB memory
JavaSoft 1.2.2
-ms128 -mx350
WLS Client
Java Application
t3s and https (using WLS RMI)
JavaSoft 1.1.7b
typically Pentium 200 MHz or better w/ 64MB or more

Packet size and selection screen

hi all.,
i have a requirement where user just need to give the no. of records to be processesed for a execution of a report.
i am using packet size were the user gives the no. of records he want to be executed in a report.
Please let me know how to use packet size in my selection screen
thnkx
bhanu

hi,
check this code regarding packagr size ,no of records to be processed to get out put in report,
TABLES : mkpf,
 mseg,
 zamatdoc,
 mara.
DATA :BEGIN OF gi_mkpf OCCURS 100,
 mblnr LIKE mkpf-mblnr,
 mjahr LIKE mkpf-mjahr,
 END OF gi_mkpf.
data gi_mseg like zamatdoc occurs 100 with header line.
DATA: BEGIN OF gi_mseg OCCURS 0.
 INCLUDE STRUCTURE zamatdoc.
DATA: END OF gi_mseg.
DATA: gv_date(11)," LIKE ekpo-aedat,
 gv_date1(11),
 year(4),
 month(2),
 day(2),
 flag(1),
 read_flag(1).
DATA :char TYPE i,
 count TYPE i.
*select-options : s_mtart for mara-mtart obligatory.
SELECTION-SCREEN: BEGIN OF BLOCK b1 WITH FRAME TITLE text-110.
SELECT-OPTIONS : records FOR char. " OBLIGATORY.
SELECTION-SCREEN : END OF BLOCK b1.
START-OF-SELECTION.
gv_date1 = sy-datum.
year = gv_date1+0(4).
month = gv_date1+4(2).
day = gv_date1+6(2).
year = year - 3.
CLEAR gv_date1.
CONCATENATE year month day INTO gv_date1.
CONCATENATE day month year INTO gv_date1.
SELECT mblnr
 mjahr
 FROM mkpf
 INTO TABLE gi_mkpf
 WHERE budat <= gv_date1.">" and BUDAT >= ).
IF sy-subrc = 0.
 SORT gi_mkpf BY mblnr.
 DELETE ADJACENT DUPLICATES FROM gi_mkpf.
 CLEAR count.
 IF NOT gi_mkpf[] IS INITIAL.
 IF NOT records-low IS INITIAL .
 IF NOT records-high IS INITIAL.
 DESCRIBE TABLE gi_mkpf LINES count.
 IF records-high < count.
 DELETE gi_mkpf FROM records-high TO count.
 ENDIF.
 IF records-low <> 1.
 IF records-low <> 0.
 DELETE gi_mkpf FROM 1 TO records-low.
 ENDIF.
 ENDIF.
 ENDIF.
 ENDIF.
 ENDIF.
SELECT matnr werks FROM mseg INTO CORRESPONDING FIELDS OF TABLE gi_mseg
 PACKAGE SIZE 100 FOR ALL ENTRIES IN gi_mkpf
 WHERE mblnr = gi_mkpf-mblnr
 AND mjahr = gi_mkpf-mjahr.
 MODIFY zamatdoc FROM TABLE gi_mseg.
 COMMIT WORK.
 ENDSELECT.
regards
siva

Default maximum packet size in 3.7.0.1

Hello,
It looks like there is another reason for performing a full cluster restart to apply the first patch for 3.7 (3.7.0.1). On a machine with MTU=1500, it appears that the default maximum packet size value was changed from 1452 to 65535 and this change prevents the cluster from forming during a rolling upgrade.
16 May 2011 14:08:01,376 ERROR Logger@813856187 3.7.0.1: 2011-05-16 14:08:01.376/1.539 Oracle Coherence GE 3.7.0.1 <Error> (thread=Cluster, member=n/a): This member could not join the cluster because of a configuration mismatch between this member and the configuration being used by the rest of the cluster. The maximum packet size (65535) for this member does not match the maximum packet size that the running cluster is using. Rejected by Member(Id=1, Timestamp=2011-05-16 14:05:49.303, Address=XXX2:11500, MachineId=38601, Location=machine:YYY2,process:14945,member:cacheserver:1, Role=cacheserver).
16 May 2011 14:24:27,675 ERROR Logger@98371294 3.7.0.0: 2011-05-16 14:24:27.674/1.539 Oracle Coherence GE 3.7.0.0 <Error> (thread=Cluster, member=n/a): This member could not join the cluster because of a configuration mismatch between this member and the configuration being used by the rest of the cluster. The maximum packet size (1452) for this member does not match the maximum packet size that the running cluster is using. Rejected by Member(Id=1, Timestamp=2011-05-16 14:11:11.927, Address=XXX1:11500, MachineId=38600, Location=machine:YYY1,process:18509,member:cacheserver:1, Role=cacheserver).
Can you please confirm?
Cheers,
Alexey

Hi Alexey,
Yes, the default maximum packet size for 3.7 was supposed to have been 65535, there was however a bug which prevented this from working. 3.7.0.1 fixes this issue, and thus "introduces" the new higher default value. A rolling restart is still possible, you would however need to manually configure the maximum to be 1468. The new maximum of 65535 allows the Coherence default configuration to support large clusters (greater then ~450 JVMs), where as the old default configuration would prevent new members from joining and would require a re-configuration and full restart.
thanks,
Mark
Oracle Coherence

Setting maximum packet size in JDBC driver to send data to database

Could someone tell me how I can set the JDBC connection property of maximum packet size to send data to database?
Regards
Rashed

Hi thanks....I'm having this strange SQLException while trying to insert BLOB image data to Oracle database. I'm saying this strange because for the same image that has been inserted before it's throwing the exception. My program is run from Oracle form and then some image data are inserted into database through a loop. I can't realize what's the problem inside my code that's causing this problem. In fact, when I run my program independently not from Oracle Form, it runs fine, every image data get inserted into database. Given below is my code snippet:
public void insertAccDocs(String[] accessions) throws SQLException
 for(int q=0; q<accessions.length; q++)
 final String docName = accessions[q];
 dbThread = new Thread(new Runnable(){
 public void run()
 try{
 System.out.println("insertDB before connection");
 getConnected();
 System.out.println("insertDB after connection");
 st=con.createStatement();
 //String docName = acc; commented
 // String docName = singleAccession;
 String text = formatFree;
 String qry = "INSERT INTO DOCUMENT VALUES
('"+docName+"','"+text+"','"+formatted+"','"+uiid+"')";
 System.out.println("parentqry"+qry);
 int ok=0;
 ok=st.executeUpdate(qry);
 if(ok==1)
 System.out.println("INSERTION SUCCESS= "+ok);
 System.out.println("Image List Size"+ imgList.size());
 // inserting into child
 for(int i=0;i<imgList.size(); i++)
 String imgPath = ""+imgList.get(i);
 System.out.println("db"+imgPath);
 FileInputStream fin = new FileInputStream(imgPath);
 BufferedInputStream bufStr = new BufferedInputStream(fin);
 byte[] imgByte = new byte[bufStr.available()];
 String img = "" + imgNameList.get(i);
 System.out.println("imgid="+i);
 callable = con.prepareCall("{call prc_insert_docimage(?,?,?)}");
 callable.setString(1,docName);
 callable.setString(2,img);
 callable.setBinaryStream(3, bufStr , (int)imgByte.length);
 callable.execute();
 callable.close();
 con.commit();
 con.close();
 else
 System.out.println("INSERTION NOT SUCCESS");
 // } //else end of severalAcc
 }catch(Exception err){ //try
 System.out.println(err.toString());
 } //run
}); //runnable
dbThread.start();
}And the exception thrown is :
java.sql.SQLException: Data size bigger than max size for this type: #####
Please let me know if possible how I can get around this.
Regards
Rashed

Set idoc Packet Size to always be a single packet

Hi All,
WE20 config has a field for packet size. If I set it to 1, the system will create 1 packet/LUW for each idoc.
If I set it to two, it will wait until there are 2 idocs available and then create 1 packet/LUW for both idocs. however, if that second idoc is never created, the first idoc will never be sent.
Is there a way to specify that the system always send 1 packet/LUW for any number of idocs? So lets say today I created 10 idocs - the system would send that as 1 LUW. Tomorrow, I create 25 idocs, and the system would send that as 1 LUW.
I'm guessing the answer to this is NO, because the system will never know when to stop waiting for more idocs and send them to the receiving system already. The PI developers here are looking for a way to avoid implementing BPM, because they say it will cause performance issues. This was suggested as an alternative. As I said, I doubt it's possible, but I wanted to make certain before going back to them with that info.
Thanks,
Bryan

For some reason I was under the impression that RSEOUT00 wouldn't send the idocs unless the number had been reached, but I see that is not the case.
I always make things more complicated than they need to be.
Thanks!

Set send packet size to 10ms

how to set the audio packet size equivalent to 10 ms ?
Current sample application sends 480 bytes RTP packect and I want it to be 80 bytes. can i set so somehow for G711 Ulaw?
Thanks!!!
Edited by: sahaj on Nov 11, 2009 12:26 PM

sahaj wrote:
Thanks ...i read it even before...just thought may be some simple way is available.Yes - this required a little digging around to find out :-) From memory I think the link above does not include an example of how you actually do it.
Look at the code for the Sun audio transmit example (AVTransmit2.java) and find this code snippet from the createProcessor() method:
             Format format = tracks[0].getFormat();
              if (tracks[0].isEnabled())
                   Format supported[] = tracks[0].getSupportedFormats();
                   tracks[0].setFormat(supported[5]);
              else
                   tracks[0].setEnabled(false); To change the default packet size you need to explicitly specify the uLaw codec chain and change the packetSize property along the way. So the code above now becomes:
              Format format = tracks[0].getFormat();
              if (tracks[0].isEnabled())
                   Format supported[] = tracks[0].getSupportedFormats();
                   tracks[0].setFormat(supported[5]);
                   RCModule rcm = new com.ibm.media.codec.audio.rc.RCModule();
                   JavaEncoder je = new com.ibm.media.codec.audio.ulaw.JavaEncoder();
                   Packetizer p = new com.sun.media.codec.audio.ulaw.Packetizer();
                   p.setPacketSize(80);
                   tracks[0].setCodecChain(new Codec[] {rcm,je,p});
              else
                   tracks[0].setEnabled(false);         You have to create the rate converter (RCModule), the encoder (JavaEncoder) and the packetizer (Packetizer), set the packetizer's packetSize to the desired amount and specifiy the codec chain for the track. A packet size of 80 will give you 10ms.
Hope this helps.
KevB

Packet size in SAP 4.7

Similar Messages

Maybe you are looking for