Unidata 8.2.1 Command line tools for updating ODBC configuration

Kevin,

You can save the command-line SQL used by VSG from the tool and build intoi a PAragraph.PROC or program to create schemas, views and permissions from the command line if tht helps?
 

I would not use CONVERT,SQL myself as it does not give fine control.

Regards

JJ

That would be lovely, but… how do I know what command line SQL is being executed by VSG?

Interesting, thank you!!

Any idea what this means?  It comes up when I click on Subtables.

Kevin,

These might help:

• https://my.rocketsoftware.com/RocketCommunity/s/article/VSG-Error-Died-in-UCI-SQLConnect-with-SQLSTATE-IM985-Native-error-81002-against-Windows-UniData-7-3-with-non-default-UniData-home-setting-1478610684645
• https://my.rocketsoftware.com/RocketCommunity/s/article/ERROR-Died-in-UCI-SQLExecDirect-with-SQLSTATE-IM985-Native-error-80001-1478610531870

I’d start with the uci.config and ud_database files.

Regards

It’s useful to be able to setup a new ud_database entry for testing.  Still doesn’t give me much in the way of answers as to why VSG is not working, but it definitely helps declutter the logs in the Unidata tmp directory.

My uci.config is fine.  It says UNIDATA and udserver where it should.

EUREKA.  Found the problem.  The permissions on this file were set before the last conversion, like a dozen years ago.  The Linux user IDs reflected in the privilege file no longer aligned with any valid user. I updated the privilege file to align with the Linux IDs and I am, as they say, back in business. 

Thanks for the help!

Kevin,

That’s more common than you might think - and a reason I ALWAYS used a site-specific functional user name, high UID and specific GID when setting up ODBC and documented it - boldly - in my handovers along with a PAragraph that prompted and then dropped all views and schemas and then recreated them along with assigning group-based permissions - both physical and documented in detail..

I once wrote a utility to verify the views, schemas, users and privileges and report/fix any mismatch as it just kept on coming up and on large systems it was not feasible to d this manually.if the original SQL was not available (it rarely (if ever - was).. It’s useful to have such a program in your toolkit and it;s not difficult to work out the file layouts. On one particular customer site I was regularly back a couple of times a year fixing their schemas, views  and permissions.

ADDED: Changing FQDN on a domain can have a similar effect, even if the short name remains the same.

Regards