You can translate the question and the replies:

Denodo Cache job error

Team, Executing a cache job to replicate data from Oracle to Redshift using the bulk data load API option for Amazon Redshift. Most of the tables are loading but couple of them are failing without much error details. 25276858 [Full_cache_u_fixture_187 {"XXX"} (LABS).pool-11-thread-6] ERROR 2022-11-28T18:51:03.297 com.denodo.scheduler.core.job.executor.AbstractDatabaseExtractionJobExecutor [] - com.denodo.scheduler.core.commons.exceptions.CacheException: ERROR: Load into table 'c_u_tableaaaa' failed. Check 'stl_load_errors' system table for details. But there is no entries in the STL load errors table. Is there a way to set the log level to trace for additional information. If yes, what is the category that we should use in the logcontroller method?
Cache scheduler job
user
28-11-2022 19:05:35 -0500
code

1 Answer

Hi, To get detailed information about the error while executing a job in Scheduler, I would set the **“com.denodo.scheduler”** property to **“trace”** by performing the below steps: * Stop the Scheduler server. * Change the “com.denodo.scheduler” property to “trace” like below by navigating to the “<DENODO_HOME>/conf/scheduler/log4j2.xml”: `<Logger name="com.denodo.scheduler" level="TRACE" />` * Start the Scheduler server. Note: After receiving the additional information about the error I would revert the above logger level back to **“ERROR”** to avoid the verbose logging which could increase the log file size leading to storage issues. Hope this helps!
Denodo Team
29-11-2022 08:07:57 -0500
code
You must sign in to add an answer. If you do not have an account, you can register here