find_all_privs.sql

 -- -----------------------------------------------------------------------------
--                 WWW.PETEFINNIGAN.COM LIMITED
-- -----------------------------------------------------------------------------
-- Script Name : find_all_privs.sql
-- Author      : Pete Finnigan
-- Date        : June 2003
-- -----------------------------------------------------------------------------
-- Description : Use this script to find which privileges have been granted to a
--               particular user. This scripts lists ROLES, SYSTEM privileges
--               and object privileges granted to a user. If a ROLE is found
--               then it is checked recursively.
--
--               The output can be directed to either the screen via dbms_output
--               or to a file via utl_file. The method is decided at run time
--               by choosing either 'S' for screen or 'F' for File. If File is
--               chosen then a filename and output directory are needed. The
--               output directory needs to be enabled via utl_file_dir prior to
--               9iR2 and a directory object after.
-- -----------------------------------------------------------------------------
-- Maintainer  : Pete Finnigan (http://www.petefinnigan.com)
-- Copyright   : Copyright (C) 2004 PeteFinnigan.com Limited. All rights
--               reserved. All registered trademarks are the property of their
--               respective owners and are hereby acknowledged.
-- -----------------------------------------------------------------------------
--  Usage      : The script provided here is available free. You can do anything
--               you want with it commercial or non commercial as long as the
--               copyrights and this notice are not removed or edited in any way.
--               The scripts cannot be posted / published / hosted or whatever
--               anywhere else except at www.petefinnigan.com/tools.htm
-- -----------------------------------------------------------------------------
-- To Do       :
--               1 - add proxy connection authorities
--               2 - add SELECT ANY TABLE and SELECT ANY DICTIONARY access
-- -----------------------------------------------------------------------------
-- Version History
-- ===============
--
-- Who         version     Date      Description
-- ===         =======     ======    ======================
-- P.Finnigan  1.0         Jun 2003  First Issue.
-- P.Finnigan  1.1         Jun 2003  Output to file added.
-- P.Finnigan  1.2         Jan 2004  Corrected exit/exists bug in 'whenever'.
-- N.Dunbar    1.3         Jan 2004  Added real TAB characters and uppercased
--                                   user input for username and output method.
-- P.Finnigan  1.4         Feb 2004  Clarified use of utl_file for 9ir2.
-- P.Finnigan  1.5         Feb 2004  Added the owner to output for object privs
--                                   (Thanks to Guy Dallaire for this addition)
-- P.Finnigan  1.6         Oct 2004  Changed output to include title in line
--                                   with other reports in the toolkit. Also added
--                                   usage notes.
-- P.Finnigan  1.7         Apr 2005  Added whenever sqlerror continue to stop
--                                   subsequent errors barfing SQL*Plus. Thanks
--                                   to Norman Dunbar for the update.
-- D. Arthur   1.8         Nov 2014  1) Added ability to skip table privileges; 
--                                   2) Added sorting: system privs, table privs, 
--                                   roles, then execute before table privs;
--                                   3) Added parallel for performance;
--                                   4) Indicate if role is password protected;
--                                   5) Fix: in column privs, owner prefix
--                                   on the table instead of the column
--                                   6) PF: put all original formatting back.
-- P.Finnigan  1.9         Nov 2014  David Litchfield found a bug ORA-12801 with
--                                   parallel hint. You can try uncommenting the
--                                   hint and if it works fine; if not leave 
--                                   commented out.
-- -----------------------------------------------------------------------------

--whenever sqlerror exit rollback
set feed on
set head on
set arraysize 1
set space 1
set verify off
set pages 25
set lines 80
set termout on
--clear screen
set serveroutput on size 1000000

--spool find_all_privs.lis

undefine user_to_find
undefine output_method
undefine file_name
undefine output_dir

set feed off
col system_date noprint new_value val_system_date

select to_char (sysdate, 'Dy Mon dd hh24:mi:ss yyyy') system_date from sys.dual;

set feed on

prompt find_all_privs: Release 1.9.0.0.0 - Production on &val_system_date
prompt Copyright (c) 2004 - 2014 PeteFinnigan.com Limited. All rights reserved.
prompt
accept user_to_find char prompt   'NAME OF USER TO CHECK                 [ORCL]: ' default orcl
accept output_method char prompt  'OUTPUT METHOD Screen/File                [S]: ' default s
accept file_name char prompt      'FILE NAME FOR OUTPUT              [priv.lst]: ' default priv.lst
accept output_dir char prompt     'OUTPUT DIRECTORY [DIRECTORY  or file (/tmp)]: ' default "/tmp"
accept examine_tables char prompt 'EXAMINE TABLE PRIVILEGES?              [N/Y]: ' default "N"
prompt

declare
   --
   lv_tabs             number := 0;
   lg_fptr             utl_file.file_type;
   lv_file_or_screen   varchar2 (1) := 'S';

    --
    procedure open_file (pv_file_name in varchar2,
            pv_dir_name in varchar2) is 
    begin
        lg_fptr:=utl_file.fopen(pv_dir_name,pv_file_name,'A');
    exception
        when utl_file.invalid_path  then
            dbms_output.put_line('invalid path');
        when utl_file.invalid_mode  then
            dbms_output.put_line('invalid mode');
        when utl_file.invalid_filehandle  then
            dbms_output.put_line('invalid filehandle');
        when utl_file.invalid_operation  then
            dbms_output.put_line('invalid operation');
        when utl_file.read_error  then
            dbms_output.put_line('read error');
        when utl_file.write_error  then
            dbms_output.put_line('write error');
        when utl_file.internal_error  then
            dbms_output.put_line('internal error');
        when others then
            dbms_output.put_line('ERROR (open_file) => '||sqlcode);
            dbms_output.put_line('MSG (open_file) => '||sqlerrm);

    end open_file;
    --
    procedure close_file is
    begin
        utl_file.fclose(lg_fptr);
    exception
        when utl_file.invalid_path  then
            dbms_output.put_line('invalid path');
        when utl_file.invalid_mode  then
            dbms_output.put_line('invalid mode');
        when utl_file.invalid_filehandle  then
            dbms_output.put_line('invalid filehandle');
        when utl_file.invalid_operation  then
            dbms_output.put_line('invalid operation');
        when utl_file.read_error  then
            dbms_output.put_line('read error');
        when utl_file.write_error  then
            dbms_output.put_line('write error');
        when utl_file.internal_error  then
            dbms_output.put_line('internal error');
        when others then
            dbms_output.put_line('ERROR (close_file) => '||sqlcode);
            dbms_output.put_line('MSG (close_file) => '||sqlerrm);

    end close_file;
    --
    procedure write_op (pv_str in varchar2) is
    begin
        if lv_file_or_screen='S' then
            dbms_output.put_line(pv_str);
        else
            utl_file.put_line(lg_fptr,pv_str);
        end if;
    exception
        when utl_file.invalid_path  then
            dbms_output.put_line('invalid path');
        when utl_file.invalid_mode  then
            dbms_output.put_line('invalid mode');
        when utl_file.invalid_filehandle  then
            dbms_output.put_line('invalid filehandle');
        when utl_file.invalid_operation  then
            dbms_output.put_line('invalid operation');
        when utl_file.read_error  then
            dbms_output.put_line('read error');
        when utl_file.write_error  then
            dbms_output.put_line('write error');
        when utl_file.internal_error  then
            dbms_output.put_line('internal error');
        when others then
            dbms_output.put_line('ERROR (write_op) => '||sqlcode);
            dbms_output.put_line('MSG (write_op) => '||sqlerrm);

    end write_op;
    --
   procedure get_privs (pv_grantee in varchar2, lv_tabstop in out number)
   is
      --
      lv_tab    varchar2 (50) := null;
      lv_loop   number;

      --
      cursor c_main (
         cp_grantee in varchar2)
      is
-- the hint is commented out as David got an ORA-12801 and an ORA-00600 because of the 
-- hint. You can try the hint, if it works, then fine, if not comment out
--           select /*+ PARALLEL a */
           select
                 a.*
             from (select 'ROLE' typ,
                          grantee grantee,
                          granted_role priv,
                          admin_option ad,
                          '--' tabnm,
                          '--' colnm,
                          '--' owner,
                          r.password_required pwd
                     from dba_role_privs rp join dba_roles r on rp.granted_role = r.role
                    where grantee = cp_grantee
                   union
                   select 'SYSTEM' typ,
                          grantee grantee,
                          privilege priv,
                          admin_option ad,
                          '--' tabnm,
                          '--' colnm,
                          '--' owner,
                          '--' pwd
                     from dba_sys_privs
                    where grantee = cp_grantee
                   union
                   select 'TABLE' typ,
                          grantee grantee,
                          privilege priv,
                          grantable ad,
                          table_name tabnm,
                          '--' colnm,
                          owner owner,
                          '--' pwd
                     from dba_tab_privs
                    where grantee = cp_grantee and '&&examine_tables' = 'Y'
                   union
                   select 'COLUMN' typ,
                          grantee grantee,
                          privilege priv,
                          grantable ad,
                          table_name tabnm,
                          column_name colnm,
                          owner owner,
                          '--' pwd
                     from dba_col_privs
                    where grantee = cp_grantee and '&&examine_tables' = 'Y') a
         order by case
                     when a.typ = 'ROLE' then 4
                     when a.typ = 'SYSTEM' then 1
                     when a.typ = 'TABLE' then 2
                     when a.typ = 'COLUMN' then 3
                     else 5
                  end,
                  case when a.priv in ('EXECUTE') then 1 when a.priv in ('SELECT', 'UPDATE', 'INSERT', 'DELETE') then 3 else 2 end,
                  a.tabnm,
                  a.colnm,
                  a.priv;

   begin
      lv_tabstop := lv_tabstop + 1;

      for lv_loop in 1 .. lv_tabstop
      loop
         lv_tab := lv_tab || chr (9);
      end loop;

      for lv_main in c_main (pv_grantee)
      loop
         if lv_main.typ = 'ROLE' then
            write_op (
                  lv_tab
               || 'ROLE => '
               || lv_main.priv
               || case when lv_main.pwd = 'YES' then ' (password)' else null end
               || ' which contains =>');
            get_privs (lv_main.priv, lv_tabstop);
         elsif lv_main.typ = 'SYSTEM' then
            write_op (lv_tab || 'SYS PRIV => ' || lv_main.priv || ' grantable => ' || lv_main.ad);
         elsif lv_main.typ = 'TABLE' then
            write_op (
                  lv_tab
               || 'TABLE PRIV => '
               || lv_main.priv
               || ' object => '
               || lv_main.owner
               || '.'
               || lv_main.tabnm
               || ' grantable => '
               || lv_main.ad);
         elsif lv_main.typ = 'COLUMN' then
            write_op (
                  lv_tab
               || 'COL PRIV => '
               || lv_main.priv
               || ' object => '
               || lv_main.owner
               || '.'
               || lv_main.tabnm
               || ' column_name => '
               || lv_main.colnm
               || ' grantable => '
               || lv_main.ad);
         end if;
      end loop;

      lv_tabstop := lv_tabstop - 1;
      lv_tab := '';
   exception
      when others then
         dbms_output.put_line ('ERROR (get_privs) => ' || sqlcode);
         dbms_output.put_line ('MSG (get_privs) => ' || sqlerrm);
   end get_privs;

begin
   lv_file_or_screen := upper ('&&output_method');

   if lv_file_or_screen = 'F' then
      open_file ('&&file_name', '&&output_dir');
   end if;

   write_op (
      'User => ' || upper ('&&user_to_find') || ' has been granted the following privileges');
   write_op ('====================================================================');
   get_privs (upper ('&&user_to_find'), lv_tabs);

   if lv_file_or_screen = 'F' then
      close_file;
   end if;
exception
   when others then
      dbms_output.put_line ('ERROR (main) => ' || sqlcode);
      dbms_output.put_line ('MSG (main) => ' || sqlerrm);
end;
/

prompt for updates please visit http://www.petefinnigan.com/tools.htm
prompt
--spool off

whenever sqlerror continue

Comments

Post a Comment

Popular posts from this blog

How To Purge Optimizer Statistics Advisor Old Records From 12.2 Onwards (Doc ID 2660128.1)

  In this Document Goal Solution References APPLIES TO: Oracle Database - Enterprise Edition - Version 12.2.0.1 and later Oracle Cloud Infrastructure - Database Service - Version N/A and later Information in this document applies to any platform. GOAL Goal of this document is to provide the method to purge the old records of Optimizer Statistics Advisor Task namely AUTO_STATS_ADVISOR_TASK that consumes huge SYSAUX space. Huge no.of old records retained in WRI$_ADV_OBJECTS for AUTO_STATS_ADVISOR_TASK or INDIVIDUAL_STATS_ADVISOR_TASK incurs heavy SYSAUX space. AUTO_STATS_ADVISOR_TASK is meant for Automatic Statistics Advisor task while INDIVIDUAL_STATS_ADVISOR_TASK is for Manual Statistics Advisor task.  DBA_ADVISOR_PARAMETERS displays all advisor task parameters and their current values in the database. There is a parameter name called EXECUTION_DAYS_TO_EXPIRE. This parameter is set in no.of days. Executions older than the value(no.of days) set would be purged automaticall...
Read more

Oracle session snapper

-- use dbms_session.sleep instead of dbms_lock on oracle 18c or higher -- last column  is sid  -- scipt_name   stat_to_collect   secods_of_snap  how_many_snap   sessions_to_snap -- @snapper all 100 1 lgdr@* -- @snapper all 100 1 sqlid@* -- @snapper all 190 1 all -- @snapper all 190 1 584 -- @snapper all 30 3 584 -- @snapper all 5 1 869 -- @snapper all 30 1 584 -- @snapper ash 5 1 144 -- @snapper ash=sql_id+event+wait_class+blocking_session+p2+p3 5 1 144 -- @snapper ash 5 1 156 -- @snapper ash 190  1 all -- @snapper ash 5 1 all -- @snapper ash=sid+event+wait_class 5 1 all -- @snapper ash=sid+event+wait_class,ash1=plsql_object_id+plsql_subprogram_id+sql_id 5 1 all -- @snapper ash=sid+event+wait_class,ash1=plsql_object_id+plsql_subprogram_id+sql_id,ash2=program+module+action 5 1 all -- @snapper ash=event+wait_class,stats,gather=ts,tinclude=CPU,sinclude=parse 5 1 all -- @snapper ash=sid+event+wait_class,ash1=sid+sqlid+module,stats,gather...
Read more

Oracle Materialized View In-Depth and Materialized View refresh issues in 19c

   We    had  situation demanding  tuning of  MV  refresh and  options  like  TUNE_MVIEW  and Atomic_Refresh was explored . Hence  Documenting materialized view sample commands  and views in this  blog .     After migration if we are  facing slowness  in  Materialized View refresh , we can explore to re-create  Materialized View   Since  main topic for this blog   was MV issues  in 19c ,  posting that topic   first in line below  We also   have Real-Time Materialized Views  to explore .  To Note :  1) We can  create Mv  on ON PREBUILT TABLE  2) We can create Index on Mv  3) We can  gather stats on mv  just like other table .  4) Mv can be REFRESH_MODE ON COMMIT / REFRESH ON DEMAND. 5) Mv  REFRESH_METHOD can be  Complete / FAST or FORCE . A FORCE attempts a FAST...
Read more