Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 26 Jan 2009 @ 22:31:36 GMT


     
  <Prev Next>  
<<First
<Prev
Next> Last>>  


Subj:   Concurrent change conflict on database -- try
 
From:   nazy_gholizadeh

Has anyone encountered this error while running a Select query?

"Concurrent change conflict on database -- try again."


In the documentation it says:

3598 Concurrent change conflict on database --try again.

Explanation: During processing of the user's transaction, another user changed the database.

Generated By: ITB, RES, GEN and OPT modules.

For Whom: End User.

Remedy: Resubmit the transaction.


But I would like to find out what process caused this job to abend, and what the change conflict was.

Looking at the errors from DBQL, nothing jumps at me that might have caused this error. It does show this error message on the query that abended due to this error, but I cannot find any deadlock situation around that time on any tables used in the query.

Any thoughts on what to look for?


Thanks,

Nazy



     
  <Prev Next>  
<<First
<Prev
Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 27 Dec 2016