JDBC issue

[former_member210677]

Hi Experts,

Can anyone let me know about the limitation of the records which XI can pull at a time as we see there are almost 25,00,00 records in the table and XI is not able to pull them.

We see the process started status at communication channel monitering but no records coming to XI.

Any Quick Help in this regard is appreciated.

Thanks & Regards,

Ranganath.

[baskar_gopalakrishnan2]

It all depends on the server hardware, memory etc. But you can always limit the size of records in the design. SAP recommends the optimum message size is upto 5 mb.

You can use select statement query to pick only the required fields also set the flag in the table and update that flag in the update statement . so that you dont reread the same data in the next polling. This way you can maintain the number of records in design way.

This issue is pretty common and We are doing about 25k records for each polling and no problem so far. HOpe that helps.

Have you seen this [link|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/17243] [original link is broken] [original link is broken] [original link is broken];?

[former_member234749]

Hi

Please check the below links.

[http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/18652] [original link is broken] [original link is broken] [original link is broken];

/people/peng.shen2/blog/2009/12/23/pi-how-to-handle-high-volume-data-per-jdbc-adapter

[]

[Shabarish_Nair]

you can limit the number of records that you poll - http://www.delphifaq.com/faq/databases/oracle/f594.shtml

Ideally, 10-30K records per polling is optimal.

[Former Member]

Hi

It all depends on your server configuration.

you can poll more then 70000 records but conditions apply - if it contains only one column, if having 50 columns then you cant fetch even 70000 also, so all depends on the msg size not on the number of records.

Please refer below link,

/people/dheeraj.kumar5/blog/2010/04/12/pixi-sender-jdbc-select-query-and-update-query-to-limit-our-records-to-be-picked-up-by-xi-from-database-to-avoid-huge-message-processing-failed

Thanks

Mary Durai

[Former Member]

chk this discussion: