Unable to view UniData ODBC tables after migration

Hello, 

I am migrating our production application (Prelude) from a UNIX to Linux environment. Currently, I am working on moving the U2 ODBC database. UniData is installed and working on the system and presents correctly in Prelude, however the ODBC database is having some issues. When I attempt to connect using U2 ODBC drivers, I can only interact with 5 out of the 40 tables present. The account used to manage these tables/subtables/views has owner permissions on the db and is part of the same groups as it was on Unix. I am not sure where to continue my troubleshooting efforts here, but direction/suggestions are greatly appreciated.

Hi Phaelen,

I would suggest raising a call with Epicor as a starting point and they can contact us in turn if needed. In order to support the same priviliges you have in SQL with UniData, there is an internal file in UniData used to maintain those relationships. When a table was first mapped or a view first created, the name and UID of the creator  / owner is mapped, if you delete a user or move to a new machine with different UIDs or usernames then this does cause a problem and some challenges on correcting the linkages in the internal file. You can end up in a situation that without logging in as the root user, you can now longer maintain the views and tables.

If you login as the 'root' user do you still have the problem or can you see everything.

Regards,

Hi Jonathan,

That makes a lot of sense. I just attempted a connection test using root and received:

[Rocket U2][U2ODBC][0302086]Error ID: 76  Severity: ERROR  Facility: DBCAPERR - [U2][SQL Client][UNIDATA]Login Failed.

The account setup to access the ODBC db is able to pass this same connection test. Ownership of the files was given to the designated account upon migration.

Is there a standard name for the file that controls SQL access in Unidata?
------------------------------
Phaelen Stuart-Berg
IT Systems Manager
Rocket Forum Shared Account
------------------------------

Phaelen,

Not being able to login as root may be a restriction in Linux, all our Linux machines come with this disabled as standard. Can you login as root via telent ?

In terms of the ownership of the files, I am not talking about the ownership or permissions at a Unix level. Better to work via a support call with Epicor on this, as the forum is not really the place that I want to openly discuss these security files.

Regards,

Jonathan,

Yes I can login as root via telnet. Checking the UID of the account used to create the tables/views, they are different between machines so I am going to start there.

That makes sense as well. I have an active support case open with Epicor.

Hi Phaelen,

This may the problem that David from Epicor has contacted me about. So I am looking into this. Please note the file keeps tracks of the security is an internal UniData file and we don't publish the structure of it. So I am not sure how looking at the UIDs will help. They are tracked inside an internal UniData file, changing values at the OS level in relation to the files themselves is not going to help.

Regards,