
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
DB2 Data loading issue
Hello team,
I am trying to load data from MSSQL to DB2 database. Job is simple one to one mapping. commit and batch size at tDBoutput is 1000.
I am facing below issue while loading data to DB2:
Exception in component tDBOutput_1 (j_f_table_name_multithreading)
java.sql.SQLException: [jcc][t4][102][10040][4.25.13] Batch failure. The batch was submitted, but at least one exception occurred on an individual member of the batch.
Use getNextException() to retrieve the exceptions for specific batched elements. ERRORCODE=-4229, SQLSTATE=null
caused by: Error for batch element # 1: DB2 SQL Error: SQLCODE=-1476, SQLSTATE=40506, SQLERRMC=-289, DRIVER=4.25.13
at migration_prod_jobs.j_f_table_name_multithreading_0_1.j_f_table_name_multithreading.tDBInput_1Process(j_f_table_name_multithreading.java:7839)
at migration_prod_jobs.j_f_table_name_multithreading_0_1.j_f_table_name_multithreading.tJava_3Process(j_f_table_name_multithreading.java:12764)
at migration_prod_jobs.j_f_table_name_multithreading_0_1.j_f_table_name_multithreading$2.run(j_f_table_name_multithreading.java:14433)
Caused by: com.ibm.db2.jcc.am.SqlTransactionRollbackException: Error for batch element # 1: DB2 SQL Error: SQLCODE=-1476, SQLSTATE=40506, SQLERRMC=-289, DRIVER=4.25.13
at com.ibm.db2.jcc.am.b6.a(b6.java:797)
at com.ibm.db2.jcc.am.b6.a(b6.java:66)
at com.ibm.db2.jcc.am.b6.a(b6.java:140)
at com.ibm.db2.jcc.am.k3.c(k3.java:2824)
at com.ibm.db2.jcc.t4.ab.x(ab.java:1827)
we suspect that this issue occurred due to dead lock or timeout while execution batch updated at DB2. we have tried below configuration changes at DB2: DB2_AVOID_LOCK_ESCALATION=ON
Can you please help me to solve this issue.
attaching error log for your referece.
Thanks and regards,
Vinay T.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
What's DB2 version are you using?
This error could indicate a deadlock or timeout occurred while executing the batch updated. This suggests some database configuration needs to be tuned. Have you already checked the db2diag log to lead into the final error?
If the DB2 self tuning memory feature is enabled (which is the default for DB2), it is recommended to set the LOCKLIST and MAXLOCKS to AUTOMATIC
Best regards
Sabrina
