Friday, 15 July 2011

db2 - SQL0903N COMMIT statement failed, transaction rolled back in db2luw -


I am working on DB2 ATS jobs. That's what I've tried made a process P1 on database D1. This process will update table T1 on database D1. I can update Table T1 from Process P1 on direct call. And now I have created a table T2 on database d2. From Database D1, I am trying to update this table T2. It's also working fine too. From database d1, I have two tables t1 & amp; T2

Now I tried to do this with ATS jobs. I can submit a job to call Process P1 to update table T1 on database D1. The job is working fine; Able to see up-to-date records.

Tried to submit a job from D1, which will update table T2 on database D2. Job is running fine without any errors, but the table is not updating

Below is my process & amp; Log some having what I can tell I remember here:

  Create or change process p1 VARCHAR (32,672)) in D_JUMP12 (Text: initiated jobno number; Immediately executed text; COMMIT; Finally p1  

This is how I'm calling process:

  DBMS_JOB.SUBMIT (Say, 'says D_JUMP12 (' 'updated sample. Reg .CABS SET FIRSTNAME = reg_f_fixed_char_repos (first name) '' '), tap);  

This is my log:

  2015-03-17-18.37.10.360000 + 330 E110713390F554 Level: Error PID: 2460 TID: 444 PROC: db2fmp64 .exe example: DB2 node: 000 dB: test1 APPID: * LOCAL.DB2.150317130717 HOSTNAME: Mango -04 EDUID: 444 function: DB2 UDB, administrative task scheduler, AtsConnection :: committed, investigated 900 message: ECF = 0x82BA00E1 = -2101739295 Data # 1: String, 124 bytes [IBM] [CLI Driver] [DB2 / NT64] SQL 0903 N Commit Statement failed, the transaction rolled back. Reason code: "2" SQLSTATE = 40504  
  2015-03-17-18.37.10.364000 + 330 I110713946F425 Level: Error PID: 2460 TID: 444 PROC: db2fmp64.exe example: DB2 node 000 dB: test1 APPID: * LOCAL.DB2.150317130717 HOSTNAME: Mango -04 EDUID: 444 function: DB2 UDB, administrative task scheduler, AtsTask :: run probe 1300 message: ECF = 0x82BA00E1 = -210173 9 2 9 5 figures # 1: Codepath , 8 bytes 4  

Please tell me what I'm missing


No comments:

Post a Comment