Error: "ORA-12899: value too large for column" seen in SPM engine logs.
Article ID: KB0092497
Updated On:
| Products | Versions |
|---|---|
| TIBCO Service Performance Manager | - |
| Not Applicable | - |
Description
Description:
Depending on BW project structure, users may have large activity paths. In database, the maximum size for this column under METRIC_PROCEXEFLOW table ("METRIC_PROCEXEFLOW"."ACTIVITYPATH") is 255. Records will fail to be inserted into the table if the activity path is longer than 255 characters.
Symptoms:
Cause:
"METRIC_PROCEXEFLOW"."ACTIVITYPATH" column size in database is 255 while actual BW activity path is longer.
Depending on BW project structure, users may have large activity paths. In database, the maximum size for this column under METRIC_PROCEXEFLOW table ("METRIC_PROCEXEFLOW"."ACTIVITYPATH") is 255. Records will fail to be inserted into the table if the activity path is longer than 255 characters.
Symptoms:
A user will see following error in the SPM engine logs:
18 Jun 2015 09:40:09,148 IST +0530 ERROR metric-compute-thread-5 [rta.services.persistence] - SQLException encountered while applying transaction
java.sql.SQLException: ORA-12899: value too large for column "ADMIN"."METRIC_PROCEXEFLOW"."ACTIVITYPATH" (actual: 346, maximum: 255)
Cause:
"METRIC_PROCEXEFLOW"."ACTIVITYPATH" column size in database is 255 while actual BW activity path is longer.
Issue/Introduction
Error: "ORA-12899: value too large for column" seen in SPM engine logs.
Resolution
You may alter the table and increase the size of that column using the following command after stopping the SPM engine.
Alter table METRIC_PROCEXEFLOW modify ACTIVITYPATH varchar2(1000);
Additional Information
Feedback
Yes
No
Powered by
