Hi Kumaril_02,
How are you doing today?, As per my understanding, It looks like the error you're getting—saying the table with a long ID doesn’t exist—is probably happening because Databricks is trying to reference a table using its internal ID rather than its actual name. This can happen if the table was dropped, renamed, or if there’s some stale metadata from a previous run. Since you’ve already set up all the necessary storage permissions and granted the right privileges on the catalog and schema, the issue is likely not with access but with how the table is being referenced. Try running REFRESH CATALOG and REFRESH SCHEMA to clear any old references, and make sure you’re using the correct table name like catalog.schema.table_name. Also, if the table used to exist and was deleted, try creating it again with a new name just to rule out any metadata issues. Let me know if you want help checking the exact command you’re using—happy to walk through it with you!
Regards,
Brahma