Forum Discussion
Cannot Remove Invalid Table "_delta_log._commits" — SQL Sync Blocked
Hello,
I'm experiencing a persistent issue in Microsoft Fabric Lakehouse.
Lakehouse: Silver_Lakehouse
Issue: SQL Sync fails due to a phantom table _delta_log._commits.
Error Message:
Delta table 'Tables_delta_log_commits_delta_log' not found.
Table: _delta_log._commits
Error code: DeltaTableNotFound
What I’ve tried:
- There is no such folder in /Tables/ or /Tables/_delta_log/
- SHOW TABLES does not list _delta_log._commits
- I cannot drop or overwrite it due to invalid table name:
AnalysisException: Invalid table name silver_lakehouse._delta_log._commits
- It appears to be residual metadata from an interrupted write operation
Thanks,
Anton
Hi Antongig
Somewhere you deleted the transaction log file or data is corrupted due to _delta_log. For that, you need to delete the whole table ( single table ) and recreate the table using Python or scala commands which ever you think is relevant.
Also, Which database are you using as a source. I mean to say Azure SQL. SQL Server...etc.
15 Replies
Hi Bhavesh, thanks for replying!
I use Silver_Lakehouse as part of a production data pipeline where:
Tables are copied from Bronze to Silver using Spark notebooks and pipelines
SQL sync is required for warehouse access and reporting
Several downstream reports and jobs depend on these tables
The issue is that Fabric tries to sync a non-existent table _delta_log._commits, likely due to a failed write or interrupted notebook cell.
I’ve tried:Dropping the table via Spark SQL (DROP TABLE)
Deleting folders via file paths
Recreating and overwriting the table
Listing all tables (it doesn't appear)
Nothing worked. Now SQL sync always fails.
I cannot delete the Lakehouse easily because many pipelines and references are linked to it by name.Do you have any suggestion for clearing this ghost table or triggering a hard SQL sync refresh?
Hi Antongig
Somewhere you deleted the transaction log file or data is corrupted due to _delta_log. For that, you need to delete the whole table ( single table ) and recreate the table using Python or scala commands which ever you think is relevant.
Also, Which database are you using as a source. I mean to say Azure SQL. SQL Server...etc.
Apparently, Microsoft fixed the problem by enabling me to see the _delta_log table and to delete it. It took 2 minutes to resolve this issure. After all it was a bug in fabric.
Thank you for your help
Hi Antongig ,
Thank you for the update.
