Sqlcode -444 Error; Sqlcode -289 Error; Sqlcode -1225 Error; Sql 0964C Transaction Log Full Error On The Bcgmas Database - IBM E02HRLL-G - WebSphere Partner Gateway Express Administration Manual

Administration guide
Table of Contents

Advertisement

v "SQL 0964C Transaction log full error on the BCGMAS database"

SQLCODE -444 error

If you encounter SQLCODE -444 error messages when starting any of the
WebSphere Partner Gateway components (bcgconsole, bcgreceiver, bcgdocmgr),
you should increase the value of the DB2 Database Manager SHEAPTHRES
parameter. This parameter should be at least two times larger than the highest
sortheap value defined for any database within the DB2 instance. Consult your
database administrator or see your DB2 administrator's guide before changing this
setting. A sample command is given below:
db2 UPDATE DBM CFG USING SHEAPTHRES xxxxx IMMEDIATE
If the SQLCODE -444 persists after changing the value of SHEAPTHRES, you can
decrease the values of STMTHEAP and APPLHEAPSZ for your WebSphere Partner
Gateway database. A sample command is given below:
db2 UPDATE DB CFG FOR <dbname> USING STMTHEAP xxxxx
db2 UPDATE DB CFG FOR <dbname> USING APPLHEAPSZ xxxxx
Consult your DBA or see your DB2 administrator's guide before changing any
settings.
It can also be found in the <DB2Home>\SQLLIB\bin\db2diag.log file.

SQLCODE -289 error

A DB2 error code -289 indicates that the database has run out of space on the file
system. Check with the database administrator about adding additional capacity
on the database sever.
Alternatively WebSphere Partner Gateway data can be archived to a different
storage location to free up disk space.

SQLCODE -1225 error

You can receive the SQLCODE -1225 error followed by a stack trace in the
WebSphere Partner Gateway server logs when DB2 resources are running low on
the system. The following is an example of the SQLCODE error.
java.sql.SQLException: com.ibm.db2.jcc.c.SqlException:
DB2 SQL error: SQLCODE: -1225, SQLSTATE: 57049, SQLERRMC: null
This error is typically occurs when transaction rates are high (large number of
documents per second) and DB2 is not able to sustain this rate. The database
administrator might want to monitor and tune the database to accommodate these
high transaction periods. To improve the performance of the database logging, you
can tune the following DB2 parameters:
v LOGPRIMARY
v LOGSECOND
v LOGFILESIZ
SQL 0964C Transaction log full error on the BCGMAS
database
WebSphere Partner Gateway creates the BCGMAS database with the following
default configuration values:
162
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide

Advertisement

Table of Contents
loading

This manual is also suitable for:

Websphere partner gateway

Table of Contents