Hi Dan,
Thanks for contacting us. The root of the problem is that the table appears to have been created with a mydb_import() call (or perhaps from the crossmatch web tool) that tried to import a table from your VOSpace storage which doesn't exist (vos://trans/G318.5+000IFx_Mosaic_Mom0_comp.csv). In fact, other similar tables based on that file do show up in your mydb, but all have zero rows. There is also an issue with table names being mixed upper-lower case and invalid characters such as '-' or '+' that may prevent you from seeing the table at all (or by the name you think you've used).
There doesn't appear to be any way to recover the file since it doesn't appear in any of our backups. Requests to the Storage Manager for that file (presumably from the mydb_import()) also show up as failing, so it may not have existed at all. At this point, all I can recommend is that you try to upload the file to vospace once again and retry the imports. I can manually delete the existing files from your MyDB beforehand if you would like.
Regards,
-Mike