2014/04/07

My article on GPO (Grupo de Profissionais Oracle) Portal

GPO (Group Oracle Professionals) - The greater Oracle community in Brazil. GPO portal is a comprehensive portal implemented with various technologies and various topics on Oracle Technologies.
GPO (Grupo de Profissionais Oracle) Portal : http://www.profissionaloracle.com.br/gpo


My article published on GPO (Group Oracle Professionals) portal. 

Mahir M. Quluzade - GPO Profile

Special thank to Victor Armbrust (Founder-Director of the GPO Portal, Oracle ACE), Sergio Willians (Coordinator GPO Portal, Oracle ACE), Alex Zaballa (Autor of GPO, Oracle AСE).

Regards
Mahir M. Quluzade

2014/02/13

Oracle Database 12c: What happens during CDB startup if one the PDB has a media problem? - Continue

During Oracle Day 2014  (February 05, 2014, which was held in Baku/Azerbaijan), I met with my friends and had a conversation about several topics.

I asked to my friend Teymur Hajiyev, what happens during CDB startup if one the PDB has a media problem? He said, CDB must open without a problem. But you need to open PDBs manually. In other words, by default PDBs in mount mode, you need call alter pluggable databases all open.

After Oracle Day, Teymur shared his tests in here. and faced the same issue. But he is wrote : If you apply PSU1 on 12c, you will not meet with such problem, CDB will skip opening problematic PDB and will open other PDBs.

I will share my tests on patched database. I applied PSU1 to my database server:  Installation and configuration Patch 17552800 - 12.1.0.1.2 Patch Set Update

My test environment as below:

[oracle@oel62-ora12c /]$ export ORACLE_SID=prmcdb 
[oracle@oel62-ora12c /]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.1.0 Production on Wed Feb 12 12:53:16 2014

Copyright (c) 1982, 2013, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> select con_id, cdb, name, open_mode from v$database;

    CON_ID CDB NAME  OPEN_MODE
---------- --- --------- --------------------
  0 YES PRMCDB  READ WRITE

SQL> select con_id, name, open_mode from v$pdbs;    

    CON_ID NAME      OPEN_MODE
---------- ------------------------------ ----------
  2 PDB$SEED     READ ONLY
  3 PRMPDB01     READ WRITE
  4 PRMPDB02     READ WRITE

SQL> select file#, name from v$datafile;

     FILE#      NAME
---------------------------------------------------------------
  1  /u01/app/oracle/oradata/prmcdb/system01.dbf
  3  /u01/app/oracle/oradata/prmcdb/sysaux01.dbf
  4  /u01/app/oracle/oradata/prmcdb/undotbs01.dbf
  5  /u01/app/oracle/oradata/prmcdb/pdbseed/system01.dbf
  6  /u01/app/oracle/oradata/prmcdb/users01.dbf
  7  /u01/app/oracle/oradata/prmcdb/pdbseed/sysaux01.dbf
  8  /u01/app/oracle/oradata/prmcdb/prmpdb01/system01.dbf
  9  /u01/app/oracle/oradata/prmcdb/prmpdb01/sysaux01.dbf
 10  /u01/app/oracle/oradata/prmcdb/prmpdb01/prmpdb01_users01.dbf
 11  /u01/app/oracle/oradata/prmcdb/prmpdb02/system01.dbf
 12  /u01/app/oracle/oradata/prmcdb/prmpdb02/sysaux01.dbf
 13  /u01/app/oracle/oradata/prmcdb/prmpdb02/prmpdb02_users01.dbf

SQL> select file#, status, error from  v$datafile_header;

     FILE# STATUS     ERROR
-----------------------------------------------------------------
  1 ONLINE
  3 ONLINE
  4 ONLINE
  5 ONLINE
  6 ONLINE
  7 ONLINE
  8 ONLINE
  9 ONLINE
 10 ONLINE
 11 ONLINE
 12 ONLINE
 13 ONLINE

12 rows selected.

SQL> select *  from dba_registry_history;

ACTION_TIME ACTION NAMESPACE VERSION ID BUNDLE_SERIES COMMENTS
24-MAY-13 01.20.05.485655000 PM APPLY SERVER 12.1.0.1 0 PSU Patchset 12.1.0.0.0
10-FEB-14 06.29.37.412212000 PM APPLY SERVER 12.1.0.1 0 PSU Patchset 12.1.0.0.0
12-FEB-14 09.48.05.383369000 AM APPLY SERVER 12.1.0.1 2 PSU PSU 12.1.0.1.2


SQL> select *  from dba_registry_sqlpatch;

PATCH_ID ACTION STATUS ACTION_TIME DESCRIPTION LOGFILE
17552800 APPLY SUCCESS 12-FEB-14 09.49.00.559171000 AM bundle:PSU /u01/app/oracle/product/12.1.0/dbhome/sqlpatch/17552800/17552800_apply_PRMCDB_CDBROOT_2014Feb12_09_47_49.log

Before everything I take full backup of my database with RMAN.

[oracle@oel62-ora12c /]$ rman target / 

Recovery Manager: Release 12.1.0.1.0 - Production on Wed Feb 12 12:52:32 2014
Copyright (c) 1982, 2013, Oracle and/or its affiliates.  All rights reserved.

connected to target database: PRMCDB (DBID=2504197888)

RMAN> backup database plus archivelog delete all input;

Starting backup at 12-FEB-14
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1

...

Finished backup at 12-FEB-14

Starting Control File and SPFILE Autobackup at 12-FEB-14
piece handle=/u01/app/oracle/fra/PRMCDB/autobackup/2014_02_12/o1_mf_s_839336238_9hpfvkm7_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 12-FEB-14


Backup  finished, I follow our scenario in this database

SQL> ! rm -fr /u01/app/oracle/oradata/prmcdb/prmpdb02/prmpdb02_users01.dbf

SQL> shut immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> 
SQL> startup
ORACLE instance started.

Total System Global Area  801701888 bytes
Fixed Size      2293496 bytes
Variable Size    377487624 bytes
Database Buffers   419430400 bytes
Redo Buffers      2490368 bytes
Database mounted.
Database opened.

Database opened without any error. Now I will open all Pluggable databases.

SQL> alter pluggable database all open;
alter pluggable database all open
*
ERROR at line 1:
ORA-01157: cannot identify/lock data file  - see DBWR trace file

SQL> select name, open_mode from v$pdbs;

NAME          OPEN_MODE
------------------------------ ----------
PDB$SEED         READ ONLY
PRMPDB01         READ WRITE
PRMPDB02         MOUNTED

I get error, but other pluggable database opened and now alert log looks as below:

alter pluggable database all open
Wed Feb 12 15:11:15 2014
Errors in file /u01/app/oracle/diag/rdbms/prmcdb/prmcdb/trace/prmcdb_dbw0_11432.trc:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: '/u01/app/oracle/oradata/prmcdb/prmpdb02/prmpdb02_users01.dbf'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Wed Feb 12 15:11:15 2014
Pdb PRMPDB02 hit error 1157 during open read write and will be closed.
ALTER SYSTEM: Flushing buffer cache inst=0 container=4 local
Wed Feb 12 15:11:15 2014
Errors in file /u01/app/oracle/diag/rdbms/prmcdb/prmcdb/trace/prmcdb_p001_11482.trc:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: '/u01/app/oracle/oradata/prmcdb/prmpdb02/prmpdb02_users01.dbf'
Wed Feb 12 15:11:18 2014
Due to limited space in shared pool (need 6094848 bytes, have 3981120 bytes), limiting Resource Manager entities from 2048 to 32
Opening pdb PRMPDB01 (3) with no Resource Manager plan active
Pluggable database PRMPDB01 opened read write
ORA-1157 signalled during: alter pluggable database all open...
Wed Feb 12 15:11:41 2014
Shared IO Pool defaulting to 24MB. Trying to get it from Buffer Cache for process 11546.

It means, if we apply patch set update (12.1.0.1.2) on Oracle Database 12c, when media failure occurs on a PDB, after startup CDB will open normally. CDB skip opening crashed PDB and other PDBs will open normally, when we call alter pluggable database all open. 
I tried open crashed pluggable database again.

SQL> alter pluggable database prmpdb02 open;
alter pluggable database prmpdb02 open
*
ERROR at line 1:
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13:
'/u01/app/oracle/oradata/prmcdb/prmpdb02/prmpdb02_users01.dbf'

SQL> select file#, status, error from  v$datafile_header;

     FILE# STATUS     ERROR
-----------------------------------------------------------------
  1 ONLINE
  3 ONLINE
  4 ONLINE
  5 ONLINE
  6 ONLINE
  7 ONLINE
  8 ONLINE
  9 ONLINE
 10 ONLINE
 11 ONLINE
 12 ONLINE
 13 ONLINE     FILE NOT FOUND
12 rows selected.


It mean we must restore Pluggable Database.

[oracle@oel62-ora12c ~]$ export ORACLE_SID=prmcdb
[oracle@oel62-ora12c ~]$ rman target / 

Recovery Manager: Release 12.1.0.1.0 - Production on Wed Feb 12 15:26:42 2014

Copyright (c) 1982, 2013, Oracle and/or its affiliates.  All rights reserved.

connected to target database: PRMCDB (DBID=2504197888)

RMAN> restore pluggable database prmpdb02;

Starting restore at 12-FEB-14
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=44 device type=DISK

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00011 to /u01/app/oracle/oradata/prmcdb/prmpdb02/system01.dbf
channel ORA_DISK_1: restoring datafile 00012 to /u01/app/oracle/oradata/prmcdb/prmpdb02/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00013 to /u01/app/oracle/oradata/prmcdb/prmpdb02/prmpdb02_users01.dbf
channel ORA_DISK_1: reading from backup piece /u01/app/oracle/fra/PRMCDB/F231EDEC22372112E043AA38A8C01F0B/backupset/2014_02_12/o1_mf_nnndf_TAG20140212T125307_9hpfs0td_.bkp
channel ORA_DISK_1: piece handle=/u01/app/oracle/fra/PRMCDB/F231EDEC22372112E043AA38A8C01F0B/backupset/2014_02_12/o1_mf_nnndf_TAG20140212T125307_9hpfs0td_.bkp tag=TAG20140212T125307
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:25
Finished restore at 12-FEB-14

RMAN> recover pluggable database prmpdb02;

Starting recover at 12-FEB-14
using channel ORA_DISK_1

starting media recovery
media recovery complete, elapsed time: 00:00:09

Finished recover at 12-FEB-14

RMAN> alter pluggable database prmpdb02 open;

Statement processed

RMAN> select name, open_mode from v$pdbs;

NAME                           OPEN_MODE 
------------------------------ ----------
PDB$SEED                       READ ONLY 
PRMPDB01                       READ WRITE
PRMPDB02                       READ WRITE


Regards
Mahir M. Quluzade

Installation and configuration Patch 17552800 - 12.1.0.1.2 Patch Set Update

Hi,

Patch 17552800 - 12.1.0.1.2 Database Patch Set Update released: January 14, 2014. You can download this PSU  from Oracle My Support. I will show short steps installation and configuration this PSU.

Note: To install the PSU 12.1.0.1.2 patch, the Oracle home must have the 12.1.0.1.0 Database installed. Subsequent PSU patches can be installed on Oracle Database 12.1.0.1.0 or any PSU with a lower 5th numeral version than the one being installed.

1. Download this patch set zip file from support web site and copy to database server.

My Oracle Support

[oracle@oel62-ora12c PSU1]$ pwd
/tmp/oracle/PSU1
[oracle@oel62-ora12c PSU1]$ ls -l
total 67952
-rw-r--r-- 1 oracle oinstall 69580299 Feb 12 09:17 p17552800_121010_Linux-x86-64.zip
[oracle@oel62-ora12c PSU1]$ 

2. Exract patch files from p17552800_121010_Linux-x86-64.zip file.

[oracle@oel62-ora12c PSU1]$ unzip p17552800_121010_Linux-x86-64.zip
Archive:  p17552800_121010_Linux-x86-64.zip
   creating: 17552800/
  inflating: 17552800/README.html   
   creating: 17552800/files/
   creating: 17552800/files/lib/
..........
 inflating: 17552800/etc/config/actions.xml 
  inflating: PatchSearch.xml 

[oracle@oel62-ora12c PSU1]$ cd 17552800
[oracle@oel62-ora12c 17552800]$ ls -l
total 84
drwxr-xr-x 3 oracle oinstall  4096 Jan  3 15:21 etc
drwxr-xr-x 7 oracle oinstall  4096 Jan  3 15:21 files
-rw-rw-r-- 1 oracle oinstall 70222 Jan 14 13:32 README.html
-rw-r--r-- 1 oracle oinstall    21 Jan  3 15:21 README.txt

You  can read all  steps of installation and configuration of PSU from README.html carefully. Read this file carefully. It is very important.

3. Pre-Installation Patch need check environment and Patch-Conflict detection and resolution.

[oracle@oel62-ora12c 17552800]$ echo $PATH
/u01/app/oracle/product/12.1.0/dbhome/bin:/usr/sbin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/oracle/bin
[oracle@oel62-ora12c 17552800]$ export PATH=$PATH:/usr/ccs/bin
[oracle@oel62-ora12c 17552800]$ echo $PATH
/u01/app/oracle/product/12.1.0/dbhome/bin:/usr/sbin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/oracle/bin:/usr/ccs/bin
[oracle@oel62-ora12c 17552800]$

[oracle@oel62-ora12c 17552800]$ /u01/app/oracle/product/12.1.0/dbhome/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -ph ./
Oracle Interim Patch Installer version 12.1.0.1.0
Copyright (c) 2012, Oracle Corporation.  All rights reserved.

PREREQ session

Oracle Home       : /u01/app/oracle/product/12.1.0/dbhome
Central Inventory : /u01/app/oraInventory
   from           : /u01/app/oracle/product/12.1.0/dbhome/oraInst.loc
OPatch version    : 12.1.0.1.0
OUI version       : 12.1.0.1.0
Log file location : /u01/app/oracle/product/12.1.0/dbhome/cfgtoollogs/opatch/opatch2014-02-12_09-42-16AM_1.log

Invoking prereq "checkconflictagainstohwithdetail"

Prereq "checkConflictAgainstOHWithDetail" passed.

OPatch succeeded.
[oracle@oel62-ora12c 17552800]$

4. Apply  patch to  Oracle Database 12c (12.1.0.1.0)

[oracle@oel62-ora12c 17552800]$ $ORACLE_HOME/OPatch/opatch apply

Oracle Interim Patch Installer version 12.1.0.1.0
Copyright (c) 2012, Oracle Corporation.  All rights reserved.

Oracle Home       : /u01/app/oracle/product/12.1.0/dbhome
Central Inventory : /u01/app/oraInventory
   from           : /u01/app/oracle/product/12.1.0/dbhome/oraInst.loc
OPatch version    : 12.1.0.1.0
OUI version       : 12.1.0.1.0
Log file location : /u01/app/oracle/product/12.1.0/dbhome/cfgtoollogs/opatch/17552800_Feb_12_2014_09_42_56/apply2014-02-12_09-42-56AM_1.log

Applying interim patch '17552800' to OH '/u01/app/oracle/product/12.1.0/dbhome'
Verifying environment and performing prerequisite checks...
Patch 17552800: Optional component(s) missing : [ oracle.network.cman, 12.1.0.1.0 ]
All checks passed.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/app/oracle/product/12.1.0/dbhome')


Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files...


Patching component oracle.network.rsf, 12.1.0.1.0...

Patching component oracle.rdbms, 12.1.0.1.0...

Patching component oracle.rdbms.rsf, 12.1.0.1.0...

Patching component oracle.ldap.rsf, 12.1.0.1.0...

Patching component oracle.ldap.rsf.ic, 12.1.0.1.0...

Patching component oracle.rdbms.util, 12.1.0.1.0...

Patching component oracle.rdbms.dbscripts, 12.1.0.1.0...

Patching component oracle.rdbms.rman, 12.1.0.1.0...

Verifying the update...
Patch 17552800 successfully applied
Log file location: /u01/app/oracle/product/12.1.0/dbhome/cfgtoollogs/opatch/17552800_Feb_12_2014_09_42_56/apply2014-02-12_09-42-56AM_1.log

OPatch succeeded.
[oracle@oel62-ora12c 17552800]$

Patch applied successfully.

5. Loading modified SQL Files into the Database

My database is Multitenant Container Database (prmcdb). If your dataabse is Multitenant Container Database, then all PDBs (pluggable databaseses) must be opened READ WRITE mode

[oracle@oel62-ora12c 17552800]$ export ORACLE_SID=prmcdb
[oracle@oel62-ora12c 17552800]$ sqlplus "/ as sysdba"

SQL*Plus: Release 12.1.0.1.0 Production on Wed Feb 12 09:46:21 2014

Copyright (c) 1982, 2013, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> select name , open_mode from v$pdbs;

NAME          OPEN_MODE
------------------------------ ----------
PDB$SEED         READ ONLY
PRMPDB01         READ WRITE
PRMPDB02         READ WRITE

SQL> exit

The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.

[oracle@oel62-ora12c 17552800]$ cd $ORACLE_HOME/OPatch
[oracle@oel62-ora12c OPatch]$ pwd
/u01/app/oracle/product/12.1.0/dbhome/OPatch
[oracle@oel62-ora12c OPatch]$ ./datapatch -verbose
SQL Patching tool version 12.1.0.1.0 on Wed Feb 12 09:47:36 2014
Copyright (c) 2013, Oracle.  All rights reserved.

Connecting to database...OK
Determining current state...
Currently installed SQL Patches:
PDB CDB$ROOT: 
PDB PDB$SEED: 
PDB PRMPDB01: 
PDB PRMPDB02: 
Currently installed C Patches: 17552800
For the following PDBs: CDB$ROOT
Nothing to roll back
The following patches will be applied: 17552800
For the following PDBs: PDB$SEED
Nothing to roll back
The following patches will be applied: 17552800
For the following PDBs: PRMPDB01
Nothing to roll back
The following patches will be applied: 17552800
For the following PDBs: PRMPDB02
Nothing to roll back
The following patches will be applied: 17552800
Adding patches to installation queue...
Installing patches...
Validating logfiles...
Patch 17552800 apply (pdb CDB$ROOT): SUCCESS
logfile: /u01/app/oracle/product/12.1.0/dbhome/sqlpatch/17552800/17552800_apply_PRMCDB_CDBROOT_2014Feb12_09_47_49.log (no errors)
catbundle generate logfile: /u01/app/oracle/cfgtoollogs/catbundle/catbundle_PSU_PRMCDB_CDBROOT_GENERATE_2014Feb12_09_47_50.log (no errors)
catbundle apply logfile: /u01/app/oracle/cfgtoollogs/catbundle/catbundle_PSU_PRMCDB_CDBROOT_APPLY_2014Feb12_09_47_53.log (no errors)
Patch 17552800 apply (pdb PDB$SEED): SUCCESS
logfile: /u01/app/oracle/product/12.1.0/dbhome/sqlpatch/17552800/17552800_apply_PRMCDB_PDBSEED_2014Feb12_09_48_09.log (no errors)
catbundle generate logfile: /u01/app/oracle/cfgtoollogs/catbundle/catbundle_PSU_PRMCDB_PDBSEED_GENERATE_2014Feb12_09_48_11.log (no errors)
catbundle apply logfile: /u01/app/oracle/cfgtoollogs/catbundle/catbundle_PSU_PRMCDB_PDBSEED_APPLY_2014Feb12_09_48_14.log (no errors)
Patch 17552800 apply (pdb PRMPDB01): SUCCESS
logfile: /u01/app/oracle/product/12.1.0/dbhome/sqlpatch/17552800/17552800_apply_PRMCDB_PRMPDB01_2014Feb12_09_48_22.log (no errors)
catbundle generate logfile: /u01/app/oracle/cfgtoollogs/catbundle/catbundle_PSU_PRMCDB_PRMPDB01_GENERATE_2014Feb12_09_48_24.log (no errors)
catbundle apply logfile: /u01/app/oracle/cfgtoollogs/catbundle/catbundle_PSU_PRMCDB_PRMPDB01_APPLY_2014Feb12_09_48_27.log (no errors)
Patch 17552800 apply (pdb PRMPDB02): SUCCESS
logfile: /u01/app/oracle/product/12.1.0/dbhome/sqlpatch/17552800/17552800_apply_PRMCDB_PRMPDB02_2014Feb12_09_48_35.log (no errors)
catbundle generate logfile: /u01/app/oracle/cfgtoollogs/catbundle/catbundle_PSU_PRMCDB_PRMPDB02_GENERATE_2014Feb12_09_48_38.log (no errors)
catbundle apply logfile: /u01/app/oracle/cfgtoollogs/catbundle/catbundle_PSU_PRMCDB_PRMPDB02_APPLY_2014Feb12_09_48_40.log (no errors)
SQL Patching tool complete on Wed Feb 12 09:49:06 2014
[oracle@oel62-ora12c OPatch]$ 

SQL Patching tool completed with no errors. You can check log files in $ORACLE_HOME/sqlpatch/17552800/ for errors.

Note: If you are using the Oracle Recovery Manager catalog, then catalog needs to be upgraded.

6. Check changes in database

SQL> select *  from dba_registry_history;

ACTION_TIME ACTION NAMESPACE VERSION ID BUNDLE_SERIES COMMENTS
24-MAY-13 01.20.05.485655000 PM APPLY SERVER 12.1.0.1 0 PSU Patchset 12.1.0.0.0
10-FEB-14 06.29.37.412212000 PM APPLY SERVER 12.1.0.1 0 PSU Patchset 12.1.0.0.0
12-FEB-14 09.48.05.383369000 AM APPLY SERVER 12.1.0.1 2 PSU PSU 12.1.0.1.2


SQL> select *  from dba_registry_sqlpatch;

PATCH_ID ACTION STATUS ACTION_TIME DESCRIPTION LOGFILE
17552800 APPLY SUCCESS 12-FEB-14 09.49.00.559171000 AM bundle:PSU /u01/app/oracle/product/12.1.0/dbhome/sqlpatch/17552800/17552800_apply_PRMCDB_CDBROOT_2014Feb12_09_47_49.log


Regards
Mahir M. Quluzade

2014/02/03

Oracle ACE Newsletter January 2014

I saw my name in Oracle ACE Newsletter January 2014.




















It is first time, is my name in Oracle ACE Newsletter. I'm very glad.
Thanks to Oracle Technology Network (OTN).

Regards
Mahir M. Quluzade

2014/01/21

OTN Article : Oracle Database 12c – Transporte de “Tablespaces” de “11.2.0.3” a “12.1” ( Parte III )

Oracle Technology Network - OTN (Latina America) published our 5th article in Spanish Language.

Oracle Database 12c – Transporte de “Tablespaces” de “11.2.0.3” a “12.1” ( Parte III ) written by Joel Perez (Oracle ACED) and Mahir M. Quluzade (OCE)

Published : January 2014










You can read article from : http://www.oracle.com/technetwork/es/articles/database-performance/transporte-tablespace-11-a-12-part3-2111105-esa.html


Regards
Mahir M. Quluzade