Results for security


41 to 60 of 5025 results. Prev  Next
Results per page:   20  | 40 | 60


Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_MVIEW

Security ModelThe DBMS_MVIEW package consists of a number of materialized view-related subprograms, each of which has different functionality and privilege requirements. The privilege model is generally based on the invoker's right. Each package subprogram is executed by first checking the privileges against the invoker. If all the required privileges are met, the subprogram will be executed. Otherwise, an insufficient

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

Logical Change Record TYPEs

Security ModelPUBLIC is granted EXECUTE privilege on the types described in this chapter.

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_METADATA_DIFF

Security Modelfetch the metadata to be compared. Therefore, the security model used for DBMS_METADATA also … .) See Also: DBMS_METADATA for information about the DBMS_METADATA security model

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_CDC_PUBLISH

Security ModelYou must have the EXECUTE_CATALOG_ROLE role to use the DBMS_CDC_PUBLISH package. Additional privileges and roles are required depending on the publishing mode and whether the publisher is on the source or staging database. See the section on Granting Privileges and Roles to the Publisher in Oracle Database Data Warehousing Guide for details.

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_XPLAN

Security ModelThis 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

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_PIPE

Security ModelSecurity can be achieved by use of GRANT EXECUTE on the DBMS_PIPE package by creating a pipe using … particular features or pipenames to particular users or roles. Depending upon your security

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_DST

Security ModelThe DBMS_DST package is an invoker's rights package. See Also: Oracle Database PL/SQL Language Reference for more information about using Invoker Rights or Definer Rights The execute privilege on the package is granted to the EXECUTE_CATALOG_ROLE role. This role is normally granted to selected users to allow EXECUTE privileges for packages and procedures in the data dictionary. The user that invokes

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_SQL

Security Modelimprove the security of the package. Preventing Malicious or Accidental Access of Open Cursor Numbers … these rules. Preventing Inappropriate Use of a Cursor Cursors are protected from security breaches … . When security_level = 2, the checks are always made. Upgrade Considerations This security regime is … , users of DBMS_SQL

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_SCHEDULER

Security ModelThe DBMS_SCHEDULER package ignores privileges granted on scheduler objects, such as jobs or chains, through roles. Object privileges must be granted directly to the user.

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

UTL_TCP

Security Model: For more information about managing fine-grained access, see Oracle Database Security Guide

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_ALERT

Security ModelSecurity on this package can be controlled by granting EXECUTE on this package to selected users or

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_DBFS_CONTENT_SPI

Security ModelImplementations of the DBMS_DBFS_CONTENT_SPI package should be created as AUTHID CURRENT_USER.

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_REDEFINITION

Security ModelSubprograms in the DBMS_REDEFINTION package are run with invokers' rights (with the privileges of the current user). There are two modes: In USER mode, the user who has the CREATE TABLE and CREATE MVIEW privileges may redefine a table residing in his own schema. In FULL mode, the user who has the ANY privilege may redefine tables in any schema.

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_XDB_ADMIN

Security ModelOwned by XDB, the DBMS_XDB_ADMIN package must be created by SYS or XDB. The EXECUTE privilege is granted to SYS or XDB or DBA. Subprograms in this package are executed using the privileges of the current user.

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_APPLY_ADM

Security ModelSecurity on this package can be controlled in either of the following ways: Granting EXECUTE on

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_OUTLN

Security ModelDBMS_OUTLN contains management procedures that should be available to appropriate users only. EXECUTE privilege is not extended to the general user community unless the DBA explicitly does so. PL/SQL functions that are available for outline management purposes can be executed only by users with EXECUTE privilege on the procedure (or package).

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_RLMGR

Security ModelThe Oracle Database installation runs the catrul.sql script to load the DBMS_RLMGR package and create the required Rules Manager schema objects in the EXFSYS Schema. DBMS_RLMGR is an EXFSYS -owned package compiled with AUTHID CURRENT_USER. Any DBMS_RLMGR subprogram called from an anonymous PL/SQL block is run using the privileges of the current user. A user must be granted CONNECT and RESOURCE roles,

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_FILE_GROUP

Security ModelSecurity on this package can be controlled in either of the following ways: Granting EXECUTE on

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_JOB

Security ModelNo 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

Database PL/SQL Packages and Types Reference, 11g Release 2 (11.2)

DBMS_DBFS_CONTENT

Security ModelThe DBMS_DBFS_CONTENT package runs under AUTHID CURRENT_USER.


Was this page helpful?