Resolution:
Description:
=========
Proxy Agent throws the following error if one of the message (Request/Response) properties has a value that is more than 255 characters in length.

database error detected ....  indexing stopped for 10 seconds. stack: java.lang.RuntimeException: unable to insert message into the database: database update failed: SQLState:72000, ErrorCode:12899, Message:ORA-12899: value too large for column "<Schema Name>"."AMBPT_STRING_PROPERTIES"."<Column Name>"
stack:java.sql.SQLException: ORA-12899: value too large for column  "<Schema Name>"."AMBPT_STRING_PROPERTIES"."<Column Name>"

Environment:
===========
TIBCO ActiveMatrix® Policy Agent 3.x connecting to a supported version of Oracle.

Symptoms:
=========
This error prevents Proxy Agent from moving the log records to the database. As a result, the log records will not be accessible through the Policy Manager console. Also, the log bundles will start accumulating to disk.

Resolution:
=========
The solution is to increase the column size in database as shown below.

1). If the logging database details have been specified at the Proxy/Plugin Agent level, shut down all the Proxy Agents/Service Grid Nodes. If you have specified the logging database details at the Container Service level, shut down the Policy Manager and all Proxy Agents/Service Grid Nodes.

2). Execute the following statement against the logging database:

alter table AmbPt_string_properties modify (
   val1  varchar(1000),
   val2  varchar(1000),
   val3  varchar(1000),
   val4  varchar(1000),
   val5  varchar(1000));

3). Delete the files under the MessageHistory directory of the Proxy Agents/Plugin Agents. You will lose any log records that are not yet moved to the database.

4). Start the components that you halted in Step 1.

Resolving the following error in the TIBCO ActiveMatrix® Policy Agent log file - java.sql.SQLException: ORA-12899: value too large for column ";Schema Name;"."AMBPT_STRING_PROPERTIES".";Column Name;"