Tagged: Oracle database

ORACLE 18C – Autonomous Database Cloud

At Oracle OpenWorld 2017, Oracle Chairman of the Board and CTO Larry Ellison unveiled his vision for the world’s first autonomous database cloud. Powered by Oracle Database 18c, the next generation of the industry-leading database, Oracle Autonomous Database Cloud uses ground- breaking machine learning to enable automation that eliminates human labor, human error and manual tuning, to enable unprecedented availability, high performance and security at a much lower cost. “This is the most important thing we’ve done in a long, long time” said Ellison. “The automation does everything. We can guarantee availability of 99.995 percent, less than 30 minutes of planned...

MODIFICA SQLPROMPT CONTAINER E PLUGGABLE DATABASE

Per impostare il nome dell’istanza sul prompt della macchina e contestualmente il nome utente e il nome dell’istanza in sqlplus eseguiamo con le seguenti modifiche: ENV PDB – Modificare l’export dell’istanza nell’env del PDB inserendo il nome del pluggable database export ISTANZA=RELAUP – Cambiare nell’export della variabile PS1 ORACLE_SID con ISTANZA export PS1='\u@${HOSTNAME}:${ISTANZA} # ' – Inserire l’export della variabile SQLPATH export SQLPATH=/home/oracle12/cfg ENV CDB – Inserire l’unset del SQLPATH, perchè se rimene settata ci si connette al PDB perché esegue il file login.sql all’interno della directory SQLPATH unset SQLPATH Di seguito gli env di GRELAUP e RELAUP: oracle12@lradbpvm01:RELAUP #...

2 PHASE COMMIT OVERVIEW

Two-phase commit protocol is comprised of a set of actions that ensure a transaction involving multiple databases does not produce unsynchronized updates. Two-phase commit provides a way for a series of database interactions on multiple different data sources to be grouped together and completed or rolled back as a single transaction. Two-phase commit transactions that represent a series of database interactions on multiple data sources are referred to as global transactions. At the beginning of a global transaction, a global transaction ID (XID) is generated and used by an external transaction manager to drive the two-phase commit processing across all...

2 PHASE COMMIT OVERVIEW

Two-phase commit protocol is comprised of a set of actions that ensure a transaction involving multiple databases does not produce unsynchronized updates. Two-phase commit provides a way for a series of database interactions on multiple different data sources to be grouped together and completed or rolled back as a single transaction. Two-phase commit transactions that represent a series of database interactions on multiple data sources are referred to as global transactions. At the beginning of a global transaction, a global transaction ID (XID) is generated and used by an external transaction manager to drive the two-phase commit processing across all...

RANGE-PARTITIONED TABLES

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,...

HASH-PARTITIONED TABLES

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...

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...

Interval Partitioning

Partitioning enables you to decompose very large tables and indexes into smaller and more manageable pieces called partitions. Each partition is an independent object with its own name and optionally its own storage. Now in 11g, Oracle introduced new partition type called INTERVAL PARTITIONING The INTERVAL clause of the CREATE TABLE statement establishes interval partitioning for the table. You must specify at least one range partition using the PARTITION clause. The range partitioning key value determines the high value of the range partitions, which is called the transition point, and the database automatically creates interval partitions for data beyond that...

Memory Resource Management for PDBs in Oracle Database 12c Rel.2 (12.2)

In the previous release there was no way to control the amount of memory used by an individual PDB. It could use up lots of memory and impact the performance of other PDBs in the same instance. Oracle Database 12c Rel.2 (12.2) allows to control the amount of memory used by a PDB. PDB Memory Parameters The following parameters can be set at the PDB level. DB_CACHE_SIZE : minimum buffer cache size for the PDB. SHARED_POOL_SIZE : minimum shared pool size for the PDB. PGA_AGGREGATE_LIMIT : maximum PGA size for the PDB. PGA_AGGREGATE_TARGET : target PGA size for the PDB....

Oracle 12c release 2: new features

Oracle introduced the long awaited Database 12c Release 2 earlier this year at OracleOpen World. Oracle just released Oracle Database 12c Release 2 for on-premises Linux and Solaris. Find below an incomplete list of the main new features: 1. Multi-Instance Redo Apply : With Oracle 12c Release 2, you can apply redo logs to multiple instance at the same time to improve recovery time objective. 2. Oracle Database Sharding : With Oracle 12c Release 2, you can horizontally partitioned data across many databases and present them as a single logical database to application. 3. Creating Data Guard Standbys With Database Creation Assistant : You...