Re: Granting access to SQL*DBA monitoring functions
From: <jl34778_at_corp02.d51.lilly.com>
Date: 12 Sep 94 17:23:53 EST
Message-ID: <1994Sep12.172353.1_at_corp02.d51.lilly.com>
>
>
> Is user in the DBA (or whatever you called it at installation time) group at
> the OS level??
>
>
> Under Ultrix, SQL*DBA checks the OS group membership before allowing certain
> operations. Are you getting the same effect?
>
>
>
> Stephen
>
Solaris does not seem to check for the dba group. I can successfully run SQL*DBA monitors from an id that is not in the dba group but that does have the MONITORER role.
Date: 12 Sep 94 17:23:53 EST
Message-ID: <1994Sep12.172353.1_at_corp02.d51.lilly.com>
In article <34lqpl$go4_at_tyndall2.tyndall.com.au>, szander_at_tyndall2.tyndall.com.au (Stephen Zander) writes:
> In article <1994Sep2.130336.1_at_corp02.d51.lilly.com>,
> <jl34778_at_corp02.d51.lilly.com> wrote:
>>In article <19940901144453.mla_at_132.203.6.11>, mla_at_132.203.6.11 (Michel Lalonde) writes: >>> As documented, the script UTLMONTR.SQL should permit access to the >>> monitoring functions of SQL*DBA without having to logon as SYS. >>> (We have Oracle 7.0.15) >>> >>> What am I missing ... >>> >>Je ne sais pas. When I do this under Solaris 2.3, running ORACLE 7.0.15.4, it >>works fine. What operating system are you one?
>
>
> Is user in the DBA (or whatever you called it at installation time) group at
> the OS level??
>
>
> Under Ultrix, SQL*DBA checks the OS group membership before allowing certain
> operations. Are you getting the same effect?
>
>
>
> Stephen
>
Solaris does not seem to check for the dba group. I can successfully run SQL*DBA monitors from an id that is not in the dba group but that does have the MONITORER role.
-- Bob Swisshelm | swisshelm_at_Lilly.com | 317 276 5472 Eli Lilly and Company | Lilly Corporate Center | Indianapolis, IN 46285Received on Tue Sep 13 1994 - 00:23:53 CEST