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
Table of Contents → VLDB and Partitioning Guide Changes for VLDB and Partitioning in Oracle Database Release 18c Changes … for VLDB and Partitioning in Oracle Database 12c Release 2 (18.104.22.168) Changes for VLDB and … Partitioning in Oracle Database 12c Release 1 (22.214.171.124) Changes for VLDB and Partitioning in Oracle
Table of Contents → VLDB and Partitioning Guide Changes for VLDB and Partitioning in Oracle Database 12c Release 2 … (126.96.36.199) Changes for VLDB and Partitioning in Oracle Database 12c Release 1 (188.8.131.52) Changes for VLDB … 1.1 Introduction to Partitioning 1.2 VLDB and Partitioning 1.3 Partitioning As the Foundation for
Changes for VLDB and Partitioning in Oracle Database Release 18c → This chapter describes changes to Oracle Database VLDB and Partitioning Guide. Changes for VLDB and … Partitioning in Oracle Database Release 18c Changes for VLDB and Partitioning in Oracle Database … 12c Release 2 (184.108.40.206) Changes for VLDB and Partitioning in Oracle Database 12c Release 1 (220.127.116.11 … ) Changes
very large database (VLDB) → have been specified for each partition. very large database (VLDB) A very large database is a
18 Very Large Databases (VLDB) → This chapter contains an overview of VLDB topics, with emphasis on partitioning as a key component … of the VLDB strategy. It covers the following topics: Introduction to Partitioning Overview of … Partitioned Indexes Partitioning to Improve Performance See Also: Oracle Database VLDB and Partitioning … Guide for more information
Contents → Related Documents Conventions Changes in This Release for Oracle Database VLDB and Partitioning Guide … Partitioning VLDB and Partitioning Partitioning As the Foundation for Information Lifecycle Management
You can use partitioning to improve performance. → Partitioning can provide tremendous benefit to a wide variety of applications by improving performance, manageability, and availability. It is not unusual for partitioning to greatly improve the performance of certain queries or maintenance operations. Moreover, partitioning can greatly simplify common administration tasks. Partitioning also enables database designers and administrators to solve some
List of Examples → 3-1 Creating a table with partition pruning 3-2 Partitioned table sales_range with attribute clustering and a zone map on a correlated column 3-3 Execution plan for partition pruning with zone maps 3-4 Querying with a full partition-wise join 3-5 Creating a table with range and interval partitioning 3-6 Creating a table with hash partitioning 3-7 Creating
To implement your ILM strategy, you can use Heat Map in Oracle Database to track data access and modification. → To implement an Information Lifecycle Management (ILM) strategy for data movement in your database, you can use Heat Map and Automatic Data Optimization (ADO) features. Note: Heat Map and ADO are supported in Oracle Database 12 c Release 2 multitenant environments. This section contains the following topics: Using Heat Map Using Automatic Data Optimization Limitations and Restrictions With ADO and
There are several necessary steps before using compression on partitioned tables with bitmap indexes. → Compression can be performed on several partitions or a complete partitioned heap-organized table. You can do this compression by either defining a complete partitioned table as being compressed, or by defining it on a per-partition level. Partitions without a specific declaration inherit the attribute from the table definition or, if nothing is specified on table level, from the tablespace definition.
A local index is prefixed if it is partitioned on a left prefix of the index columns and the subpartioning… → In a local index, all keys in a particular index partition refer only to rows stored in a single underlying table partition. A local index is created by specifying the LOCAL attribute. Oracle constructs the local index so that it is equipartitioned with the underlying table. Oracle partitions the index on the same columns as the underlying table, creates the same number of partitions or subpartitions,
3.1.7 Partition Pruning Tips → Partition pruning is enhanced to take advantage of zone maps for pruning of complete partitions. Providing enhanced pruning capabilities provides better performance with less resource consumption and shorter time-to-information. A zone map is a independent access structure that can be built for a table. During table scans, zone maps enable you to prune disk blocks of a table and partitions of a partitioned
Global Prefixed (range partitioning only) No Foot 2 Yes Yes A B B → A B, A A Global Prefixed (range partitioning only) No Foot 2 Yes Yes A B B For a unique local nonprefixed index, the partitioning key must be a subset of the index key and cannot be a partial index. Although a global partitioned index may be equipartitioned with the underlying table, Oracle does not take advantage of the partitioning or maintain equipartitioning after partition maintenance operations
The restrictions for parallel DML and direct-path operations are identified in this topic. → Additional considerations when using parallel DML operations are introduced in this topic. When you want to refresh your data warehouse database using parallel insert, update, or delete operations on a data warehouse, there are additional issues to consider when designing the physical database. These considerations do not affect parallel execution operations. These issues are: Parallel DML and Direct-Path
Parallel execution enables the application of multiple CPU and I/O resources to the execution of a single… → Parallel execution is the ability to apply multiple CPU and I/O resources to the execution of a single SQL statement by using multiple processes. This chapter explains how parallel execution works, and how to control, manage, and monitor parallel execution in the Oracle Database. This chapter contains the following sections: Parallel Execution Concepts Setting the Degree of Parallelism In-Memory Parallel
Partitions can be added using partition exchange load (PEL). → Data warehouses store historical data. Important parts of a data warehouse are the data loading and purging. Partitioning is powerful technology that can help data management for data warehouses. This section contains the following topics: Partition Exchange Load Partitioning and Indexes Removing Data from Tables Partitioning and Data Compression See Also: Oracle Database SQL Tuning Guide for information
A global partitioned index is prefixed if it is partitioned on a left prefix of the index columns. → In a global partitioned index, the keys in a particular index partition may refer to rows stored in multiple underlying table partitions or subpartitions. A global index can be range or hash partitioned, though it can be defined on any type of partitioned table. A global index is created by specifying the GLOBAL attribute. The database administrator is responsible for defining the initial partitioning
You can query using a full partition-wise join. → A full partition-wise join divides a large join into smaller joins between a pair of partitions from the two joined tables. To use full partition-wise joins, you must equipartition both tables on their join keys, or use reference partitioning. You can use various partitioning methods to equipartition both tables. These methods are described at a high level in the following topics: Querying a Full
You can modify the default attributes of a table, or for a partition of a composite partitioned table. → The modification of attributes of tables, partitions, and subpartitions is introduced in this topic. About Modifying Default Attributes About Modifying Real Attributes of Partitions 18.104.22.168 About Modifying Default Attributes You can modify the default attributes of a table, or for a partition of a composite partitioned table. When you modify default attributes, the new attributes affect only future
Table Type Index Behavior → You can split the contents of a partition into two new partitions. The SPLIT PARTITION clause of the ALTER TABLE or ALTER INDEX statement is used to redistribute the contents of a partition into two new partitions. Consider doing this when a partition becomes too large and causes backup, recovery, or maintenance operations to take a long time to complete or it is felt that there is simply too much