Well, it's rather unrelated to spring or ibatis, I bet with pure JDBC the problem will still be there.
50000x4000 ~ 200Mb - 2 hours may indeed be reasonable. Here's what I'd check in the first place: Single transaction for all that 200Mb means allocating large rollback segments etc, I'd try splitting it into smaller ones. Check whether table where insert is done is already sized properly, so that Oracle does not have to allocate more space during your inserts. Use statement batching. Good luck On 2/2/07, kovy <[EMAIL PROTECTED]> wrote:
hey everyone, I'm having a performance problem. I need to insert around 50000 records in one time. These insert statement can contain CLOB values with over more then 4000 characters. It takes up to 2 hours to do this procedure. Is this normal??? Or what is the best way to do this??? I can't go explaining my architecture completelly, the method which executes this functionality is transactional and the SQL map method is transactional too. thnx Stefaan -- View this message in context: http://www.nabble.com/spring-%2B-ibatis-%2B-oracle-tf3159908.html#a8764127 Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
On 2/2/07, kovy <[EMAIL PROTECTED]> wrote:
hey everyone, I'm having a performance problem. I need to insert around 50000 records in one time. These insert statement can contain CLOB values with over more then 4000 characters. It takes up to 2 hours to do this procedure. Is this normal??? Or what is the best way to do this??? I can't go explaining my architecture completelly, the method which executes this functionality is transactional and the SQL map method is transactional too. thnx Stefaan -- View this message in context: http://www.nabble.com/spring-%2B-ibatis-%2B-oracle-tf3159908.html#a8764127 Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
