You can translate the question and the replies:

Denodo Cache refresh gets stuck when a SELECT is already being executed on the VDB

Hello, We have a VDB with cache db configured on Azure PostgreSQL v11. Assume a scenario when a SELECT is already running on Denodo VDB, accessing data from the configured cache. Now, if the Cache refresh job starts, at a set time, through Denodo Scheduler while this SELECT is running then the cache refresh job gets stuck and does not progress at all. We end up killing either set of these queries to resolve this. This method is not sustainable. Has this been observed before? What could be the potential issue and appropriate solution to handle it? Appreciate a quicker response.
30-05-2023 02:00:00 -0400

1 Answer

Hi, This is not normal behavior of the Cache Engine on Denodo and need further investigation by looking at the related logs, if you are a valid support account user you can open a new case in the [Denodo Support Site](, so the Denodo team can help you. Hope this helps!
Denodo Team
30-05-2023 03:13:57 -0400
You must sign in to add an answer. If you do not have an account, you can register here