Forum Discussion

QLc3GKkTqYwHUN's avatar
QLc3GKkTqYwHUN
New Member
1 year ago
Solved

DataSource.Error: ODBC: ERROR [40001]

How can I resolve this error? It happened suddenly a few days ago and only affects this one query; others are refreshing fine.

 

  • Hi QLc3GKkTqYwHUN,

     

    Thank you for reaching out to Microsoft Fabric Community.

     

    From the error message, it looks like the database is undergoing recovery or vacuuming, and the query was canceled because it attempted to access row versions that are no longer available.

    • Retry the query again, it might be a temporary issue due to background maintenance.
    • Check for any long running transactions, if any transaction is running too long, terminate it
    • Since the error is related to the vacuum process. check for vacuuming issues and when tables were last vacuumed. If a table has not vacuumed long time, run VACUUM ANALYZE manually
    • If the error persists, check logs to see if the database is undergoing recovery.

     

    If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

     

    Thanks and regards,

    Anjan Kumar Chippa

5 Replies

  • What's the data source?  Were they doing a restore while you were attempting your query?

  • v-achippa's avatar
    v-achippa
    Community Support

    Hi QLc3GKkTqYwHUN,

     

    Thank you for reaching out to Microsoft Fabric Community.

     

    From the error message, it looks like the database is undergoing recovery or vacuuming, and the query was canceled because it attempted to access row versions that are no longer available.

    • Retry the query again, it might be a temporary issue due to background maintenance.
    • Check for any long running transactions, if any transaction is running too long, terminate it
    • Since the error is related to the vacuum process. check for vacuuming issues and when tables were last vacuumed. If a table has not vacuumed long time, run VACUUM ANALYZE manually
    • If the error persists, check logs to see if the database is undergoing recovery.

     

    If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

     

    Thanks and regards,

    Anjan Kumar Chippa

    • v-achippa's avatar
      v-achippa
      Community Support

      Hi QLc3GKkTqYwHUN,

       

      As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.
      If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

       

      Thanks and regards,

      Anjan Kumar Chippa

      • v-achippa's avatar
        v-achippa
        Community Support

        Hi @QLc3GKkTqYwHUN,

         

        We wanted to kindly follow up to check if the solution I have provided for the issue worked.
        If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

         

        Thanks and regards,

        Anjan Kumar Chippa