topic Re: Refresh streaming table error in Data Engineering

Refresh streaming table error

Anandhi-Sekaran — Tue, 17 Mar 2026 11:46:10 GMT

Refresh streaming table sql succeeds for the first time.

The subsequent refresh statements fails with TABLE_OR_VIEW_NOT_FOUND error.

The streaming table is still available in the same catalog and schema

Re: Refresh streaming table error

Ashwin_DSA — Tue, 17 Mar 2026 16:02:38 GMT

I would need more context to help you. Please share the exact SQL you’re using, with any catalog, schema, or table names anonymised if necessary, so I can identify what might be affecting you.

As a starter, just make sure you’re using all three parts (Catalog, Schema & Table) every time rather than just using the table name alone.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.

Re: Refresh streaming table error

Anandhi-Sekaran — Thu, 19 Mar 2026 07:42:06 GMT

Here is the query i use

REFRESH STREAMING TABLE `cxxxxx`.`tgt_dev`.`ldp_csv`

It is successful when i execute the first time.

If i run the same query after 30 min, it throws error TABLE_OR_VIEW_NOT_FOUND

Re: Refresh streaming table error

Ashwin_DSA — Thu, 19 Mar 2026 09:04:02 GMT

Hi @Anandhi-Sekaran,

Thanks for clarifying. I'm wondering if another script, pipeline or a different user dropped the table after you created it. or, maybe even created a normal table replacing the existing streaming table? Here are some options for you to debug.

Can you run the below and see if it returns anything? If it does, is it showing the type as streaming?

DESCRIBE TABLE EXTENDED `cxxxxx`.`tgt_dev`.`ldp_csv` AS JSON;

Is it also possible that you are running it from a different workspace? In the same warehouse where your query has failed, can you try the following and see what you find?

VALUES current_catalog(), current_schema(); SELECT 1 FROM `cxxxxx`.`tgt_dev`.`ldp_csv` LIMIT 1; SHOW TABLES IN `cxxxxx`.`tgt_dev` LIKE 'ldp_csv';

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.