You can translate the question and the replies:

Cache fetch error

Hi Team, Denodo 6.0 source DB : SQL Server cache DB : SQL Server cache type : Full Cache , Never Expire normal query : runs successfully, 10230397 rows cache query : when loading cache : error Error: [BASE] [ERROR] There was an error during a batch insertion: Data truncation [JDBC WRAPPER] [STOPPED] Please suggest. Thanks.
user
02-12-2019 01:37:39 -0500
code

4 Answers

Hi, This error most likely means that there has been some changes in the data source after the cache was created, most probably some columns have been altered to fit bigger types. This made the cache metadata inconsistent with the source table metadata. If this was the problem what I would do to try fixing it would be to use the [Source Refresh](https://community.denodo.com/docs/html/browse/6.0/vdp/administration/creating_views/importing_data_sources_and_creating_base_views/source_refresh) to propagate any metadata changes to the VDP Server and thus to the cache table. Hope this helps!
Denodo Team
02-12-2019 17:53:00 -0500
code
Hi Team, This is a new base view. It was not cached previously. Cached for first time. Even I created (again) new Base View, (note all fields are there in Base view which are in underlying table). Still same error. Thanks.
user
04-12-2019 02:55:28 -0500
Hi, What I would do to try to troubleshoot this issue is to go to the data source and compare the original table to the cache table in terms of metadata. I would find the cache table on the SQL Server cache. Cache tables have a name starting with ‘C_’ followed by the view name and a control number. There I would expect to find a column with a type that causes trouble when trying to store data from the original table of that same source. Then, to fix this I would go back to Denodo and [change the type](https://community.denodo.com/docs/html/browse/6.0/vdp/administration/creating_views/importing_data_sources_and_creating_base_views/viewing_the_schema_of_a_base_view#viewing-the-schema-of-a-base-view), by clicking on the pencil icon, in the appropriate field to something suitable in terms of size. Say varchar(10) to varchar(20). This change would then propagate to the cache and should fix a problem of this kind Hope this helps!
Denodo Team
11-12-2019 12:01:19 -0500
code
Thanks, will check.
user
12-12-2019 00:34:47 -0500
You must sign in to add an answer. If you do not have an account, you can register here