Unidata 8.2.1 - ODBC configuration changed - need to restore

Kevin,

Not an easy one - there are a number of files created by VSG on initial connection as well as new VOC entries and potential modification to data file dictionaries.
 

If you create a new/empty account with a nominal data file Icopy one of the DEMO account files)and connect with VSG you will see what defailts get created - they typically start with “__” if I recall correctly similar to __VIEWS__. In addition there are likely to be synonym VOC entries for mapped files and some new data-file-specific VOC entries created.

I’d be tempted to parallel restore a backup of the affected account at another location/name and start comparing VOC entries and file dictionaries a start. You could also try re-GRANTing permission to use to users from a SQL command prompt.

As a note - has anything changed on the domain that might have removed use privileges to either short or fully-qualified user names - including deletion of the user or change of UID/GiD who originally created the views and schemas (permissions are all inherited). When creating SQL/ODBC mapping I have always used  a specific user name with a specific UID and GID - which gets formally documented and reserved. 

Regards

JJ

Yeah that user ID thing was one of the biggest problems I was having with the VSG.  As to restoring, I found that the tables starting with SQL in the current directory had been removed - somehow.  SQLColumns, SQLTables, SQLSpecialColumns, and one other that I don’t remember at this time.  The DV_* dicts also were missing.  I brought all those back from a recent backup, including ___V___VIEW__ + ___SCHEMA__MAP__ + __SCHEMA__PROC__ and it seemed to work - eventually after a LOT of analyzing trace logs, with copious thanks to you for the assist.