Monday, August 17, 2015

Upgrade 12.1.0.1 to 12.1.0.2



UPGRADE 12c Standalone Database
From 12.1.0.1.7 to 12.1.0.2.0

Today I am performing a database upgrade from 12.1.0.1.7 to 12.1.0.2 on RedHat Enterprise 5.10 x64.

In this scenario we have 2 PDBS.
               
  1. E7DB      (Created on 12.1.0.1)
  2. PROD    (Upgraded from 11.2.0.4)

Prior to upgradation I have install 12.1.0.4 binary under /u01/app/oracle/product/12.1.0.2 folder.  I have also created pfile from 12.1.0.1 spfile and move to 12.1.0.2 home under dbs folder.

Also I performed full database backup before upgrade, in case of any disaster.


Go to new installed binary home under <ORACLE_HOME>/bin and run database upgrade assistance.




Upgrade wizard will show how to proceed and what information I have to fill into this.


Select Upgrade Database .



In next wizard I will some warning.  Check on database related to any invalid objects.  Also run the utlrp.sql on database to fix any invalid objects then Click Next



Select the parallelism for upgrade as per your server available resources.  Also I check recompile invalid object during upgrade.




Check the Enterprise manager for database express.



Set the location if required



Select the listener which you want to upgrade



Take the back if you haven’t taken.


Summary




Verify Upgrade results




Verify Upgrade results


Verify in DBA_REGISTRY for upgraded component.

SQL> select substr(comp_id,1,15) comp_id,substr(comp_name,1,30)
  comp_name,substr(version,1,10) version,status
  from dba_registry order by modified;

COMP_ID   COMP_NAME                       VERSION     STATUS
--------- ------------------------------- ----------- ---------
AMD       OLAP Catalog                    11.2.0.4.0  OPTION OF
CATALOG   Oracle Database Catalog Views   12.1.0.2.0  VALID
CATPROC   Oracle Database Packages and T  12.1.0.2.0  VALID
OWM       Oracle Workspace Manager        12.1.0.2.0  VALID
JAVAVM    JServer JAVA Virtual Machine    12.1.0.2.0  VALID
XML       Oracle XDK                      12.1.0.2.0  VALID
CATJAVA   Oracle Database Java Packages   12.1.0.2.0  VALID
CONTEXT   Oracle Text                     12.1.0.2.0  VALID
XDB       Oracle XML Database             12.1.0.2.0  VALID
ORDIM     Oracle Multimedia               12.1.0.2.0  VALID
APS       OLAP Analytic Workspace         12.1.0.2.0  VALID
XOQ       Oracle OLAP API                 12.1.0.2.0  VALID
SDO       Spatial                         12.1.0.2.0  VALID
APEX      Oracle Application Express      4.2.5.00.0  VALID
OWB       OWB                             11.2.0.4.0  VALID

15 rows selected.

SQL> select banner from v$version;

BANNER
--------------------------------------------------------------------------------
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
PL/SQL Release 12.1.0.2.0 - Production
CORE    12.1.0.2.0      Production
TNS for Linux: Version 12.1.0.2.0 - Production
NLSRTL Version 12.1.0.2.0 - Production


SQL> select pdb_name, status, vsn from cdb_pdbs;

PDB_NAME   STATUS           VSN
---------- ------- ------------
E7DB       NORMAL     202375680
PDB$SEED   NORMAL     202375680
PROD       NORMAL     202375680



"OPTION WARNING Database option mismatch: PDB installed version NULL" in PDB_PLUG_IN_VIOLATIONS (Doc ID 2020172.1)  So we can ignore.
APPLIES TO:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and later Information in this document applies to any platform.
SYMPTOMS
After converting a non-CDB to a PDB and running the noncdb_to_pdb.sql script, you see messages of this form in PDB_PLUG_IN_VIOLATIONS.  In this case, the PDB name is "PRDS".

PRDS OPTION WARNING Database option XML mismatch: PDB installed version NULL. CDB installed version 12.1.0.2.0. PENDING Fix the database option in the PDB or the CDB
PRDS OPTION WARNING Database option XOQ mismatch: PDB installed version NULL. CDB installed version 12.1.0.2.0. PENDING Fix the database option in the PDB or the CDB
PRDS APEX WARNING APEX mismatch: PDB installed version NULL CDB installed version 4.2.5.00.08 PENDING Please contact Oracle Support.
 CAUSE
 These messages mean that the option is not installed in the PDB, but is installed in the CDB.
SOLUTION
Some warnings in PDB_PLUG_IN_VIOLATIONS prevent you from actually opening the PDB in READ WRITE mode; this is not one of them.  You can ignore these messages.   It is okay for a PDB to have a subset (fewer) options installed than the CDB into which it is plugged.   (The reverse is NOT true, however -- the CDB must always have the same or more options as its PDBs).   
Unpublished Bug 16192980 : NO SIMPLE WAY TO CLEAN ROWS FROM PDB_PLUG_IN_VIOLATIONS AFTER DBMS_PDB CALL has been filed to request a way to clear out no-impact warnings from PDB_PLUG_IN_VIOLATIONS.  There is no projected date available for when this might be implemented. 
 Note: In this example, the warnings are for the PDB named PRDS.  Do not disregard such warnings about PDB$SEED.  PDB$SEED should not be opened/modified by users.  Oracle tools, such as datapatch, will open/close it as needed.  You need to address warnings of this format for PDB$SEED.


SQL> select time, status, message from pdb_plug_in_violations;

TIME                             STATUS    MESSAGE
-------------------------------- --------- ------------------------------------------------------------------------------------------
15-AUG-15 03.52.52.023089 AM     PENDING   CDB parameter processes mismatch: Previous 300 Current 500
15-AUG-15 03.52.52.033331 AM     PENDING   CDB parameter shared_pool_size mismatch: Previous 838860800 Current 0
15-AUG-15 03.52.52.033383 AM     PENDING   CDB parameter large_pool_size mismatch: Previous 67108864 Current 0
15-AUG-15 03.52.52.033427 AM     PENDING   CDB parameter java_pool_size mismatch: Previous 218103808 Current 0
15-AUG-15 03.52.52.033489 AM     PENDING   CDB parameter db_cache_size mismatch: Previous 16777216 Current 0
15-AUG-15 03.52.52.033569 AM     PENDING   CDB parameter job_queue_processes mismatch: Previous 0 Current 1000
15-AUG-15 03.52.52.033585 AM     PENDING   CDB parameter pga_aggregate_target mismatch: Previous 67108864 Current 0
15-AUG-15 03.52.52.033644 AM     PENDING   CDB parameter statistics_level mismatch: Previous BASIC Current TYPICAL
15-AUG-15 03.56.11.900400 AM     RESOLVED  Character set mismatch: PDB character set US7ASCII CDB character set AL32UTF8.
15-AUG-15 04.53.12.203112 AM     PENDING   Database option DV mismatch: PDB installed version NULL. CDB installed version 12.1.0.1.0.
15-AUG-15 04.53.12.203249 AM     PENDING   Database option OLS mismatch: PDB installed version NULL. CDB installed version 12.1.0.1.0
.

15-AUG-15 04.53.12.203327 AM     PENDING   PDB plugged in is a non-CDB, requires noncdb_to_pdb.sql be run.
15-AUG-15 04.53.12.203505 AM     PENDING   CDB parameter sga_target mismatch: Previous 805306368 Current 0
15-AUG-15 04.53.12.203557 AM     PENDING   CDB parameter memory_target mismatch: Previous 1073741824 Current 1258291200
15-AUG-15 04.53.12.203611 AM     PENDING   CDB parameter compatible mismatch: Previous 11.2.0.4.0 Current 12.1.0.0.0
15-AUG-15 05.02.45.916726 AM     RESOLVED  CDB parameter sga_target mismatch: Previous 805306368 Current 0
15-AUG-15 05.02.45.916726 AM     RESOLVED  CDB parameter memory_target mismatch: Previous 1073741824 Current 1258291200
15-AUG-15 05.02.45.916726 AM     RESOLVED  CDB parameter compatible mismatch: Previous 11.2.0.4.0 Current 12.1.0.0.0
15-AUG-15 05.40.34.838335 AM     RESOLVED  PDB plugged in is a non-CDB, requires noncdb_to_pdb.sql be run.
15-AUG-15 08.32.04.148031 AM     RESOLVED  SQL patch 19769486 mismatch: Installed in the CDB but not in the PDB.
15-AUG-15 08.32.04.148031 AM     RESOLVED  SQL patch 20299016 mismatch: Installed in the CDB but not in the PDB.
15-AUG-15 08.41.14.626661 AM     RESOLVED  SQL patch 19769486 mismatch: Installed in the CDB but not in the PDB.
15-AUG-15 08.41.14.626661 AM     RESOLVED  SQL patch 20299016 mismatch: Installed in the CDB but not in the PDB.
17-AUG-15 08.16.08.602770 AM     RESOLVED  Database option DV mismatch: PDB installed version NULL. CDB installed version 12.1.0.1.0.
17-AUG-15 08.16.08.602770 AM     RESOLVED  Database option OLS mismatch: PDB installed version NULL. CDB installed version 12.1.0.1.0.

17-AUG-15 08.46.49.518344 AM     RESOLVED  PDB's version does not match CDB's version: PDB's version 12.1.0.1.0. CDB's version 12.1.0.2.0.

17-AUG-15 09.06.17.710619 AM     RESOLVED  PDB's version does not match CDB's version: PDB's version 12.1.0.1.0. CDB's version 12.1.0                                          .2.0.

17-AUG-15 09.06.18.788636 AM     RESOLVED  PDB's version does not match CDB's version: PDB's version 12.1.0.1.0. CDB's version 12.1.0.2.0.

17-AUG-15 11.01.43.718986 AM     PENDING   Database option DV mismatch: PDB installed version NULL. CDB installed version 12.1.0.2.0.
17-AUG-15 11.01.43.719594 AM     PENDING   Database option OLS mismatch: PDB installed version NULL. CDB installed version 12.1.0.2.0




No comments:

Post a Comment