Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

error while enable paralization

Hi,

I have a job hat usually works fine, I have tried to active the option "Enable paralization"  with Number of parallel executions set as 2, but it gives me an error. I have tried this option with other jobs and it works well but with this one every time I try to execute after 10-20 minutes executing says: 

 

09:33:18|20200113092212_DgBf3|20200113092212_DgBf3|20200113092212_DgBf3|39373|P_CORPOWARE|LOAD_FACT_CDM_PROCESO_DIARIO_IDEMP|_s7oLAH_TEeaX6rPasE3pZg|3.1|Default||end|failure|666095
Exception in component tAsyncIn_tPostgresqlOutput_1 (LOAD_FACT_CDM_PROCESO_DIARIO_IDEMP)
java.lang.RuntimeException: Unparseable date: "Fri Jan 10 00:00:00 CET 2020"
at routines.system.ParserUtils.parseTo_Date(ParserUtils.java:321)
at p_corpoware.load_fact_cdm_proceso_diario_idemp_3_1.LOAD_FACT_CDM_PROCESO_DIARIO_IDEMP$1tAsyncIn_tPostgresqlOutput_1_ParallelThread.run(LOAD_F ACT_CDM_PROCESO_DIARIO_IDEMP.java:41604)
 
Any ideas why this happens?
Labels (3)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

Hi,

 

    The error is saying - Unparseable date: "Fri Jan 10 00:00:00 CET 2020"

 

     Could you please verify the date format of the column and see whether it matches your input data?

 

Warm Regards,
Nikhil Thampi

Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved

View solution in original post

3 Replies
Anonymous
Not applicable
Author

Hi,

 

    The error is saying - Unparseable date: "Fri Jan 10 00:00:00 CET 2020"

 

     Could you please verify the date format of the column and see whether it matches your input data?

 

Warm Regards,
Nikhil Thampi

Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved

Anonymous
Not applicable
Author

Thanks for your reply.

I have not check this out because it did work when the parallelization was not activate, I am going to look the date fields and see if it fix the error.

Anonymous
Not applicable
Author

Thanks a lot, after checking all the dates fields I saw that there are two who do not have the right length/precission. I wonder why it was working when the parallelization was off. Maybe this option activate the "die on error" option.