| « PREVIOUS « |
MAIN INDEX 19C HOL | » FALLBACK » |
In this part of the Hands-On Lab you will now unplug an Oracle 12.2.0.1 pluggable database (PDB) from CDB1 and plug it into 19c’s CDB2, including all the necessary steps.
Index
1. Preparation work in CDB1
The PDB3 we will use in this part of the lab is created already in CDB1 – but you need to startup CDB1 and PDB3.
. cdb1
sqlplus / as sysdba
startup
alter pluggable database pdb3 open;
show pdbs
exit
2. Preupgrade.jar and Unplug
Run the preupgrade.jar but only on container PDB3
java -jar $OH19/rdbms/admin/preupgrade.jar -c 'pdb3' TERMINAL TEXT
This will execute preupgrade.jar only in container “PDB3”.
Follow the advice of preupgrade.jar‘s output. You can leave all underscore parameters in
Be aware: If you’d remove for instance the _fix_control, you’d remove this setting for the entire CDB. This would affect other PDBs as well which may still remain in the 12.2.0.1 environment. That’s why we will leave all underscores as is.
Open a second terminal window (or a new tab in your existing one) and logon at first to CDB$ROOT. Then change to PDB3 to complete the steps recommended by preupgrade.jar.
. cdb1
sqlplus / as sysdba
alter session set container=PDB3;
@/u01/app/oracle/cfgtoollogs/CDB1/preupgrade/preupgrade_fixups.sql
alter session set container=CDB$ROOT;
alter pluggable database PDB3 close;
alter pluggable database PDB3 unplug into '/home/oracle/pdb3.pdb';
drop pluggable database PDB3 including datafiles;
Unplugging into a *.pdp does create a zip archive including all necessary files. It will take 30 seconds or more.
shutdown immediate
exit
3. Plugin
In this step you’ll plugin PDB3 into CDB2.
. cdb2
sqlplus / as sysdba
At first, you’ll do a compatibility check and find out, why the action is classified as “not compatible”:
SET SERVEROUTPUT ON
DECLARE
compatible CONSTANT VARCHAR2(3) := CASE DBMS_PDB.CHECK_PLUG_COMPATIBILITY(
pdb_descr_file => '/home/oracle/pdb3.pdb',
pdb_name => 'PDB3')
WHEN TRUE THEN 'YES' ELSE 'NO'
END;
BEGIN
DBMS_OUTPUT.PUT_LINE(compatible);
END;
/
If the result is “NO“, check PDB_PLUG_IN_VIOLATIONS for the reason:
select message from pdb_plug_in_violations where type like '%ERR%' and status <> 'RESOLVED';
You receive two messages:
SQL> select message from pdb_plug_in_violations where type like '%ERR%' and status <> 'RESOLVED'; MESSAGE -------------------------------------------------------------------------------- PDB's version does not match CDB's version: PDB's version 12.2.0.1.0. CDB's vers ion 19.0.0.0.0. DBRU bundle patch 190416 (DATABASE APR 2019 RELEASE UPDATE 12.2.0.1.190416): Not installed in the CDB but installed in the PDB '19.3.0.0.0 Release_Update 1904101227' is installed in the CDB but no release up dates are installed in the PDB
The first one is correct and makes sense. The second and third one can be ignored as it doesn’t matter if PDB3 has a different patch level in 12.2.0.1 – you will upgrade it to 19c anyway. You may read a bit more about PDB_PLUG_IN_VIOLATIONS here.
Plugin the PDB3, the open it in UPGRADE mode:
create pluggable database pdb3 using '/home/oracle/pdb3.pdb' file_name_convert=('/home/oracle', '/u02/oradata/CDB2/pdb3');
alter pluggable database PDB3 open upgrade;
exit
4. Upgrade PDB3
As final action, as a PDB has its own data dictionary, you need to upgrade PDB3 now.
. cdb2
dbupgrade -c 'PDB3' -l /home/oracle/logs -n 2
Once the upgrade has been completed, you need to recompile and run the postupgrade_fixups.sql as usual:
. cdb2
alter session set container=PDB3;
startup
@?/rdbms/admin/utlrp.sql
@/u01/app/oracle/cfgtoollogs/CDB1/preupgrade/postupgrade_fixups.sql
alter session set container=CDB$ROOT;
show pdbs
exit
Done.
If you’d like, you can now try some fallback exercises. For this part of the lab you should restore the initial snapshot again.
Mark the initial snapshot in the VirtualBox Manager with the mouse <click>:
Then <click> on the Restore icon.
| « PREVIOUS « |
MAIN INDEX 19C HOL | » FALLBACK » |
