This topic contains RANGE-PARTITIONED TABLES that is available since Oracle 8i. 1. RANGE-PARTITIONED TABLES The PARTITION BY RANGE clause of the CREATE TABLE statement specifies that the table or index is to be range-partitioned. The PARTITION clauses identify the individual partition ranges, and the optional sub clauses of a PARTITION clause can specify physical and other attributes specific to a partition segment. Using Reference Partitioning: Range partitioning is useful when you have distinct ranges of data you want to store together. The classic example of this is the use of dates. Here an example: Creates a table of four partitions, Read More


The PARTITION BY HASH clause of the CREATE TABLE statement identifies that the table is to be hash- partitioned. The PARTITIONS clause can then be used to specify the number of partitions to create, and optionally, the tablespaces to store them in. Alternatively, you can use PARTITION clauses to name the individual partitions and their tablespaces. The only attribute you can specify for hash partitions is TABLESPACE. All of the hash partitions of a table must share the same segment attributes (except TABLESPACE), which are inherited from the table level. Using Reference Partitioning: Hash partitioning is useful when there is Read More

Oracle VM 3.4.3

In recent weeks Oracle has released VM 3.4.3 The principal enhancements present in this release are: Installation and Upgrades: – Simplified UEFI PXE Boot for Oracle VM Server Infrastructure: – Support for Software RAID Devices with Oracle VM Server – Support for Microsoft Windows Server Failover Clustering – Update to Oracle VM Agent for SPARC – Update to the dom0 Kernel – Updates to Multipath Configuration for Oracle ZFS Storage Appliance Performance and Scalability: – Improved Job completion performance – Improved Storage refresh performance – Improved Performance With Multiple Concurrent Connections to the Oracle VM Manager Command Line Interface Usability: Read More

Calling an ODI Scenario from APEX

How to call scenario odi from apex application. Instead to open the client to execute the run of the scenario there is possibility to call odi scenario just using a button created into your application front-end apex. Objects to create – Job type PLSQL_BLOCK – Apex button to enable the job indicated Here the source for the button As we developed the following Download the script that contains: – create job – enable the job created Out of scope: – Create scenario propaedeutic for the job, in this case the scenario calls PKG_ALLINEA_CASSE (see ScenarioName tag)