Only single level list partitioning is supported for HIVE.Īttribute clustering ( CLUSTERING clause) is not allowed.ĭML operations only on internal partitions of a hybrid partitioned table (external partitions are treated as read-only partitions) Only partial indexes are allowed and unique indexes cannot be partial. No unique indexes or global unique indexes. Only single level LIST and RANGE partitioning are supported. No support for REFERENCE and SYSTEM partitioning methods
Restrictions that apply to external tables also apply to hybrid partitioned tables unless explicitly noted The following are restrictions and limitations on hybrid partitioned tables.
Restrictions on Hybrid Partitioned Tables Also, an internal partition can be exchanged with an internal nonpartitioned table. VALIDATE STRUCTURE on internal partitions only on hybrid partitioned tablesĪltering an existing hybrid partitioned table with no external partitions to a partitioned table with internal partitions onlyĪn external partition can be exchanged with an external nonpartitioned table. Modifying for external partitions the location of the external data sources at the partition levelĪltering an existing partitioned internal table to a hybrid partitioned table containing both internal and external partitionsĬhanging the existing location to an empty location resulting in an empty external partitionĬreating global partial non-unique indexes on internal partitionsĬreating materialized views on internal partitionsĬreating materialized views that include external partitions in QUERY_REWRITE_INTEGRITY stale tolerated mode onlyįull partition wise refreshing on external partitionsĭML trigger operations on a hybrid partitioned table on internal partitions DDLs such as ADD, DROP, and RENAME partitions The following are operations supported on hybrid partitioned tables.Ĭreating single level RANGE and LIST partitioning methods Supported Operations on Hybrid Partitioned Tables However, Automatic Data Optimization (ADO) defined on the table level only has an effect on internal partitions of the table. Hybrid partitioned tables provide users with the capability to move data between internal and external partitions for cost effective purposes. Partition-based optimizations include the following across internal and external data sources: Hybrid partitioned tables can use partition-based optimizations across internal and external partitions. To activate optimizations based on these constraints, set the session parameter QUERY_REWRITE_INTEGRITY to TRUSTED or STALE_TOLERATED.
Only constraints in the RELY DISABLE mode, such as NOT NULL, primary key, unique, and foreign-primary key are supported on hybrid partitioned tables. For example, primary or foreign key constraints cannot be enforced on a hybrid partitioned table.
#ORACLE DATABASE PARTITIONING DRIVER#
For external partitions of ORACLE_HIVE and ORACLE_HDFS access driver type, the DEFAULT DIRECTORY is only used to store specifications for log files.Įnforcement of constraints is not supported on data stored in external partitions because the constraints apply to the entire table. You can override the default directory location with a DEFAULT DIRECTORY value in a partition clause. For example, the DEFAULT DIRECTORY value defined in the EXTERNAL PARTITION ATTRIBUTES clause is the default location for data files and logging and bad files. Table-level external parameters apply to all external partitions of hybrid partitioned tables. WRITE privileges on directories with logging and bad filesĮXECUTE privileges on directories with pre-processor programs READ privileges on directories with data files External table types forĮxternal partitions use the following access driver types:įor external partitions of ORACLE_LOADER and ORACLE_DATAPUMP access driver type, you must grant the following privileges to the user: Partitions: ORACLE_DATAPUMP, ORACLE_LOADER, Hybrid partitioned tables support all existing external table types for external On Hadoop Distributed File System (HDFS) with Java server or Object Store on Cloud. Partitions of hybrid partitioned tables can reside on both Oracle tablespaces andĮxternal sources, such as Linux files with comma-separated values (CSV) records, files Using this feature also enables you to easily move non-active partitions to external files for a cheaper storage solution. Hybrid partitioned tables enable you to easily integrate internal partitions and external partitions (those residing on sources outside the database) into a single partition table. Oracle hybrid partitioned tables combine classical internal partitioned tables with Oracle external partitioned tables to form a more general partitioning called hybrid partitioned tables.