B
Betty Hardin
Guest
Adriano - No - Option 8 does not show the remote user name. George - YES - it does. I believe that I've found the answer here: knowledgebase.progress.com/.../P14172 "When NO database security is set, then Progress uses the O/S userid. As soon as database security is initialized, the mode is changed and we use the entries in the _user table. So, if a blank userid is allowed to be used to access the database, a blank userid is shown." Have verified that to be true by removing 'sysprogress' from _user. Sysprogess was added to _user to enable ODBC connections after the failed dump / load. Using a copy of the database I am working through this: knowledgebase.progress.com/.../20143 I can see the username who ran the dump / load is now in sysdbauth - with dba and resource permissions. I also see sysprogess there. I understand that sysprogress is the default dba and that the dump / load effectively disabled that making the new user the default dba. Using that 'new' dba I can see data in tables via ODBC. The thing that confuses me is that the ODBC is setup to connect as user sc with password sc... and 'sc' doesn't exist anywhere that I can see. The people who setup that ODBC connection don't remember why they used 'sc'. I believe that may have come from old document on a v8 installation; this is Syteline v6.03 on Progress v10.2B - migrated recently from Progress v8.3E. I have attempted to add 'sc' and set permissions for that user using these commands: create user 'sc','sc' grant dba to 'sc' grant resource to 'sc' After doing that I see that 'sc' has been added to sysdbauth - but the dba permission has not been granted and the user who was created by the dump/load process is now effectively disabled - so I end up with NO dba user - and have had to restore the database again to get back to where I was. Am I on the right path? Is there something different that I need to do?
Continue reading...
Continue reading...