This article shows how to combine internal and external partitions into a single Hybrid Partitioned Table in Oracle Database 19c. Hybrid partitioned tables support the following external table types for external partitions. In this article we'll focus on the and examples. Hybrid partitioned tables support the following external table types for external partitions. - In this article we'll focus on the and examples. Hybrid partitioned tables support the following external table types for external partitions. - In this article we'll focus on the and examples. - Setup - Create Hybrid Partitioned Table (ORACLE_LOADER) - Create Hybrid Partitioned Table (ORACLE_DATAPUMP) - Add/Drop Partitions - Restrictions Related articles. Connect to a privileged user and create a new test user called . Create two new directory objects, making sure has , and permissions on them. All other actions will be performed from . Generate some flat files with dummy data for use with external table partitions. The following example creates a hybrid partitioned table. It uses list partitioning, with a single internal partition for USA data, and two external partitions for GBR and IRE data respectively. The clause defines the table-level external table parameters. For external partitions, the clause is used to define partition-level attributes, such as file locations and non-default directory objects. The column in the views show this is a hybrid table. We only have data in the external partitions at the moment. We can perform DML on the internal partition as normal. As you might expect, trying to insert into the external partitions results in an error. The full list of supported operations can be found in the Hybrid Partitioned Tables document. We create a dump file called "bgr_xt.dmp" containing BGR data. Creating the external table generates the Data Pump dump file. When we drop the table the dump file remains on the database file system, so we can use it for our test. The following example creates a hybrid partitioned table. It uses list partitioning, with a single internal partition for USA data, and a data pump external partitions for BGR data. The clause defines the table-level Data Pump external table parameters. For external partitions, the clause is used to define partition-level attributes, such as file locations and non-default directory objects. The column in the views show this is a hybrid table. We only have data in the external partitions at the moment. We can perform DML on the internal partition as normal. As you might expect, trying to insert into the external partitions results in an error. The full list of supported operations can be found in the Hybrid Partitioned Tables document. We can add and drop partitions in a normal manner. We drop the partition for the IRE data from the table. We add back the partition for the IRE data. We drop the partition for the BGR data from the table. We add back the partition for the BGR data. The operations on the internal partitions are as you would expect to regular partitioned tables. The full list of supported operations can be found in the Hybrid Partitioned Tables document. The standout restrictions are as follows. - You can only use or partitioning. - There is no support for and partitioning. Most of the other restrictions are what you would expect for the various types of partitions. The full list of restrictions can be found in the Hybrid Partitioned Tables document. For more information see: Hope this helps. Regards Tim...