Forum Discussion
Mirrored Lakehouse Table Unidentified
I have a Lakehouse that mirrors data from my Prod Lakehouse. Previously I have had no issue with the lakehouse on reading the data, this last week I started getting errors about mirrored tables "Unable to identify these objects as tables or views. To keep these objects in the lakehouse, move them to Files." I have tried to mvoe the tables to Files to try and reconvert them back to Tables but I get an erros "Unable to move all unidentified items to Files." My next move is to recreate the entire lakehouse and re-mirror the tables. I am trying to avoid this as I have multiple Power BI reports that are built off the mirrored lakehouse. Any suggestions on why I am getting this error?
Lakehouse error:
SQL Endpoint Table Error:
Hello JDay98
The issue with schema shortcuts is typically caused by:
- A corrupted or partially synchronised schema metadata file
- Modifications to the underlying Delta transaction log at the source
- Desynchronisation of shortcuts following schema evolution
- Inconsistent metadata within the mirrored lakehouse
Before addressing your mirrored lakehouse, please ensure the source is in good health.
Within your production lakehouse, confirm that /Tables exists and contains the *_delta_log:
Fabric shortcuts may have become outdated.
To refresh:
- Select the relevant schema shortcut
- Click Refresh
If the refresh is unsuccessful, it is likely due to metadata corruption in either the shortcut or the source.
From the mirrored lakehouse:
- Go to SQL Endpoint > Refresh
- Navigate to Tables view > Refresh
- If the problematic table displays a warning, select “Remove from SQL endpoint”
This action removes only the metadata and does not affect the actual data.
Hi JDay98 ,
I belive you are creating a shortcut from the prod lakehouse. If my understanding is correct. Please refresh the shortcuts. This should trigger to refresh the metadata for shortcut. If still the issue persists, please recreate the shortcuts. As we are only pointing our data and not actually creating any tables, recreating the shortcuts should not break any downstream componenets.
I hope this helps, lets me know if you face any issues.
4 Replies
Hello JDay98
The issue with schema shortcuts is typically caused by:
- A corrupted or partially synchronised schema metadata file
- Modifications to the underlying Delta transaction log at the source
- Desynchronisation of shortcuts following schema evolution
- Inconsistent metadata within the mirrored lakehouse
Before addressing your mirrored lakehouse, please ensure the source is in good health.
Within your production lakehouse, confirm that /Tables exists and contains the *_delta_log:
Fabric shortcuts may have become outdated.
To refresh:
- Select the relevant schema shortcut
- Click Refresh
If the refresh is unsuccessful, it is likely due to metadata corruption in either the shortcut or the source.
From the mirrored lakehouse:
- Go to SQL Endpoint > Refresh
- Navigate to Tables view > Refresh
- If the problematic table displays a warning, select “Remove from SQL endpoint”
This action removes only the metadata and does not affect the actual data.
Hi JDay98,
Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to deborshi_nag, for those inputs on this thread.Has your issue been resolved? If the response provided by the community member deborshi_nag, addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.
Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.
Thank you for using the Microsoft Community Forum.Hi JDay98,
Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.Thank you.
Hi JDay98 ,
I belive you are creating a shortcut from the prod lakehouse. If my understanding is correct. Please refresh the shortcuts. This should trigger to refresh the metadata for shortcut. If still the issue persists, please recreate the shortcuts. As we are only pointing our data and not actually creating any tables, recreating the shortcuts should not break any downstream componenets.
I hope this helps, lets me know if you face any issues.
