DBORCLOUD Blog

Create Sequence-Oracle Database 12c

Database version : from Oracle Database 12cR1 Create sequence with session or global option When a sequence number is generated, the sequence is incremented, independent of the transaction committing or rolling back. SESSION option makes opportunity to create sequence that can used in association with global temporary table then its visibility is just for session. The following options CACHE, NOCACHE, ORDER, or NOORDER are ignored when SESSION is declared. 1) statement SQL> CREATE GLOBAL TEMPORARY TABLE glb_tmp_table (a number); Table created. SQL> CREATE SEQUENCE sq_sess SESSION; Sequence created. 2) Script execution SQL> INSERT INTO glb_tmp_table VALUES (sq_sess.NEXTVAL); 1 row created. Read More

LIST-PARTITIONED

Introducing the topic: In list partitioning, the database uses a list of discrete values as the partition key for each partition. You can use list partitioning to control how individual rows map to specific partitions. By using lists, you can group and organize related sets of data when the key used to identify them is not conveniently ordered. Here an example: 1. This example shows how the index works Assume that you create list_sales as a list-partitioned table using the following statement. The channel_id column is the partition key. check partition: Table Partition HIGH_VALUE Table Partition MEDIUM_VALUE Table Partition LOWER_VALUE Read More

ORACLE 12 rel.2 – Partitioning new features

In Oracle 12c rel.2 a great number of enhancements to the Oracle database Partitioning option have been introduced. These include: Automatic List Partitioning Filtered Partition maintenance operations Multi-Column List Partitioning Online conversion of non-partitioned to partitioned table Read-only Partitions Partitioned External Tables Automatic List Partitioning: The ability to partition a table based on distinct values in a column has been around since quite some time, but what is new in Oracle database 12.2 is that we can initially partition the table based on values that are known and present in the column we would like to partition the table on. Read More

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 Read More

ORACLE 12C M.T.S. model

Until Oracle Database 12c, Oracle processes did not run as threads on UNIX and Linux systems. Every dedicated connection was represented by an operating system process. In systems where high workload was an issue, the only way to reduce CPU and memory usage was to switch from dedicated connections to shared connections using the multithreaded server (MTS) feature. Starting in Oracle Database 12c the multithreaded database model was introduced, enabling database processes to be executed as operating system threads and reducing the number of dedicated process necessary to manage database services. By default, every new 12c instance is created to Read More

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 # Read More