• Re: User authorization check failed

    From Steve@21:1/5 to richf...@gmail.com on Tue Dec 14 08:02:45 2021
    On Wednesday, December 15, 2021 at 2:40:48 AM UTC+11, richf...@gmail.com wrote:
    I have just been created as a DBA on a linux server but when I try and run accessdb I get the following error:

    E_US18FF User authorization check failed.
    Your user identifier was not known to this installation.
    Contact your system manager for further assistance.

    What needs to be modified so I can run this?

    Rich

    Hi Rich

    I suspect you have a "dba" OS account, but no "dba" Ingres user.

    Log in as the installation owner (ingres by default) and then using accessdb, create Ingres user dba. Then you should be able to log in as dba at the OS level and run accessdb.

    Note, you have to be a privileged user to run accessdb.

    Please see Karl's first comment in this link:

    https://communities.actian.com/s/question/0D53300003w96oZCAQ/how-to-specify-the-password-when-using-terminal-monitor-

    Steve

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rich Ford@21:1/5 to All on Tue Dec 14 07:40:47 2021
    I have just been created as a DBA on a linux server but when I try and run accessdb I get the following error:

    E_US18FF User authorization check failed.
    Your user identifier was not known to this installation.
    Contact your system manager for further assistance.

    What needs to be modified so I can run this?

    Rich

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roy Hann@21:1/5 to Rich Ford on Tue Dec 14 16:30:49 2021
    Rich Ford wrote:

    I have just been created as a DBA on a linux server but when I try and run accessdb I get the following error:

    E_US18FF User authorization check failed.
    Your user identifier was not known to this installation.
    Contact your system manager for further assistance.

    What needs to be modified so I can run this?

    It's important to understand that Ingres distinguishes Ingres system administrators from Ingres DBAs. A system administrator is responsible
    for the Ingres processes and physical resources, and can act as a
    security administrator. An Ingres DBA has relatively limited privileges,
    being restricted to managing database assets like tables, procedures
    etc, and granting access to those assets.

    An Ingres DBA is just an ordinary Ingres user who has created a
    database and by virtue of doing so is the DBA of that database.

    A lot of sites blur/confuse the roles and allow the system administrator
    (often the user ingres) to also be the DBA of all the databases. That is
    poor practice IMO but very common, possibly almost universal.

    If your role is such that you would want to run accessdb that implies to
    me that you want to be a system administrator. If you can't/won't su to
    ingres to do those things, log in as the installation owner (probably
    ingres) then in accessdb "create" your user ID as an Ingres user and
    give it the privileges you need, e.g. security administrator, operator, maintain users, maintain locations--in fact take 'em all.

    Roy

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From George Neuner@21:1/5 to specially@processed.almost.meat on Thu Dec 16 22:28:01 2021
    On Tue, 14 Dec 2021 16:30:49 -0000 (UTC), Roy Hann <specially@processed.almost.meat> wrote:

    :

    It's important to understand that Ingres distinguishes Ingres system >administrators from Ingres DBAs. A system administrator is responsible
    for the Ingres processes and physical resources, and can act as a
    security administrator. An Ingres DBA has relatively limited privileges, >being restricted to managing database assets like tables, procedures
    etc, and granting access to those assets.

    An Ingres DBA is just an ordinary Ingres user who has created a
    database and by virtue of doing so is the DBA of that database.

    A lot of sites blur/confuse the roles and allow the system administrator >(often the user ingres) to also be the DBA of all the databases. That is
    poor practice IMO but very common, possibly almost universal.

    Yes.

    If your role is such that you would want to run accessdb that implies to
    me that you want to be a system administrator. If you can't/won't su to >ingres to do those things, log in as the installation owner (probably
    ingres) then in accessdb "create" your user ID as an Ingres user and
    give it the privileges you need, e.g. security administrator, operator, >maintain users, maintain locations--in fact take 'em all.

    FWIW: in many Unix/Linux system DBMS installations, the owner account ("ingres", "postgres", "mysql", etc.) does not have a password and so
    no one can log in as that user.

    The DBMS tools do typically allow admin or su to access the DBMS as if
    they are the owner.

    Roy
    George

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)