How do I narrow my search results?
After you submit your search query:
- On the Refine Search results page, select one or more categories of products or services from the left sidebar.
- 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
Enterprise Manager name Record Applied DDL → Scope Database Enterprise Manager name Record Applied DDL
Executing SQL DDL and DML Statements → ->terminateStatelessConnectionPool (scPool); Executing S QL DDL and DML Statements SQL is the industry-wide language
Follow the Best Practices for Replicating DDL Changes → When replicating data definition language (DDL) changes, do not allow system-generated names for … replicate DDL in your Oracle Streams environment, then any table structure changes must be performed … manually at each database in the environment. See Also: \"Considerations for Applying DDL Changes\"
10.5.3 Setting up a Skip Handler for a DDL Statement → You can create a procedure to intercept certain DDL statements and replace the original DDL … transparently handle DDL transactions with file specifications. The following procedure can handle … handle tablespace DDL transactions: CREATE OR REPLACE PROCEDURE SYS.HANDLE_TBS_DDL ( OLD_STMT IN
Types of DDL Changes Ignored by an Apply Process → The following types of DDL changes are not supported by an apply process. These types of DDL … DDL LCR that specifies an operation that cannot be applied, then the apply process ignores the DDL … LCR and records the following message in the apply process trace file, followed by the DDL text that
C.11 DDL Statements Supported by a Logical Standby Database → C.11 DDL Statements Supported by a Logical Standby Databas e Table C-1 lists the supported values … DBMS_LOGSTDBY package and Section 10.5.3, \"Setting up a Skip Handler for a DDL Statement\" Table C-1 Values … ALTER INDEX CREATE INDEX DROP INDEX NON_SCHEMA_DDL All DDL that does not pertain to a particular schema … SEGMENT SCHEMA_DDL
C.4 Support For Row-level Security and Fine-Grained Auditing → As of Oracle Database 11 g, Logical Standby can automatically replicate the security environment provided through the DBMS_RLS and DBMS_FGA PL/SQL packages. This support simplifies management of security considerations when a server fails over to the standby since the security environment will transparently be maintained. It also ensures that access control policies applied to the primary data can
C.4.2 Fine-Grained Auditing → Fine-grained auditing provides a way to audit select statements. The DBMS_FGA package enables all select statements that access a table to be captured, together with what data was accessed. An FGA policy may be applied to a particular column or even to only those select statements that return rows for which a specified predicate returns TRUE. When a DBMS_FGA procedure is executed on the primary, additional
C.8.3 Handling XML and XDB PL/SQL Packages in Logical Standby → In Oracle Database 11 g release 1 (11.1), Logical Standby supports XML when it is stored in CLOB format. However, there are several PL/SQL packages used in conjunction with XML that are not fully supported. The PL/SQL packages and procedures that are supported by Logical Standby only modify in-memory structures; they do not modify data stored in the database. These packages do not generate redo and
C.10 Skipped SQL Statements on a Logical Standby Database → C.10 S kipped SQL Statements on a Logical Standby Database By default, the following SQ L statements are automatically skipped by SQL Apply: ALTER DATABASE ALTER MATERIALIZED VIEW ALTER MATERIALIZED VIEW LOG ALTER SESSION ALTER SYSTEM CREATE CONTROL FILE CREATE DATABASE CREATE DATABASE LINK CREATE PFILE FROM SPFILE CREATE MATERIALIZED VIEW CREATE MATERIALIZED VIEW LOG CREATE SCHEMA AUTHORIZATION CREATE
C.1 Datatype Considerations → The following sections list the supported and unsupported database objects: Supported Datatypes in a Logical Standby Database Unsupported Datatypes in a Logical Standby Database
C.7 Unsupported Table Storage Types → Logical standby databases do not support the following table storage types: Tables stored with segment compression enabled Tables containing LOB columns stored as SecureFiles Tables with virtual columns
C.1.2 Unsupported Datatypes in a Logical Standby Database → C.1.2 Unsupported Datatypes in a Logical Standby Databas e Logical standby databases do not support the following datatypes: BFILE Collections (including VARRAYS and nested tables) Multimedia data types (including Spatial, Image, and Oracle Text ) ROWID, UROWID User-defined types LOBs stored as SecureFiles XMLType stored as Object Relational Binary XML
C.6 Supported Table Storage Types → Logical standby databases support the following table storage types: Cluster tables (including index clusters and heap clusters) Index-organized tables (partitioned and nonpartitioned, including overflow segments) Heap-organized tables (partitioned and nonpartitioned)
C.11.2 Replication of AUD$ and FGA_LOG$ on Logical Standbys → Auditing and fine-grained auditing are supported on logical standbys. Changes made to the AUD$ and FGA_AUD$ tables at the primary database are replicated at the logical standby. Both the AUD$ table and the FGA_AUD$ table have a DBID column. If the DBID value is that of the primary database, then the row was replicated to the logical standby based on activities at the primary. If the DBID value is
C Data Type and DDL Support on a Logical Standby Database → Database DDL Statements Supported by a Logical Standby Database Replication of AUD$ and FGA_LOG$ on Logical Standbys
C.8.1 Supported PL/SQL Supplied Packages → C.8.1 Supported PL/SQL Supplied Package s Oracle PL/SQL supplied packages that do not modify system metadata or user data leave no footprint in the archived redo log files, and hence are safe to use on the primary database. Examples of such packages are DBMS_OUTPUT, DBMS_RANDOM, DBMS_PIPE, DBMS_DESCRIBE, DBMS_OBFUSCATION_TOOLKIT, DBMS_TRACE, DBMS_METADATA, DBMS_CRYPTO. Oracle PL/SQL supplied packages
C.4.1 Row-level Security → supporting packages. You must ensure that these objects are placed in maintained schemas and that no DDL
C.8.2 Unsupported PL/SQL Supplied Packages → Oracle PL/SQL supplied packages that modify system metadata typically are not supported by SQL Apply, and therefore their effects are not visible on the logical standby database. Examples of such packages are DBMS_JAVA, DBMS_REGISTRY, DBMS_ALERT, DBMS_SPACE_ADMIN, DBMS_REFRESH, DBMS_REDEFINITION, and DBMS_AQ. Specific support for DBMS_JOB has been provided. Job execution is suspended on a logical
C.2 Support for Transparent Data Encryption (TDE) → Data Guard SQL Apply can be used to provide data protection for a primary database with Transparent Data Encryption (TDE) enabled. Consider the following when using a logical standby database to provide data protection for applications with advanced security requirements: Tables with Transparent Data Encryption using server held keys are supported in the context of a logical standby database when