SQL0803N One or more values in the INSERT statement, UPDATE

          having duplicate rows for those columns. 

Explanation:

The INSERT or UPDATE object table "

          a deadlock or timeout.  Reason code "". 

Explanation:

The current unit of work was involved in an unresolved contention

for use of an object and had to be rolled back. 

 The reason codes are as follows:

 2 transaction rolled back due to deadlock. 

 68 transaction rolled back due to lock timeout. 

 72 transaction rolled back due to an error concerning a DB2 Data

Links Manager involved in the transaction. 

Note: The changes associated with the unit of work must be  

       entered again. 

 The application is rolled back to the previous COMMIT. 

User Response:

To help avoid deadlock or lock timeout, issue frequent COMMIT

operations, if possible, for a long-running application, or for

an application likely to encounter a deadlock. 

 Federated system users: the deadlock can occur at the federated

server or at the data source.  There is no mechanism to detect

deadlocks that span data sources and potentially the federated

system.  It is possible to identify the data source failing the

request (refer to the problem determination guide to determine

which data source is failing to process the SQL statement). 

 Deadlocks are often normal or expected while processing certain

combinations of SQL statements.  It is recommended that you

design applications to avoid deadlocks to the extent possible. 

 sqlcode :  -911

 sqlstate :  40001 

3. SQL0964

SQL0964C The transaction log for the database is full. 

Explanation:

All space in the transaction log is being used. 

 If a circular log with secondary log files is being used, an

attempt has been made to allocate and use them.  When the file

system has no more space, secondary logs cannot be used. 

 If an archive log is used, then the file system has not provided

space to contain a new log file. 

 The statement cannot be processed. 

User Response:

Execute a COMMIT or ROLLBACK on receipt of this message (SQLCODE)

or retry the operation. 

 If the database is being updated by concurrent applications,

retry the operation.  Log space may be freed up when another

application finishes a transaction. 

 Issue more frequent commit operations.  If your transactions are

not committed, log space may be freed up when the transactions

are committed.  When designing an application, consider when to

commit the update transactions to prevent a log full condition. 

 If deadlocks are occurring, check for them more frequently. 

This can be done by decreasing the database configuration

parameter DLCHKTIME.  This will cause deadlocks to be detected

and resolved sooner (by ROLLBACK) which will then free log

space. 

 If the condition occurs often, increase the database

configuration parameter to allow a larger log file.  A larger log

file requires more space but reduces the need for applications to

retry the operation. 

 If installing the sample database, drop it and install the

sample database again. 

 sqlcode :  -964

 sqlstate :  57011