• It has been observed in the current release of FSW 6.0.0 that specifically for DB2 database users, the "CONTENT" column for "RTGOV_ACTIVITIES" and "DESCRIPTION" column for "RTGOV_SITUATIONS" tables of RTGov are limited to CLOB(10240) values only. This value for CLOB columns are far too short for some message's content.

As the corresponding DDL queries for these tables can be found in the "jboss-eap-6.1/standalone/deployments/overlord-rtgov/overlord-rtgov-epn.war/WEB-INF/classes/META-INF/sql/overlord-rtgov-epn.overlord-rtgov-epn.DB2Dialect.sql" script.
~~~
...
call execute_if_not_exists('create table RTGOV_ACTIVITIES (
activityType varchar(31) not null,
unitId varchar(255) not null,
unitIndex integer not null,
principal varchar(255),
tstamp bigint,
customType varchar(255),
logLevel integer,
message varchar(255),
instanceId varchar(255),
processType varchar(255),
status integer,
version varchar(255),
variableName varchar(255),
variableType varchar(255),
variableValue varchar(255),
content clob(10240),
messageType varchar(255),
destination varchar(255),
fault varchar(255),
interface varchar(255),
operation varchar(255),
serviceType varchar(255),
replyToId varchar(255),
primary key (unitId, unitIndex)
)');

...
call execute_if_not_exists('create table RTGOV_SITUATIONS (
id varchar(255) not null,
description clob(10240),
severity integer,
subject varchar(255),
tstamp bigint,
situationType varchar(255),
primary key (id)
)');

...
~~~

I have checked the same DDL queries for other databases like Oracle ("overlord-rtgov-epn.overlord-rtgov-epn.Oracle10gDialect.sql") and they are set to it's maximum limit.
~~~
...
begin execute_if_not_exists('create table RTGOV_ACTIVITIES (
activityType varchar2(31 char) not null,
unitId varchar2(255 char) not null,
unitIndex number(10,0) not null,
principal varchar2(255 char),
tstamp number(19,0),
customType varchar2(255 char),
logLevel number(10,0),
message varchar2(255 char),
instanceId varchar2(255 char),
processType varchar2(255 char),
status number(10,0),
version varchar2(255 char),
variableName varchar2(255 char),
variableType varchar2(255 char),
variableValue varchar2(255 char),
content clob,
messageType varchar2(255 char),
destination varchar2(255 char),
fault varchar2(255 char),
interface varchar2(255 char),
operation varchar2(255 char),
serviceType varchar2(255 char),
replyToId varchar2(255 char),
primary key (unitId, unitIndex)
)'); end;;

...
begin execute_if_not_exists('create table RTGOV_SITUATIONS (
id varchar2(255 char) not null,
description clob,
severity number(10,0),
subject varchar2(255 char),
tstamp number(19,0),
situationType varchar2(255 char),
primary key (id)
)'); end;;

...
~~~

Hence, requesting to change the values for such CLOB columns for the respective tables in their DB2 specific DDL scripts, at par to the other databases' script. This should help DB2 based users to also utilize these columns ("CONTENT" column for "RTGOV_ACTIVITIES" and "DESCRIPTION" column for "RTGOV_SITUATIONS" tables) as per their business requirements.

Version-Release number of selected component (if applicable):

• RTGov 1.0.1

How reproducible:

• Always