Security Model → You must have the EXECUTE_CATALOG_ROLE role to use the DBMS_LOGMNR package.
Security Model → You must have the EXECUTE_CATALOG_ROLE role to use the DBMS_LOGMNR_D package.
Security Model → The XDBADMIN role is required to invoke the configuration interface. It may invoked by the database user \" XDB \". The authorization interface can be invoked by any user.
Security Model → This package runs with the privileges of the calling user, not the package owner ( SYS ). The table function DISPLAY_CURSOR requires to have select privileges on the following fixed views: V$SQL_PLAN, V$SESSION and V$SQL_PLAN_STATISTICS_ALL. Using the DISPLAY_AWR Function requires the user to have SELECT privileges on DBA_HIST_SQL_PLAN, DBA_HIST_SQLTEXT, and V$DATABASE. Using the DISPLAY_SQLSET Function
Security Model → This package is available to PUBLIC and performs its own security checking based on the schema object being described.
Security Model → and the Oracle Database SQL Language Reference. For information about the security model pertaining to temporary LOB s, see Operational Notes.
Security Model → User group PUBLIC is granted EXECUTE privilege on this package. See Also: Oracle Database Security Guide for more information about user group PUBLIC
Security Model → Users must have EXECUTE privilege to run the procedures of DBMS_HM package.
Security Model → This package runs with SYS privileges; therefore, any user who has privilege to execute the package can manipulate the bitmaps.
Security Model → The procedural option is needed to use this package. This package must be created under SYS (connect/as sysdba). Operations provided by this package are performed under the current calling user, not under the package owner SYS. You can use the UTL_REF package from stored PL/SQL procedures/packages on the server, as well as from client/side PL/SQL code. When invoked from PL/SQL procedures/packages
Security Model → The dbmsotpt.sql script must be run as user SYS. This creates the public synonym DBMS_OUTPUT, and EXECUTE permission on this package is granted to public.
Security Model → Oracle installs this package in the SYS schema. You can then grant package access to existing users and roles as needed. The package also grants access to the PUBLIC role so no explicit grant needs to be done.
Security Model → The DBMS_CQ_NOTIFICATION package requires that the user have the CHANGE NOTIFICATION system privilege in order to receive notifications, and be granted EXECUTE privilege on the DBMS_CQ_NOTIFICATION package. In addition the user is required to have SELECT privileges on all objects to be registered. Note that if the SELECT privilege on an object was granted at the time of registration creation but lost
Security Model → This package should be installed as SYS. By default, the package is initialized with the current user name, current time down to the second, and the current session.
Security Model → No specific system privileges are required to use DBMS_JOB. No system privileges are available to manage DBMS_JOB. Jobs cannot be altered or deleted other than jobs owned by the user. This is true for all users including those users granted DBA privileges. You can execute procedures that are owned by the user or for which the user is explicitly granted EXECUTE. However, procedures for which the user
Security Model → the security exposure this involves. In installing UTL_MAIL, you should take steps to prevent the … Managing Fine-grained Access to External Network Services in Oracle Database Security Guide
Security Model → Security for the DBMS_DATAPUMP package is implemented through roles. Roles The existing … Although the SYS schema does not have the EXP_FULL_DATABASE role assigned to it, all security checks … IMP_FULL_DATABASE role assigned to it, all security checks performed by Data Pump that require the IMP_FULL_DATABASE role will also grant access
Security Model → The subprograms in the DBMS_REPORT package operate under the current user's privileges. When reports are generated by means of the DBMS_REPORT interface, the component building the report will check to ensure the current user has all of the necessary privileges to see that report.
Security Model → The EXECUTE privilege is granted to PUBLIC on all types defined in the DBMS_MGWMSG package as well as the canonical types. The DBMS_MGWMSG packages and object types are owned by SYS. Note: You must run the catmgw.sql script to load the Messaging Gateway packages and object types into the database. Refer to the Oracle Streams Advanced Queuing User's Guide for information on loading database objects
Security Model → The following code describes the minimal set of privileges required to Create directory objects Operate the interface provided by the DBMS_WORKLOAD_CAPTURE and DBMS_WORKLOAD_REPLAY packages Act as a replay client user (wrc someuser / somepassword or wrc USER=someuser PASSWORD=somepassword ) DROP USER rom1 CASCADE; CREATE USER rom1 IDENTIFIED BY rom1; GRANT EXECUTE ON DBMS_WORKLOAD_CAPTURE TO rom1;