You are using an outdated browser. Please upgrade to the latest version for the best experience.
How do I narrow my search results?

After you submit your search query:

  1. On the Refine Search results page, select one or more categories of products or services from the left sidebar.
  2. Then for a category with search results, click Select to choose your product and release filters, and then click OK.

For search queries that contain multiple words, surround the query with quotes, and then resubmit your query. Example: "database cloud service"

How do I find the documentation for my product or service?

From the home page, click the technology categories for your products or services. If you do not know which category to pick, try the following features:

  • Click the Find a product tab and search for your product or service.
  • Click Browse All Products & Services at the bottom of the home page to view an alphabetical listing of products and services.
  • Apple Safari: Version 6
  • Google Chrome: Version 29 and later
  • Mozilla Firefox: Version 24 and later
  • Microsoft Internet Explorer: Version 9 and later
Results for security


21 to 80 of 4163 results. previous page Prev  Next next page
Results per page:  20 | 40 |  60 


Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_LOGMNR

Security ModelYou must have the EXECUTE_CATALOG_ROLE role to use the DBMS_LOGMNR package.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_LOGMNR_D

Security ModelYou must have the EXECUTE_CATALOG_ROLE role to use the DBMS_LOGMNR_D package.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_EPG

Security ModelThe 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.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

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 1 (11.1)

DBMS_DESCRIBE

Security ModelThis package is available to PUBLIC and performs its own security checking based on the schema object being described.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_LOB

Security Modeland the Oracle Database SQL Language Reference. For information about the security model pertaining to temporary LOB s, see Operational Notes.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_RULE_ADM

Security ModelUser group PUBLIC is granted EXECUTE privilege on this package. See Also: Oracle Database Security Guide for more information about user group PUBLIC

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_HM

Security ModelUsers must have EXECUTE privilege to run the procedures of DBMS_HM package.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_SPACE_ADMIN

Security ModelThis package runs with SYS privileges; therefore, any user who has privilege to execute the package can manipulate the bitmaps.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

UTL_REF

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

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_OUTPUT

Security ModelThe 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.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_OBFUSCATION_TOOLKIT

Security ModelOracle 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.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_CQ_NOTIFICATION

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

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_RANDOM

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

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

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 1 (11.1)

UTL_MAIL

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

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_DATAPUMP

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

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_REPORT

Security ModelThe 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.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_MGWMSG

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

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_WORKLOAD_CAPTURE

Security ModelThe 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;

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

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 1 (11.1)

DBMS_DDL

Security ModelThis package runs with the privileges of the calling user, rather than the package owner SYS.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_LIBCACHE

Security Modelobjects with access granted though roles. This is a standard PL/SQL security limitation.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_CRYPTO

Security ModelOracle Database installs this package in the SYS schema. You can then grant package access to existing users and roles as needed.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_ADVISOR

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 1 (11.1)

DBMS_APPLICATION_INFO

Security ModelNote: The public synonym for DBMS_APPLICATION_INFO is not dropped before creation so that you can redirect the public synonym to point to your own package. No further privileges are required. The DBMSAPIN.SQL script is already run as a part of standard database creation.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

UTL_TCP

Security Modelconnect. Note: For more information, see Managing Fine-grained Access to External Network Services in Oracle Database Security Guide

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_ADVANCED_REWRITE

Security Modeladministrators. You can control security on this package by granting the EXECUTE privilege to

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_SESSION

Security ModelThis package runs with the privileges of the calling user, rather than the package owner SYS.

Database New Features Guide, 11g Release 1 (11.1)

Oracle 11g Database New Features

1.12 Securitycolumns as FLOAT ODBC applications will perform faster, with little or no code change. 1.12 Security … Features described in the following sections include security and compliance.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_RULE

Security ModelPUBLIC is granted EXECUTE privilege on this package.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_PROFILER

Security ModelThe profiler only gathers data for units for which a user has CREATE privilege; you cannot use the package to profile units for which EXECUTE ONLY access has been granted. In general, if a user can debug a unit, the same user can profile it. However, a unit can be profiled whether or not it has been compiled DEBUG. Oracle advises that modules that are being profiled should be compiled DEBUG, since

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

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 1 (11.1)

DBMS_STREAMS_ADM

Security Modeluser is the user in whose security domain a capture process or synchronous capture captures changes … user in whose security domain an apply process dequeues messages that satisfy its rule sets, applies

Database Concepts, 11g Release 1 (11.1)

Schema Object Dependencies

Security AuthorizationOracle Database notices when a DML object or system privilege is granted to or revoked from a user or PUBLIC and automatically invalidates all the owner's dependent objects. Oracle Database invalidates the dependent objects to verify that an owner of a dependent object continues to have the necessary privileges for all referenced objects.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_TDB

Security ModelUse of this package requires the DBA privilege.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

UTL_SMTP

Security Modelconnect. Note: For more information, see Managing Fine-grained Access to External Network Services in Oracle Database Security Guide

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

UTL_FILE

Security ModelThe set of files and directories that are accessible to the user through UTL_FILE is controlled by a number of factors and database parameters. Foremost of these is the set of directory objects that have been granted to the user. The nature of directory objects is discussed in [AWAITING XLINK TARGET]. Assuming the user has both READ and WRITE access to the directory object user_dir, the user can open

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

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 1 (11.1)

DEBUG_EXTPROC

Security ModelYour Oracle account must have EXECUTE privileges on the package and CREATE LIBRARY privileges.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_METADATA

Security ModelThe object views of the Oracle metadata model implement security as follows: Nonprivileged users

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

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 1 (11.1)

DBMS_STREAMS

Security ModelUser group PUBLIC is granted EXECUTE privilege on this package. See Also: Oracle Database Security Guide for more information about user group PUBLIC

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_DIMENSION

Security ModelSecurity on this package can be controlled by granting EXECUTE to selected users or roles. A user

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_UTILITY

Security ModelDBMS_UTILITY runs with the privileges of the calling user for the NAME_RESOLVE Procedure and the COMPILE_SCHEMA Procedure. This is necessary so that the SQL works correctly. The package does not run as SYS. The privileges are checked using DBMS_DDL.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_SERVICE

Security ModelPrivileges The client using this package should have the ALTER SYSTEM execution privilege and the V$SESSION table read privilege. Schemas This package should be installed under SYS schema. Roles The EXECUTE privilege of the package is granted to the DBA role only.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_CDC_SUBSCRIBE

Security ModelChange Data Capture grants EXECUTE privileges to PUBLIC on the DBMS_CDC_SUBSCRIBE package.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_COMPARISON

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 1 (11.1)

DBMS_XA

Security ModelThis package is created under SYS. Operations provided by this package are performed under the current calling user, not under the package owner SYS.Any DBMS_XA subprogram called from an anonymous PL/SQL block is executed using the privileges of the current user. Any DBMS_XA subprogram called from a stored procedure is executed using the privileges of the owner of the stored procedure. SELECT privilege

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_ROWID

Security ModelThis package runs with the privileges of calling user, rather than the package owner SYS.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_FLASHBACK

Security ModelTo use this package, a database administrator must grant EXECUTE privileges for DBMS_FLASHBACK.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

UTL_HTTP

Security Modelconnect. Note: For more information, see Managing Fine-grained Access to External Network Services in Oracle Database Security Guide

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_DISTRIBUTED_TRUST_ADMIN

Security ModelTo execute DBMS_DISTRIBUTED_TRUST_ADMIN, the EXECUTE_CATALOG_ROLE role must be granted to the DBA. To select from the view TRUSTED_SERVERS, the SELECT_CATALOG_ROLE role must be granted to the DBA. It is important to know whether all servers are trusted or not trusted. Trusting a particular server with the ALLOW_SERVER procedure does not have any effect if the database already trusts all databases,

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_RLS

Security ModelA security check is performed when the transient view is created with a subquery. The schema owning … the policy function, which generates the dynamic predicate, is the transient view's definer for security check and object lookup.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_FGA

Security ModelExecute privilege on DBMS_FGA is needed for administering audit policies. Because the audit function can potentially capture all user environment and application context values, policy administration should be executable by privileged users only. The policy event handler module will be executed with the module owner's privilege.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_REPAIR

Security ModelThe package is owned by SYS. Execution privilege is not granted to other users.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_ERRLOG

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

Database Installation Guide for Linux, 11g Release 1 (11.1)

Oracle Database Postinstallation Tasks

4.3.2 Configuring Oracle Label SecurityIf you installed Oracle Label Security, you must configure it in a database before you use it. You … can configure Oracle Label Security in two ways; with Oracle Internet Directory integration and … without Oracle Internet Directory integration. If you configure Oracle Label Security without Oracle … stage. Note: To configure

Database 2 Day + Security Guide, 11g Release 1 (11.1)

Database 2 Day + Security Guide - Contents

ContentsDocuments Conventions 1 Introduction to Oracle Database Security About This Guide Before Using This … Guide What This Guide Is and Is Not Common Database Security Tasks Tools for Securing Your Database … Securing the Database Installation and Configuration Enabling the Default Security Settings Securing the … Run-Time Facilities

Database Advanced Security Administrator's Guide, 11g Release 1 (11.1)

Database Advanced Security Administrator's Guide - Contents

ContentsAdvanced Security? Oracle Database 11 g Release 1 (11.1) New Features in Oracle Advanced Security Part I … Getting Started with Oracle Advanced Security 1 Introduction to Oracle Advanced Security 1.1 Security … Challenges in an Enterprise Environment 1.1.1 Security in Enterprise Grid