{"id":9371,"date":"2016-11-19T21:01:36","date_gmt":"2016-11-19T20:01:36","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/12cr2-upgrade-by-unplugplug-in-the-oracle-cloud-service\/"},"modified":"2016-11-19T21:01:36","modified_gmt":"2016-11-19T20:01:36","slug":"12cr2-upgrade-by-unplugplug-in-the-oracle-cloud-service","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/12cr2-upgrade-by-unplugplug-in-the-oracle-cloud-service\/","title":{"rendered":"12cR2: Upgrade by unplug\/plug in the Oracle Cloud Service"},"content":{"rendered":"

By Franck Pachot<\/h2>\n

.<\/p>\n

    \n12.2 is available in the Oracle Public Cloud DBaaS. If you have a 12.1 DBaaS service, there’s no button to upgrade it. I’ll describe all the possible upgrade procedures and the first one, and the most simple, is to create a new DBaaS service in 12.2 and unplug\/plug the PDBs to it.
    \n
    \nHere is my DBaaS in 12.1<\/p>\n
    [oracle@HP121A ~]$ sqlplus \/ as sysdba\n \nSQL*Plus: Release 12.1.0.2.0 Production on Sat Nov 19 14:47:04 2016\n \nCopyright (c) 1982, 2014, Oracle.  All rights reserved.\n \n \nConnected to:\nOracle Database 12c EE High Perf Release 12.1.0.2.0 - 64bit Production\nWith the Partitioning, Oracle Label Security, OLAP, Advanced Analytics\nand Real Application Testing options\n \nSQL> show pdbs\n \n    CON_ID CON_NAME                       OPEN MODE  RESTRICTED\n---------- ------------------------------ ---------- ----------\n         2 PDB$SEED                       READ ONLY  NO\n         3 PDB1                           READ WRITE NO<\/code><\/pre>\n
    Unplug<\/h3>\n
    I close the PDB1 and unplug it.<\/p>\n
    SQL> alter pluggable database PDB1 close;\n \nPluggable database altered.\n \nSQL> alter pluggable database PDB1 unplug into '\/tmp\/PDB1.xml';\n \nPluggable database altered.<\/code><\/pre>\n
    Copy files<\/h3>\n
    I’ve opened ssh between the two VMs and copy the xml file<\/p>\n
    [oracle@HP122A tmp]$ scp 141.144.32.166:\/tmp\/PDB1.xml .\nThe authenticity of host '141.144.32.168 (141.144.32.168)' can't be established.\nRSA key fingerprint is 84:e4:e3:db:67:20:e8:e2:f7:ff:a6:4d:9e:ee:a4:08.\nAre you sure you want to continue connecting (yes\/no)? yes\nWarning: Permanently added '141.144.32.168' (RSA) to the list of known hosts.\nPDB1.xml                                                                                           100% 6118     6.0KB\/s   00:00<\/code><\/pre>\n
    From the xml file I see which files are referenced:<\/p>\n
    [oracle@HP121A ~]$ grep path \/tmp\/PDB1.xml\n      <path>\/u02\/app\/oracle\/oradata\/HP121A\/41A8A48F54195236E0534EC5C40A569E\/datafile\/o1_mf_system_d30owr5v_.dbf<\/path>\n      <path>\/u02\/app\/oracle\/oradata\/HP121A\/41A8A48F54195236E0534EC5C40A569E\/datafile\/o1_mf_sysaux_d30owr69_.dbf<\/path>\n      <path>\/u02\/app\/oracle\/oradata\/HP121A\/41A8A48F54195236E0534EC5C40A569E\/datafile\/o1_mf_temp_d30owr6h_.dbf<\/path><\/code><\/pre>\n
    and copy them<\/p>\n
    [oracle@HP122A tmp]$ scp -r 141.144.32.168:\/u02\/app\/oracle\/oradata\/HP121A\/41A8A48F54195236E0534EC5C40A569E \/u02\/app\/oracle\/oradata\/HP121A\no1_mf_temp_d30owr6h_.dbf                                                                           100%   20MB  20.0MB\/s   00:00\no1_mf_system_d30owr5v_.dbf                                                                         100%  270MB 135.0MB\/s   00:02\no1_mf_sysaux_d30owr69_.dbf                                                                         100%  570MB 114.0MB\/s   00:05<\/code><\/pre>\n
    Plug<\/h3>\n
    It’s only one command to plug it into the 12.2 CDB:<\/p>\n
    [oracle@HP122A tmp]$ sqlplus \/ as sysdba\n \nSQL*Plus: Release 12.2.0.1.0 Production on Sat Nov 19 14:50:26 2016\n \nCopyright (c) 1982, 2016, Oracle.  All rights reserved.\n \nConnected to:\nOracle Database 12c EE High Perf Release 12.2.0.1.0 - 64bit Production\n \nSQL> show pdbs\n \n    CON_ID CON_NAME                       OPEN MODE  RESTRICTED\n---------- ------------------------------ ---------- ----------\n         2 PDB$SEED                       READ ONLY  NO\n \nSQL> create pluggable database PDB1 using '\/tmp\/PDB1.xml';\nPluggable database created.<\/code><\/pre>\n
    At that time, you can drop it from the source but probably you will remove the service once you are sure the migration is ok.<\/p>\n
    Upgrade<\/h3>\n
    That was easy, but that was only the transportation of the PDB to another CDB, but it cannot be opened so easily on a newer version CDB. When we open the PDB we get a warning:<\/p>\n
    SQL> alter pluggable database PDB1 open;\n \nWarning: PDB altered with errors.<\/code><\/pre>\n
    and have to look at the PDB_PLUG_IN_VIOLATIONS<\/p>\n
    SQL> select MESSAGE from pdb_plug_in_violations order by time\n \nMESSAGE\n-----------------------------------------------------------------------------------------------------------\nAPEX mismatch: PDB installed version NULL CDB installed version 5.0.4.00.12\nCDB is using local undo, but no undo tablespace found in the PDB.\nCDB parameter compatible mismatch: Previous '12.1.0.2.0' Current '12.2.0'\nDatabase option APS mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nDatabase option CATALOG mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nDatabase option CATJAVA mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nDatabase option CATPROC mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nDatabase option CONTEXT mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nDatabase option DV mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nDatabase option JAVAVM mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nDatabase option OLS mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nDatabase option ORDIM mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nDatabase option OWM mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nDatabase option SDO mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nDatabase option XDB mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nDatabase option XML mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nDatabase option XOQ mismatch: PDB installed version 12.1.0.2.0. CDB installed version 12.2.0.1.0.\nPDB's version does not match CDB's version: PDB's version 12.1.0.2.0. CDB's version 12.2.0.1.0.<\/code><\/pre>\n
    Each component report a newer version. We have to upgrade them running catupgrd.sql.
    \nIn 12.2 we have a new script that calls the catctl.pl and catupgrd.sql to make this easier. It is a shell script located in ORACLE_HOME\/bin and is dbupgrade<\/b>. As with catcon.pl we have the ‘-c’ argument to run it on PDB1:<\/p>\n
    [oracle@HP122A tmp]$ $ORACLE_HOME\/bin\/dbupgrade -c PDB1<\/code><\/pre>\n
    How long does it take? Documentation says that:
    \nIt is easier to apply a patch to one CDB than to multiple non-CDBs and to upgrade one CDB than to upgrade several non-CDBs.<\/em>
    \nSo this supposes that upgrade work is mostly done at CDB level. PDBs have only metadata links to them. It’s only a virtual dictionary.<\/p>\n
    More than 3 years after the multitenant architecture was released, there are big doubts about the time it takes to upgrade a PDB plugged from a previous version:<\/p>\n
    \n
    #dbupgrade<\/a> @OracleDatabase<\/a>
    Guess how many minutes to catupgrd a 12.1 PDB plugged into an empty 12.2 CDB?
    [ doc says     https:\/\/t.co\/hQTknmKl1y<\/a><\/p>\n
    — Franck Pachot (@FranckPachot) November 19, 2016<\/a><\/p><\/blockquote>\n