Database error messages

The server.log file can contain error messages that relate to databases, such as DB2®, Oracle, and SQL Server.

DB2 SQL error example

Log Type: Exception Header

WARN/ERROR DB2 SQL Error: SQLCODE=### SQLSTATE=#####

Resolution area

DB2database

Issue

An SQL exception was encountered. The value of SQLCODE is based on the cause of the exception.

Suggested action

Examine the message in the server.log and find the line that starts with SQLCODE. To determine the cause, look up the SQLCODE in the online documentation for your DB2 version. The issues can be varied, from being out of space to invalid SQL.

Example 1

This code indicates that the database has run out of space in the file system:

2014-07-02 21:07:15,498 ERROR 
[com.tririga.architecture.workflow.dataaccess.
WFTemplateDAO](http-0.0.0.0-8001-4) 
com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException: DB2 SQL Error: 
SQLCODE=-289 SQLSTATE= 57011 

Search for SQLCODE=-289 SQLSTATE=57011

The DB2 error code -289 indicates that the database has run out of space on the file system.

Example 2

In this example, the S_POLINE business object and its staging table do not exist.

2014-07-02 12:14:55,759 ERROR
[com.tririga.platform.admin.dataaccess.
DBScriptRunnerDAOImpl](http-0.0.0.0-8001-3) 
com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-204, 
SQLSTATE=42704, SQLERRMC=TRIDATA.S_POLINE, DRIVER=4.16.24 
com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-204, 
SQLSTATE=42704, SQLERRMC=TRIDATA.S_POLINE, DRIVER=4.16.24  

Search for SQLCODE=-204 SQLSTATE=42704 
Object does not exist.