Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. IMPORTANT DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

ORA-12899: value too large for column -- TASKEXECUTIONHISTORY

Hi,
I am using context variables to distinguish between DEV, STAGE and PROD for the database connection string. When I run from the Talend Studio, it works fine while using Target Exec as remote server on DEV and STAGE. I wanted to use the Administration Center to schedule this task and run it on DEV, STAGE and PROD. I can Add a task, generate the job, deploy the job but when I run the job, I receive this error message. I know that the column ContextValues in the TASKEXECUTIONHISTORY table is very small compared to the context value string I have. I did a simple test to see if this was the issue by using a simple component to connect to a database and shortening my context variables to less then 255 bytes/characters and it works.
The following is the error message from the tdqserver_log.log from the administration Center on the Tomcat server
------------------------------------------------------------------------------------------------------------------
2011-05-13 12:35:55 ERROR JDBCExceptionReporter - ORA-12899: value too large for column "TALEND"."TASKEXECUTIONHISTORY"."CONTEXTVALUES" (actual: 416, maximum: 255)
-------------------------------------------------------------------------------------------------------------------

This is the table creation script for that table and most columns are limited to 255 characters. This is definitely going to be a problem moving forward since Clients might be using a number of context variables and they might cross the 255 character limit. The max for a varchar2 is 4000. I know I am not supposed to touch the Talend Administration Center schema tables, but would like to know if I can increase the size of the table column CONTEXTVALUES to something more then 255 char.
CREATE TABLE TASKEXECUTIONHISTORY
(
ID NUMBER(10) NOT NULL,
DTYPE VARCHAR2(255 CHAR) NOT NULL,
E_VERSION NUMBER(10) NOT NULL,
BASICSTATUS VARCHAR2(255 CHAR),
DETAILEDSTATUS VARCHAR2(255 CHAR),
TASKLABEL VARCHAR2(255 CHAR),
TASKDESCRIPTION VARCHAR2(255 CHAR),
PROJECTNAME VARCHAR2(255 CHAR),
TALENDJOBNAME VARCHAR2(255 CHAR),
TALENDJOBID VARCHAR2(255 CHAR),
TALENDJOBVERSION VARCHAR2(255 CHAR),
CONTEXTNAME VARCHAR2(255 CHAR),
VIRTUALSERVERNAME VARCHAR2(255 CHAR),
EXECUTIONSERVERNAME VARCHAR2(255 CHAR),
EXECUTIONSERVERHOST VARCHAR2(255 CHAR),
EXECUTIONSERVERCMDPORT NUMBER(10),
EXECUTIONSERVERFILEPORT NUMBER(10),
EXECUTI NUMBER(10),
APPLYCONTEXTTOCHILDREN NUMBER(1),
TRIGGEREDBY VARCHAR2(255 CHAR),
TRIGGERTYPE VARCHAR2(255 CHAR),
TRIGGERNAME VARCHAR2(255 CHAR),
TRIGGERDESCRIPTION VARCHAR2(255 CHAR),
TASKERRORSTACKTRACE CLOB,
IDQUARTZJOB NUMBER(10),
IDQUARTZTRIGGER NUMBER(10),
LASTJOBGENERATIONDATE TIMESTAMP(6),
JOBARCHIVEFILENAME VARCHAR2(255 CHAR),
FILETRIGGERFILEMASK VARCHAR2(255 CHAR),
FILETRIGGERFILENAME VARCHAR2(255 CHAR),
FILETRIGGERFOLDERPATH VARCHAR2(255 CHAR),
FILETRIGGERTRIGGEREDFILEPATH VARCHAR2(255 CHAR),
EXPECTEDTRIGGERINGDATE TIMESTAMP(6),
TASKSTARTDATE TIMESTAMP(6),
TASKENDDATE TIMESTAMP(6),
ADMINJOBSTARTDATE TIMESTAMP(6),
ADMINJOBENDDATE TIMESTAMP(6),
SERVERJOBSTARTDATE TIMESTAMP(6),
SERVERJOBENDDATE TIMESTAMP(6),
IDREMOTEJOB VARCHAR2(255 CHAR),
IDREMOTEJOBEXECUTION VARCHAR2(255 CHAR),
REQUESTID VARCHAR2(255 CHAR),
RESUMINGMODE NUMBER(1),
CONTEXTVALUES VARCHAR2(255 CHAR),
JVMVALUES VARCHAR2(255 CHAR),
PARENTTASKEXECID NUMBER(10),
PARENTPLANEXECID NUMBER(10),
ORIGINALLABEL VARCHAR2(255 CHAR),
CURRENTLABEL VARCHAR2(255 CHAR)
)
LOGGING
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;
Thank you,
Santhosh.
1 Reply
Anonymous
Not applicable
Author

Hi
A solution is available in 18248.
Best regards
Shong