DB2 Error - SQL1476N

kksr · Post by **kksr** » Mon Apr 06, 2009 12:10 am

Hi All,

For one of my job Target Db is DB2. for this i am using DB2 stage and i am using lookup table as target table(DB2 stage)

target table having receord count is 412057
I am running this job from 25 days, job ran successfully
today it got failed with Error like:
db2User,0: ERROR during execution of DB2-CLI requests: SQL_ERROR; SQLSTATE = 40506;
NativeErrorCode = -1476; Message = [IBM][CLI Driver][DB2/AIX64] SQL1476N
The current transaction was rolled back because of error "-911". SQLSTATE=40506.

Then I used commit intervals as 500 also
again got failed,
Please help me on this..

ray.wurlod · Post by **ray.wurlod** » Mon Apr 06, 2009 7:24 am

Ask your DB2 DBA to help, or refer to the DB2 errors and messages manual. This error is being generated by DB2.

richiejeffery · Post by **richiejeffery** » Fri Jul 09, 2010 3:42 pm

I found this on another site that was helpful in explaining this issue a little better.

There is Advanced tab on output page which you are looking (buffering
setting). But also there is Advanced tab in stage page.
You should check that page.

DB2 deadlock occurs when running in parallel mode when the access path is
not using appropriate index to update.
To avoid the deadlock in this mode, you should change to sequential when
updating or change the commit count to 1.
If the table has unique index and that can be used for the SQL for
updating, then you should check the access path set for that table. (DBA
role. )

Best Regards,
Shin Takakura (Original Poster)

For myself, I resolved this problem by creating database indexes on my update keys. Worked like a charm!

Hope that helps,
Rich