preupgrade.jar for Oracle Database 12c release 2 (12.2)
Oracle Doc Link ....
https://docs.oracle.com/database/122/UPGRD/using-preupgrade-information-tool-for-oracle-database.htm#UPGRD-GUID-C0219AF1-AD43-4097-B358-E53E48958647
About the Pre-Upgrade Information Tool
The Pre-Upgrade Information Tool is revised and enhanced in Oracle Database 12c release 2 (12.2). You must run this tool to check your earlier release
Oracle Database to determine if it is ready for upgrading to the new release.
preupgrd.sql & utluppkg.sql are deprecated in Oracle Database 12c release 2 (12.2)
Metalink 884522.1 – Download and Run Oracle’s Database Pre-Upgrade Utility
old home = /u01/app/oracle/product/12.1.0.2/db_1
New Home = /u02/app/oracle/product/12.2.0.1/db_1
if required ..
export TWO_TASK=
Command to run ...
[oracle@vbgeneric admin]$ /u01/app/oracle/product/12.1.0.2/db_1/jdk/bin/java -jar /u02/app/oracle/product/12.2.0.1/db_1/rdbms/admin/preupgrade.jar TEXT TERMINAL
Report generated by Oracle Database Pre-Upgrade Information Tool Version
12.2.0.1.0
Upgrade-To version: 12.2.0.1.0
=======================================
Status of the database prior to upgrade
=======================================
Database Name: ORCL12C
Container Name: CDB$ROOT
Container ID: 1
Version: 12.1.0.2.0
Compatible: 12.1.0.2.0
Blocksize: 8192
Platform: Linux x86 64-bit
Timezone File: 18
Database log mode: ARCHIVELOG
Readonly: FALSE
Edition: EE
Oracle Component Upgrade Action Current Status
---------------- -------------- --------------
Oracle Server [to be upgraded] VALID
JServer JAVA Virtual Machine [to be upgraded] VALID
Oracle XDK for Java [to be upgraded] VALID
Real Application Clusters [to be upgraded] OPTION OFF
Oracle Workspace Manager [to be upgraded] VALID
OLAP Analytic Workspace [to be upgraded] VALID
Oracle Label Security [to be upgraded] VALID
Oracle Database Vault [to be upgraded] VALID
Oracle Text [to be upgraded] VALID
Oracle XML Database [to be upgraded] VALID
Oracle Java Packages [to be upgraded] VALID
Oracle Multimedia [to be upgraded] VALID
Oracle Spatial [to be upgraded] VALID
Oracle OLAP API [to be upgraded] VALID
==============
BEFORE UPGRADE
==============
Run <preupgradeLogDirPath>/preupgrade_fixups_CDB_ROOT.sql to complete all
of the BEFORE UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
+ Adjust TABLESPACE SIZES as needed.
Auto 12.2.0.1.0
Tablespace Size Extend Min Size Action
---------- ---------- -------- ---------- ------
SYSAUX 880 MB ENABLED 902 MB None
SYSTEM 800 MB ENABLED 1244 MB None
TEMP 197 MB DISABLED 150 MB None
UNDOTBS2 100 MB ENABLED 400 MB None
Note that 12.2.0.1.0 minimum sizes are estimates.
If you plan to upgrade multiple pluggable databases concurrently,
then you must ensure that the UNDO tablespace size is equal to at least
the number of pluggable databases that you upgrade concurrently,
multiplied by that minimum. Failing to allocate sufficient space can
cause the upgrade to fail.
+ Update NUMERIC INITIALIZATION PARAMETERS to meet estimated minimums.
Parameter 12.2.0.1.0 minimum
--------- ------------------
memory_target* 3594518528
* These minimum memory/pool sizes are recommended for the upgrade process
+ REMOVE the following OBSOLETE initialization parameters.
Parameter
------------------------------
exclude_seed_cdb_view
+ (AUTOFIXUP) Empty the RECYCLEBIN immediately before database upgrade.
The database contains 6 objects in the recycle bin.
The recycle bin must be completely empty before database upgrade.
RECOMMENDED ACTIONS
===================
+ Review and remove any unnecessary HIDDEN/UNDERSCORE parameters.
The database contains the following initialization parameters whose name
begins with an underscore:
_catalog_foreign_restore
_ash_size
Remove hidden parameters before database upgrade unless your application
vendors and/or Oracle Support state differently. Changes will need to
be made in the spfile.
+ (AUTOFIXUP) Gather stale data dictionary statistics prior to database
upgrade in off-peak time using:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Dictionary statistics do not exist or are stale (not up-to-date).
Dictionary statistics help the Oracle optimizer find efficient SQL
execution plans and are essential for proper upgrade timing. Oracle
recommends gathering dictionary statistics in the last 24 hours before
database upgrade.
For information on managing optimizer statistics, refer to the 12.1.0.2
Oracle Database SQL Tuning Guide.
INFORMATION ONLY
================
+ Ensure there is additional disk space in LOG_ARCHIVE_DEST_1 for at least
18 GB of archived logs. Check alert log during the upgrade that there
is no write error to the destination due to lack of disk space. Execute
'archive log list' and query v$archive_dest for more
LOG_ARCHIVE_DEST_<N> destinations to check.
Archiving cannot proceed if the archive log destination is full during
upgrade.
Archive Log Destination:
Parameter : LOG_ARCHIVE_DEST_1
Destination : /u01/app/oracle/Archive
The database has archiving enabled and LOG_ARCHIVE_DEST_<N> set. The
upgrade process will need free disk space in the archive log
destination(s) to generate archived logs to.
=============
AFTER UPGRADE
=============
Run <preupgradeLogDirPath>/postupgrade_fixups_CDB_ROOT.sql to complete all
of the AFTER UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
None
RECOMMENDED ACTIONS
===================
+ Upgrade the database time zone version using the DBMS_DST package.
The database is using timezone datafile version 18 and the target
12.2.0.1.0 database ships with timezone datafile version 26.
Oracle recommends using the most recent timezone data. For further
information, refer to My Oracle Support Note 1585343.1.
+ (AUTOFIXUP) Gather dictionary statistics after the upgrade using the
command:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Oracle recommends gathering dictionary statistics after upgrade.
Dictionary statistics provide essential information to the Oracle
optimizer to help it find efficient SQL execution plans. After a
database upgrade, statistics need to be re-gathered as there can now be
tables that have significantly changed during the upgrade or new tables
that do not have statistics gathered yet.
Report generated by Oracle Database Pre-Upgrade Information Tool Version
12.2.0.1.0
Upgrade-To version: 12.2.0.1.0
=======================================
Status of the database prior to upgrade
=======================================
Database Name: ORCL12C
Container Name: PDB$SEED
Container ID: 2
Version: 12.1.0.2.0
Compatible: 12.1.0.2.0
Blocksize: 8192
Platform: Linux x86 64-bit
Timezone File: 18
Database log mode: ARCHIVELOG
Readonly: TRUE
Edition: EE
Oracle Component Upgrade Action Current Status
---------------- -------------- --------------
Oracle Server [to be upgraded] VALID
JServer JAVA Virtual Machine [to be upgraded] VALID
Oracle XDK for Java [to be upgraded] VALID
Real Application Clusters [to be upgraded] OPTION OFF
Oracle Workspace Manager [to be upgraded] VALID
OLAP Analytic Workspace [to be upgraded] VALID
Oracle Label Security [to be upgraded] VALID
Oracle Database Vault [to be upgraded] VALID
Oracle Text [to be upgraded] VALID
Oracle XML Database [to be upgraded] VALID
Oracle Java Packages [to be upgraded] VALID
Oracle Multimedia [to be upgraded] VALID
Oracle Spatial [to be upgraded] VALID
Oracle OLAP API [to be upgraded] VALID
==============
BEFORE UPGRADE
==============
Run <preupgradeLogDirPath>/preupgrade_fixups_PDB_SEED.sql to complete all
of the BEFORE UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
+ Adjust TABLESPACE SIZES as needed.
Auto 12.2.0.1.0
Tablespace Size Extend Min Size Action
---------- ---------- -------- ---------- ------
SYSAUX 740 MB DISABLED 716 MB None
SYSTEM 260 MB ENABLED 696 MB None
TEMP 100 MB ENABLED 150 MB None
Note that 12.2.0.1.0 minimum sizes are estimates.
If you plan to upgrade multiple pluggable databases concurrently,
then you must ensure that the UNDO tablespace size is equal to at least
the number of pluggable databases that you upgrade concurrently,
multiplied by that minimum. Failing to allocate sufficient space can
cause the upgrade to fail.
+ REMOVE the following OBSOLETE initialization parameters.
Parameter
------------------------------
exclude_seed_cdb_view
RECOMMENDED ACTIONS
===================
+ Run 12.1.0.2.0 $ORACLE_HOME/rdbms/admin/utlrp.sql to recompile invalid
objects. You can view the individual invalid objects with
SET SERVEROUTPUT ON;
EXECUTE DBMS_PREUP.INVALID_OBJECTS;
2 objects are INVALID.
There should be no INVALID objects in SYS/SYSTEM or user schemas before
database upgrade.
+ Review and remove any unnecessary HIDDEN/UNDERSCORE parameters.
The database contains the following initialization parameters whose name
begins with an underscore:
_catalog_foreign_restore
_ash_size
Remove hidden parameters before database upgrade unless your application
vendors and/or Oracle Support state differently. Changes will need to
be made in the spfile.
+ (AUTOFIXUP) Gather stale data dictionary statistics prior to database
upgrade in off-peak time using:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Dictionary statistics do not exist or are stale (not up-to-date).
Dictionary statistics help the Oracle optimizer find efficient SQL
execution plans and are essential for proper upgrade timing. Oracle
recommends gathering dictionary statistics in the last 24 hours before
database upgrade.
For information on managing optimizer statistics, refer to the 12.1.0.2
Oracle Database SQL Tuning Guide.
=============
AFTER UPGRADE
=============
Run <preupgradeLogDirPath>/postupgrade_fixups_PDB_SEED.sql to complete all
of the AFTER UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
None
RECOMMENDED ACTIONS
===================
+ Upgrade the database time zone version using the DBMS_DST package.
The database is using timezone datafile version 18 and the target
12.2.0.1.0 database ships with timezone datafile version 26.
Oracle recommends using the most recent timezone data. For further
information, refer to My Oracle Support Note 1585343.1.
+ (AUTOFIXUP) Gather dictionary statistics after the upgrade using the
command:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Oracle recommends gathering dictionary statistics after upgrade.
Dictionary statistics provide essential information to the Oracle
optimizer to help it find efficient SQL execution plans. After a
database upgrade, statistics need to be re-gathered as there can now be
tables that have significantly changed during the upgrade or new tables
that do not have statistics gathered yet.
Report generated by Oracle Database Pre-Upgrade Information Tool Version
12.2.0.1.0
Upgrade-To version: 12.2.0.1.0
=======================================
Status of the database prior to upgrade
=======================================
Database Name: ORCL12C
Container Name: ORCL
Container ID: 3
Version: 12.1.0.2.0
Compatible: 12.1.0.2.0
Blocksize: 8192
Platform: Linux x86 64-bit
Timezone File: 18
Database log mode: ARCHIVELOG
Readonly: FALSE
Edition: EE
Oracle Component Upgrade Action Current Status
---------------- -------------- --------------
Oracle Server [to be upgraded] VALID
JServer JAVA Virtual Machine [to be upgraded] VALID
Oracle XDK for Java [to be upgraded] VALID
Real Application Clusters [to be upgraded] OPTION OFF
Oracle Workspace Manager [to be upgraded] VALID
OLAP Analytic Workspace [to be upgraded] VALID
Oracle Label Security [to be upgraded] VALID
Oracle Database Vault [to be upgraded] VALID
Oracle Text [to be upgraded] VALID
Oracle XML Database [to be upgraded] VALID
Oracle Java Packages [to be upgraded] VALID
Oracle Multimedia [to be upgraded] VALID
Oracle Spatial [to be upgraded] VALID
Oracle Application Express [to be upgraded] VALID
Oracle OLAP API [to be upgraded] VALID
==============
BEFORE UPGRADE
==============
Run <preupgradeLogDirPath>/preupgrade_fixups_ORCL.sql to complete all
of the BEFORE UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
+ Adjust TABLESPACE SIZES as needed.
Auto 12.2.0.1.0
Tablespace Size Extend Min Size Action
---------- ---------- -------- ---------- ------
EXAMPLE 1244 MB DISABLED 1217 MB None
SYSAUX 1220 MB ENABLED 2095 MB None
SYSTEM 410 MB ENABLED 911 MB None
TEMP 197 MB DISABLED 150 MB None
USERS 150 MB DISABLED 148 MB None
Note that 12.2.0.1.0 minimum sizes are estimates.
If you plan to upgrade multiple pluggable databases concurrently,
then you must ensure that the UNDO tablespace size is equal to at least
the number of pluggable databases that you upgrade concurrently,
multiplied by that minimum. Failing to allocate sufficient space can
cause the upgrade to fail.
+ REMOVE the following OBSOLETE initialization parameters.
Parameter
------------------------------
exclude_seed_cdb_view
+ (AUTOFIXUP) Empty the RECYCLEBIN immediately before database upgrade.
The database contains 7 objects in the recycle bin.
The recycle bin must be completely empty before database upgrade.
+ Set the OPEN_CURSORS initialization parameter to at least 150 before
upgrading the database.
The OPEN_CURSORS initialization parameter is set to 50.
The OPEN_CURSORS initialization parameter must be set to a minimum of
150 to avoid exceeding number of open cursors during Oracle Application
Express (APEX) upgrade.
Note that updating the PFILE/SPFILE will not take effect until the next
database startup.
RECOMMENDED ACTIONS
===================
+ Run 12.1.0.2.0 $ORACLE_HOME/rdbms/admin/utlrp.sql to recompile invalid
objects. You can view the individual invalid objects with
SET SERVEROUTPUT ON;
EXECUTE DBMS_PREUP.INVALID_OBJECTS;
492 objects are INVALID.
There should be no INVALID objects in SYS/SYSTEM or user schemas before
database upgrade.
+ Review and remove any unnecessary HIDDEN/UNDERSCORE parameters.
The database contains the following initialization parameters whose name
begins with an underscore:
_catalog_foreign_restore
_ash_size
Remove hidden parameters before database upgrade unless your application
vendors and/or Oracle Support state differently. Changes will need to
be made in the spfile.
+ (AUTOFIXUP) Gather stale data dictionary statistics prior to database
upgrade in off-peak time using:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Dictionary statistics do not exist or are stale (not up-to-date).
Dictionary statistics help the Oracle optimizer find efficient SQL
execution plans and are essential for proper upgrade timing. Oracle
recommends gathering dictionary statistics in the last 24 hours before
database upgrade.
For information on managing optimizer statistics, refer to the 12.1.0.2
Oracle Database SQL Tuning Guide.
+ Please make sure that all the MVs are refreshed and sys.sumdelta$
becomes empty before doing upgrade, unless you have strong business
reasons not to do so. You can use dbms_mview.refresh() to refresh the
MVs except those stale ones to be kept due to business need. If there
are any stale MVs depending on changes in sys.sumdelta$, do not truncate
it, because doing so will cause wrong results after refresh.
There is one or more non-fresh MV in the database or sumdelta$ is not
empty.
Oracle recommends that all materialized views (MV's) are refreshed
before upgrading the database because this will clear the MV logs and
the sumdelta$ table, and make the UPGRADE process faster. If you choose
to not refresh some MVs, the change data for those MV's will be carried
through the UPGRADE process. After UPGRADE, you can refresh the MV's and
MV incremental refresh should work in normal cases.
=============
AFTER UPGRADE
=============
Run <preupgradeLogDirPath>/postupgrade_fixups_ORCL.sql to complete all
of the AFTER UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
None
RECOMMENDED ACTIONS
===================
+ If you use the -T option for the database upgrade, then run
$ORACLE_HOME/rdbms/admin/utluptabdata.sql after the upgrade is complete,
to VALIDATE and UPGRADE any user tables affected by changes to
Oracle-Maintained types.
There are user tables dependent on Oracle-Maintained object types.
If the -T option is used to set user tablespaces to READ ONLY during the
upgrade, user tables in those tablespaces, that are dependent on
Oracle-Maintained types, will not be automatically upgraded. If a type
is evolved during the upgrade, any dependent tables need to be
re-validated and upgraded to the latest type version AFTER the database
upgrade completes.
+ Upgrade the database time zone version using the DBMS_DST package.
The database is using timezone datafile version 18 and the target
12.2.0.1.0 database ships with timezone datafile version 26.
Oracle recommends using the most recent timezone data. For further
information, refer to My Oracle Support Note 1585343.1.
+ Patch your APEX software from version 5.0.3.00.03 to at least version
5.0.4.00.12.
Your existing version of APEX (5.0.3.00.03) does not require upgrade,
but may still need manual APEX patching.
The APEX patching process is not performed by the 12.1.0.2.0 Oracle
database upgrade. The APEX version upgrade only ensures that the APEX
version is upgraded to version 5.0 and does not guarantee the version is
brought all the way to the patched level 5.0.4.00.12. If a PDB from
this CDB is unplugged and plugged into another ROOT, the plugin process
may require the PDB to be at the patched level 5.0.4.00.12. That
patching process, if desired, must be performed manually. See My Oracle
Support Note 1088970.1 for more details.
+ (AUTOFIXUP) Gather dictionary statistics after the upgrade using the
command:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Oracle recommends gathering dictionary statistics after upgrade.
Dictionary statistics provide essential information to the Oracle
optimizer to help it find efficient SQL execution plans. After a
database upgrade, statistics need to be re-gathered as there can now be
tables that have significantly changed during the upgrade or new tables
that do not have statistics gathered yet.
Report generated by Oracle Database Pre-Upgrade Information Tool Version
12.2.0.1.0
Upgrade-To version: 12.2.0.1.0
=======================================
Status of the database prior to upgrade
=======================================
Database Name: ORCL12C
Container Name: ORDS
Container ID: 4
Version: 12.1.0.2.0
Compatible: 12.1.0.2.0
Blocksize: 8192
Platform: Linux x86 64-bit
Timezone File: 18
Database log mode: ARCHIVELOG
Readonly: FALSE
Edition: EE
Oracle Component Upgrade Action Current Status
---------------- -------------- --------------
Oracle Server [to be upgraded] VALID
JServer JAVA Virtual Machine [to be upgraded] VALID
Oracle XDK for Java [to be upgraded] VALID
Real Application Clusters [to be upgraded] OPTION OFF
Oracle Workspace Manager [to be upgraded] VALID
OLAP Analytic Workspace [to be upgraded] VALID
Oracle Label Security [to be upgraded] VALID
Oracle Database Vault [to be upgraded] VALID
Oracle Text [to be upgraded] VALID
Oracle XML Database [to be upgraded] VALID
Oracle Java Packages [to be upgraded] VALID
Oracle Multimedia [to be upgraded] VALID
Oracle Spatial [to be upgraded] VALID
Oracle OLAP API [to be upgraded] VALID
==============
BEFORE UPGRADE
==============
Run <preupgradeLogDirPath>/preupgrade_fixups_ORDS.sql to complete all
of the BEFORE UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
+ Adjust TABLESPACE SIZES as needed.
Auto 12.2.0.1.0
Tablespace Size Extend Min Size Action
---------- ---------- -------- ---------- ------
SYSAUX 740 MB DISABLED 724 MB None
SYSTEM 260 MB ENABLED 699 MB None
TEMP 20 MB ENABLED 150 MB None
Note that 12.2.0.1.0 minimum sizes are estimates.
If you plan to upgrade multiple pluggable databases concurrently,
then you must ensure that the UNDO tablespace size is equal to at least
the number of pluggable databases that you upgrade concurrently,
multiplied by that minimum. Failing to allocate sufficient space can
cause the upgrade to fail.
+ REMOVE the following OBSOLETE initialization parameters.
Parameter
------------------------------
exclude_seed_cdb_view
+ (AUTOFIXUP) Empty the RECYCLEBIN immediately before database upgrade.
The database contains 7 objects in the recycle bin.
The recycle bin must be completely empty before database upgrade.
RECOMMENDED ACTIONS
===================
+ Run 12.1.0.2.0 $ORACLE_HOME/rdbms/admin/utlrp.sql to recompile invalid
objects. You can view the individual invalid objects with
SET SERVEROUTPUT ON;
EXECUTE DBMS_PREUP.INVALID_OBJECTS;
2 objects are INVALID.
There should be no INVALID objects in SYS/SYSTEM or user schemas before
database upgrade.
+ Review and remove any unnecessary HIDDEN/UNDERSCORE parameters.
The database contains the following initialization parameters whose name
begins with an underscore:
_catalog_foreign_restore
_ash_size
Remove hidden parameters before database upgrade unless your application
vendors and/or Oracle Support state differently. Changes will need to
be made in the spfile.
+ (AUTOFIXUP) Gather stale data dictionary statistics prior to database
upgrade in off-peak time using:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Dictionary statistics do not exist or are stale (not up-to-date).
Dictionary statistics help the Oracle optimizer find efficient SQL
execution plans and are essential for proper upgrade timing. Oracle
recommends gathering dictionary statistics in the last 24 hours before
database upgrade.
For information on managing optimizer statistics, refer to the 12.1.0.2
Oracle Database SQL Tuning Guide.
=============
AFTER UPGRADE
=============
Run <preupgradeLogDirPath>/postupgrade_fixups_ORDS.sql to complete all
of the AFTER UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
None
RECOMMENDED ACTIONS
===================
+ Upgrade the database time zone version using the DBMS_DST package.
The database is using timezone datafile version 18 and the target
12.2.0.1.0 database ships with timezone datafile version 26.
Oracle recommends using the most recent timezone data. For further
information, refer to My Oracle Support Note 1585343.1.
+ (AUTOFIXUP) Gather dictionary statistics after the upgrade using the
command:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Oracle recommends gathering dictionary statistics after upgrade.
Dictionary statistics provide essential information to the Oracle
optimizer to help it find efficient SQL execution plans. After a
database upgrade, statistics need to be re-gathered as there can now be
tables that have significantly changed during the upgrade or new tables
that do not have statistics gathered yet.
Report generated by Oracle Database Pre-Upgrade Information Tool Version
12.2.0.1.0
Upgrade-To version: 12.2.0.1.0
=======================================
Status of the database prior to upgrade
=======================================
Database Name: ORCL12C
Container Name: ANUJ
Container ID: 5
Version: 12.1.0.2.0
Compatible: 12.1.0.2.0
Blocksize: 8192
Platform: Linux x86 64-bit
Timezone File: 18
Database log mode: ARCHIVELOG
Readonly: FALSE
Edition: EE
Oracle Component Upgrade Action Current Status
---------------- -------------- --------------
Oracle Server [to be upgraded] VALID
JServer JAVA Virtual Machine [to be upgraded] VALID
Oracle XDK for Java [to be upgraded] VALID
Real Application Clusters [to be upgraded] OPTION OFF
Oracle Workspace Manager [to be upgraded] VALID
OLAP Analytic Workspace [to be upgraded] VALID
Oracle Label Security [to be upgraded] VALID
Oracle Database Vault [to be upgraded] VALID
Oracle Text [to be upgraded] VALID
Oracle XML Database [to be upgraded] VALID
Oracle Java Packages [to be upgraded] VALID
Oracle Multimedia [to be upgraded] VALID
Oracle Spatial [to be upgraded] VALID
Oracle OLAP API [to be upgraded] VALID
==============
BEFORE UPGRADE
==============
Run <preupgradeLogDirPath>/preupgrade_fixups_ANUJ.sql to complete all
of the BEFORE UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
+ Adjust TABLESPACE SIZES as needed.
Auto 12.2.0.1.0
Tablespace Size Extend Min Size Action
---------- ---------- -------- ---------- ------
SYSAUX 740 MB DISABLED 722 MB None
SYSTEM 260 MB ENABLED 697 MB None
TEMP 20 MB ENABLED 150 MB None
Note that 12.2.0.1.0 minimum sizes are estimates.
If you plan to upgrade multiple pluggable databases concurrently,
then you must ensure that the UNDO tablespace size is equal to at least
the number of pluggable databases that you upgrade concurrently,
multiplied by that minimum. Failing to allocate sufficient space can
cause the upgrade to fail.
+ REMOVE the following OBSOLETE initialization parameters.
Parameter
------------------------------
exclude_seed_cdb_view
+ (AUTOFIXUP) Empty the RECYCLEBIN immediately before database upgrade.
The database contains 2 objects in the recycle bin.
The recycle bin must be completely empty before database upgrade.
RECOMMENDED ACTIONS
===================
+ Run 12.1.0.2.0 $ORACLE_HOME/rdbms/admin/utlrp.sql to recompile invalid
objects. You can view the individual invalid objects with
SET SERVEROUTPUT ON;
EXECUTE DBMS_PREUP.INVALID_OBJECTS;
2 objects are INVALID.
There should be no INVALID objects in SYS/SYSTEM or user schemas before
database upgrade.
+ Review and remove any unnecessary HIDDEN/UNDERSCORE parameters.
The database contains the following initialization parameters whose name
begins with an underscore:
_catalog_foreign_restore
_ash_size
Remove hidden parameters before database upgrade unless your application
vendors and/or Oracle Support state differently. Changes will need to
be made in the spfile.
+ (AUTOFIXUP) Gather stale data dictionary statistics prior to database
upgrade in off-peak time using:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Dictionary statistics do not exist or are stale (not up-to-date).
Dictionary statistics help the Oracle optimizer find efficient SQL
execution plans and are essential for proper upgrade timing. Oracle
recommends gathering dictionary statistics in the last 24 hours before
database upgrade.
For information on managing optimizer statistics, refer to the 12.1.0.2
Oracle Database SQL Tuning Guide.
=============
AFTER UPGRADE
=============
Run <preupgradeLogDirPath>/postupgrade_fixups_ANUJ.sql to complete all
of the AFTER UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
None
RECOMMENDED ACTIONS
===================
+ Upgrade the database time zone version using the DBMS_DST package.
The database is using timezone datafile version 18 and the target
12.2.0.1.0 database ships with timezone datafile version 26.
Oracle recommends using the most recent timezone data. For further
information, refer to My Oracle Support Note 1585343.1.
+ (AUTOFIXUP) Gather dictionary statistics after the upgrade using the
command:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Oracle recommends gathering dictionary statistics after upgrade.
Dictionary statistics provide essential information to the Oracle
optimizer to help it find efficient SQL execution plans. After a
database upgrade, statistics need to be re-gathered as there can now be
tables that have significantly changed during the upgrade or new tables
that do not have statistics gathered yet.
Report generated by Oracle Database Pre-Upgrade Information Tool Version
12.2.0.1.0
Upgrade-To version: 12.2.0.1.0
=======================================
Status of the database prior to upgrade
=======================================
Database Name: ORCL12C
Container Name: VIHAAN
Container ID: 6
Version: 12.1.0.2.0
Compatible: 12.1.0.2.0
Blocksize: 8192
Platform: Linux x86 64-bit
Timezone File: 18
Database log mode: ARCHIVELOG
Readonly: FALSE
Edition: EE
Oracle Component Upgrade Action Current Status
---------------- -------------- --------------
Oracle Server [to be upgraded] VALID
JServer JAVA Virtual Machine [to be upgraded] VALID
Oracle XDK for Java [to be upgraded] VALID
Real Application Clusters [to be upgraded] OPTION OFF
Oracle Workspace Manager [to be upgraded] VALID
OLAP Analytic Workspace [to be upgraded] VALID
Oracle Label Security [to be upgraded] VALID
Oracle Database Vault [to be upgraded] VALID
Oracle Text [to be upgraded] VALID
Oracle XML Database [to be upgraded] VALID
Oracle Java Packages [to be upgraded] VALID
Oracle Multimedia [to be upgraded] VALID
Oracle Spatial [to be upgraded] VALID
Oracle OLAP API [to be upgraded] VALID
==============
BEFORE UPGRADE
==============
Run <preupgradeLogDirPath>/preupgrade_fixups_VIHAAN.sql to complete all
of the BEFORE UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
+ Adjust TABLESPACE SIZES as needed.
Auto 12.2.0.1.0
Tablespace Size Extend Min Size Action
---------- ---------- -------- ---------- ------
SYSAUX 740 MB DISABLED 721 MB None
SYSTEM 260 MB ENABLED 697 MB None
TEMP 20 MB ENABLED 150 MB None
Note that 12.2.0.1.0 minimum sizes are estimates.
If you plan to upgrade multiple pluggable databases concurrently,
then you must ensure that the UNDO tablespace size is equal to at least
the number of pluggable databases that you upgrade concurrently,
multiplied by that minimum. Failing to allocate sufficient space can
cause the upgrade to fail.
+ REMOVE the following OBSOLETE initialization parameters.
Parameter
------------------------------
exclude_seed_cdb_view
+ (AUTOFIXUP) Empty the RECYCLEBIN immediately before database upgrade.
The database contains 1 objects in the recycle bin.
The recycle bin must be completely empty before database upgrade.
RECOMMENDED ACTIONS
===================
+ Run 12.1.0.2.0 $ORACLE_HOME/rdbms/admin/utlrp.sql to recompile invalid
objects. You can view the individual invalid objects with
SET SERVEROUTPUT ON;
EXECUTE DBMS_PREUP.INVALID_OBJECTS;
2 objects are INVALID.
There should be no INVALID objects in SYS/SYSTEM or user schemas before
database upgrade.
+ Review and remove any unnecessary HIDDEN/UNDERSCORE parameters.
The database contains the following initialization parameters whose name
begins with an underscore:
_catalog_foreign_restore
_ash_size
Remove hidden parameters before database upgrade unless your application
vendors and/or Oracle Support state differently. Changes will need to
be made in the spfile.
+ (AUTOFIXUP) Gather stale data dictionary statistics prior to database
upgrade in off-peak time using:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Dictionary statistics do not exist or are stale (not up-to-date).
Dictionary statistics help the Oracle optimizer find efficient SQL
execution plans and are essential for proper upgrade timing. Oracle
recommends gathering dictionary statistics in the last 24 hours before
database upgrade.
For information on managing optimizer statistics, refer to the 12.1.0.2
Oracle Database SQL Tuning Guide.
=============
AFTER UPGRADE
=============
Run <preupgradeLogDirPath>/postupgrade_fixups_VIHAAN.sql to complete all
of the AFTER UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
None
RECOMMENDED ACTIONS
===================
+ Upgrade the database time zone version using the DBMS_DST package.
The database is using timezone datafile version 18 and the target
12.2.0.1.0 database ships with timezone datafile version 26.
Oracle recommends using the most recent timezone data. For further
information, refer to My Oracle Support Note 1585343.1.
+ (AUTOFIXUP) Gather dictionary statistics after the upgrade using the
command:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Oracle recommends gathering dictionary statistics after upgrade.
Dictionary statistics provide essential information to the Oracle
optimizer to help it find efficient SQL execution plans. After a
database upgrade, statistics need to be re-gathered as there can now be
tables that have significantly changed during the upgrade or new tables
that do not have statistics gathered yet.
Report generated by Oracle Database Pre-Upgrade Information Tool Version
12.2.0.1.0
Upgrade-To version: 12.2.0.1.0
=======================================
Status of the database prior to upgrade
=======================================
Database Name: ORCL12C
Container Name: ORCLDP
Container ID: 7
Version: 12.1.0.2.0
Compatible: 12.1.0.2.0
Blocksize: 8192
Platform: Linux x86 64-bit
Timezone File: 18
Database log mode: ARCHIVELOG
Readonly: FALSE
Edition: EE
Oracle Component Upgrade Action Current Status
---------------- -------------- --------------
Oracle Server [to be upgraded] VALID
JServer JAVA Virtual Machine [to be upgraded] VALID
Oracle XDK for Java [to be upgraded] VALID
Real Application Clusters [to be upgraded] OPTION OFF
Oracle Workspace Manager [to be upgraded] VALID
OLAP Analytic Workspace [to be upgraded] VALID
Oracle Label Security [to be upgraded] VALID
Oracle Database Vault [to be upgraded] VALID
Oracle Text [to be upgraded] VALID
Oracle XML Database [to be upgraded] VALID
Oracle Java Packages [to be upgraded] VALID
Oracle Multimedia [to be upgraded] VALID
Oracle Spatial [to be upgraded] VALID
Oracle Application Express [to be upgraded] VALID
Oracle OLAP API [to be upgraded] VALID
==============
BEFORE UPGRADE
==============
Run <preupgradeLogDirPath>/preupgrade_fixups_ORCLDP.sql to complete all
of the BEFORE UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
+ Adjust TABLESPACE SIZES as needed.
Auto 12.2.0.1.0
Tablespace Size Extend Min Size Action
---------- ---------- -------- ---------- ------
EXAMPLE 1244 MB DISABLED 1217 MB None
SYSAUX 1220 MB ENABLED 2095 MB None
SYSTEM 410 MB ENABLED 911 MB None
TEMP 20 MB ENABLED 150 MB None
USERS 150 MB DISABLED 148 MB None
Note that 12.2.0.1.0 minimum sizes are estimates.
If you plan to upgrade multiple pluggable databases concurrently,
then you must ensure that the UNDO tablespace size is equal to at least
the number of pluggable databases that you upgrade concurrently,
multiplied by that minimum. Failing to allocate sufficient space can
cause the upgrade to fail.
+ REMOVE the following OBSOLETE initialization parameters.
Parameter
------------------------------
exclude_seed_cdb_view
+ (AUTOFIXUP) Empty the RECYCLEBIN immediately before database upgrade.
The database contains 7 objects in the recycle bin.
The recycle bin must be completely empty before database upgrade.
+ Set the OPEN_CURSORS initialization parameter to at least 150 before
upgrading the database.
The OPEN_CURSORS initialization parameter is set to 50.
The OPEN_CURSORS initialization parameter must be set to a minimum of
150 to avoid exceeding number of open cursors during Oracle Application
Express (APEX) upgrade.
Note that updating the PFILE/SPFILE will not take effect until the next
database startup.
RECOMMENDED ACTIONS
===================
+ Run 12.1.0.2.0 $ORACLE_HOME/rdbms/admin/utlrp.sql to recompile invalid
objects. You can view the individual invalid objects with
SET SERVEROUTPUT ON;
EXECUTE DBMS_PREUP.INVALID_OBJECTS;
492 objects are INVALID.
There should be no INVALID objects in SYS/SYSTEM or user schemas before
database upgrade.
+ Review and remove any unnecessary HIDDEN/UNDERSCORE parameters.
The database contains the following initialization parameters whose name
begins with an underscore:
_catalog_foreign_restore
_ash_size
Remove hidden parameters before database upgrade unless your application
vendors and/or Oracle Support state differently. Changes will need to
be made in the spfile.
+ (AUTOFIXUP) Gather stale data dictionary statistics prior to database
upgrade in off-peak time using:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Dictionary statistics do not exist or are stale (not up-to-date).
Dictionary statistics help the Oracle optimizer find efficient SQL
execution plans and are essential for proper upgrade timing. Oracle
recommends gathering dictionary statistics in the last 24 hours before
database upgrade.
For information on managing optimizer statistics, refer to the 12.1.0.2
Oracle Database SQL Tuning Guide.
+ Please make sure that all the MVs are refreshed and sys.sumdelta$
becomes empty before doing upgrade, unless you have strong business
reasons not to do so. You can use dbms_mview.refresh() to refresh the
MVs except those stale ones to be kept due to business need. If there
are any stale MVs depending on changes in sys.sumdelta$, do not truncate
it, because doing so will cause wrong results after refresh.
There is one or more non-fresh MV in the database or sumdelta$ is not
empty.
Oracle recommends that all materialized views (MV's) are refreshed
before upgrading the database because this will clear the MV logs and
the sumdelta$ table, and make the UPGRADE process faster. If you choose
to not refresh some MVs, the change data for those MV's will be carried
through the UPGRADE process. After UPGRADE, you can refresh the MV's and
MV incremental refresh should work in normal cases.
=============
AFTER UPGRADE
=============
Run <preupgradeLogDirPath>/postupgrade_fixups_ORCLDP.sql to complete all
of the AFTER UPGRADE action items below marked with '(AUTOFIXUP)'.
REQUIRED ACTIONS
================
None
RECOMMENDED ACTIONS
===================
+ If you use the -T option for the database upgrade, then run
$ORACLE_HOME/rdbms/admin/utluptabdata.sql after the upgrade is complete,
to VALIDATE and UPGRADE any user tables affected by changes to
Oracle-Maintained types.
There are user tables dependent on Oracle-Maintained object types.
If the -T option is used to set user tablespaces to READ ONLY during the
upgrade, user tables in those tablespaces, that are dependent on
Oracle-Maintained types, will not be automatically upgraded. If a type
is evolved during the upgrade, any dependent tables need to be
re-validated and upgraded to the latest type version AFTER the database
upgrade completes.
+ Upgrade the database time zone version using the DBMS_DST package.
The database is using timezone datafile version 18 and the target
12.2.0.1.0 database ships with timezone datafile version 26.
Oracle recommends using the most recent timezone data. For further
information, refer to My Oracle Support Note 1585343.1.
+ Patch your APEX software from version 5.0.3.00.03 to at least version
5.0.4.00.12.
Your existing version of APEX (5.0.3.00.03) does not require upgrade,
but may still need manual APEX patching.
The APEX patching process is not performed by the 12.1.0.2.0 Oracle
database upgrade. The APEX version upgrade only ensures that the APEX
version is upgraded to version 5.0 and does not guarantee the version is
brought all the way to the patched level 5.0.4.00.12. If a PDB from
this CDB is unplugged and plugged into another ROOT, the plugin process
may require the PDB to be at the patched level 5.0.4.00.12. That
patching process, if desired, must be performed manually. See My Oracle
Support Note 1088970.1 for more details.
+ (AUTOFIXUP) Gather dictionary statistics after the upgrade using the
command:
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;
Oracle recommends gathering dictionary statistics after upgrade.
Dictionary statistics provide essential information to the Oracle
optimizer to help it find efficient SQL execution plans. After a
database upgrade, statistics need to be re-gathered as there can now be
tables that have significantly changed during the upgrade or new tables
that do not have statistics gathered yet.
Preupgrade generated files:
/u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/preupgrade_fixups.sql
/u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/postupgrade_fixups.sql
[oracle@vbgeneric admin]$ ls -ltr /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/*fix*.sql
-rw-r--r-- 1 oracle oinstall 6201 May 1 08:20 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/preupgrade_fixups_CDB_ROOT.sql
-rw-r--r-- 1 oracle oinstall 5549 May 1 08:20 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/postupgrade_fixups_CDB_ROOT.sql
-rw-r--r-- 1 oracle oinstall 5070 May 1 08:21 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/preupgrade_fixups_PDB_SEED.sql
-rw-r--r-- 1 oracle oinstall 5549 May 1 08:21 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/postupgrade_fixups_PDB_SEED.sql
-rw-r--r-- 1 oracle oinstall 8230 May 1 08:21 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/preupgrade_fixups_ORCL.sql
-rw-r--r-- 1 oracle oinstall 8112 May 1 08:21 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/postupgrade_fixups_ORCL.sql
-rw-r--r-- 1 oracle oinstall 5737 May 1 08:21 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/preupgrade_fixups_ORDS.sql
-rw-r--r-- 1 oracle oinstall 5533 May 1 08:21 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/postupgrade_fixups_ORDS.sql
-rw-r--r-- 1 oracle oinstall 5737 May 1 08:21 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/preupgrade_fixups_ANUJ.sql
-rw-r--r-- 1 oracle oinstall 5533 May 1 08:21 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/postupgrade_fixups_ANUJ.sql
-rw-r--r-- 1 oracle oinstall 5745 May 1 08:21 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/preupgrade_fixups_VIHAAN.sql
-rw-r--r-- 1 oracle oinstall 5541 May 1 08:21 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/postupgrade_fixups_VIHAAN.sql
-rw-r--r-- 1 oracle oinstall 8238 May 1 08:22 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/preupgrade_fixups_ORCLDP.sql
-rw-r--r-- 1 oracle oinstall 8120 May 1 08:22 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/postupgrade_fixups_ORCLDP.sql
-rw-r--r-- 1 oracle oinstall 34965 May 1 08:22 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/preupgrade_fixups.sql
-rw-r--r-- 1 oracle oinstall 24858 May 1 08:22 /u01/app/oracle/cfgtoollogs/orcl12c/preupgrade/postupgrade_fixups.sql
**********************************
For Out put in Dir
[oracle@vbgeneric Upgrade]$ /u01/app/oracle/product/12.1.0.2/db_1/jdk/bin/java -jar /u02/app/oracle/product/12.2.0.1/db_1/rdbms/admin/preupgrade.jar FILE DIR /tmp/Upgrade
Preupgrade generated files:
/tmp/Upgrade/preupgrade.log
/tmp/Upgrade/preupgrade_fixups.sql
/tmp/Upgrade/postupgrade_fixups.sql
[oracle@vbgeneric Upgrade]$ ls -ltr /tmp/Upgrade/*.*
-rw-r--r-- 1 oracle oinstall 5373 May 1 08:32 /tmp/Upgrade/dbms_registry_basic.sql
-rw-r--r-- 1 oracle oinstall 12693 May 1 08:32 /tmp/Upgrade/dbms_registry_extended.sql
-rw-r--r-- 1 oracle oinstall 7027 May 1 08:32 /tmp/Upgrade/preupgrade_driver.sql
-rw-r--r-- 1 oracle oinstall 390244 May 1 08:32 /tmp/Upgrade/preupgrade_package.sql
-rw-r--r-- 1 oracle oinstall 60144 May 1 08:32 /tmp/Upgrade/preupgrade_messages.properties
-rw-r--r-- 1 oracle oinstall 400 May 1 08:32 /tmp/Upgrade/dir_preUpgrade_catCon_catcon_14209.lst
-rw-r--r-- 1 oracle oinstall 7377 May 1 08:32 /tmp/Upgrade/dir_preUpgrade_catCon0.log
-rw-r--r-- 1 oracle oinstall 5617 May 1 08:32 /tmp/Upgrade/dir_preUpgrade_catCon1.log
-rw-r--r-- 1 oracle oinstall 6201 May 1 08:32 /tmp/Upgrade/preupgrade_fixups_CDB_ROOT.sql
-rw-r--r-- 1 oracle oinstall 5549 May 1 08:32 /tmp/Upgrade/postupgrade_fixups_CDB_ROOT.sql
-rw-r--r-- 1 oracle oinstall 6779 May 1 08:32 /tmp/Upgrade/preupgrade_CDB_ROOT.log
-rw-r--r-- 1 oracle oinstall 5070 May 1 08:32 /tmp/Upgrade/preupgrade_fixups_PDB_SEED.sql
-rw-r--r-- 1 oracle oinstall 5549 May 1 08:32 /tmp/Upgrade/postupgrade_fixups_PDB_SEED.sql
-rw-r--r-- 1 oracle oinstall 5714 May 1 08:32 /tmp/Upgrade/preupgrade_PDB_SEED.log
-rw-r--r-- 1 oracle oinstall 8230 May 1 08:32 /tmp/Upgrade/preupgrade_fixups_ORCL.sql
-rw-r--r-- 1 oracle oinstall 8112 May 1 08:32 /tmp/Upgrade/postupgrade_fixups_ORCL.sql
-rw-r--r-- 1 oracle oinstall 9119 May 1 08:32 /tmp/Upgrade/preupgrade_ORCL.log
-rw-r--r-- 1 oracle oinstall 5737 May 1 08:33 /tmp/Upgrade/preupgrade_fixups_ORDS.sql
-rw-r--r-- 1 oracle oinstall 5533 May 1 08:33 /tmp/Upgrade/postupgrade_fixups_ORDS.sql
-rw-r--r-- 1 oracle oinstall 5921 May 1 08:33 /tmp/Upgrade/preupgrade_ORDS.log
-rw-r--r-- 1 oracle oinstall 5737 May 1 08:33 /tmp/Upgrade/preupgrade_fixups_ANUJ.sql
-rw-r--r-- 1 oracle oinstall 5533 May 1 08:33 /tmp/Upgrade/postupgrade_fixups_ANUJ.sql
-rw-r--r-- 1 oracle oinstall 5921 May 1 08:33 /tmp/Upgrade/preupgrade_ANUJ.log
-rw-r--r-- 1 oracle oinstall 5745 May 1 08:33 /tmp/Upgrade/preupgrade_fixups_VIHAAN.sql
-rw-r--r-- 1 oracle oinstall 5541 May 1 08:33 /tmp/Upgrade/postupgrade_fixups_VIHAAN.sql
-rw-r--r-- 1 oracle oinstall 5927 May 1 08:33 /tmp/Upgrade/preupgrade_VIHAAN.log
-rw-r--r-- 1 oracle oinstall 8238 May 1 08:33 /tmp/Upgrade/preupgrade_fixups_ORCLDP.sql
-rw-r--r-- 1 oracle oinstall 8120 May 1 08:33 /tmp/Upgrade/postupgrade_fixups_ORCLDP.sql
-rw-r--r-- 1 oracle oinstall 9125 May 1 08:33 /tmp/Upgrade/preupgrade_ORCLDP.log
-rw-r--r-- 1 oracle oinstall 25444 May 1 08:33 /tmp/Upgrade/execPreUpgrade_catCon0.log
-rw-r--r-- 1 oracle oinstall 19536 May 1 08:33 /tmp/Upgrade/execPreUpgrade_catCon1.log
-rw-r--r-- 1 oracle oinstall 49434 May 1 08:33 /tmp/Upgrade/execPreUpgrade_catCon_catcon_14339.lst
-rw-r--r-- 1 oracle oinstall 48506 May 1 08:33 /tmp/Upgrade/preupgrade.log
-rw-r--r-- 1 oracle oinstall 34965 May 1 08:33 /tmp/Upgrade/preupgrade_fixups.sql
-rw-r--r-- 1 oracle oinstall 24858 May 1 08:33 /tmp/Upgrade/postupgrade_fixups.sql
