Oracle 19c Database Upgrade From 12.2.0.1 To 19.2.0.0 Using DBUA

Oracle 19c Database Upgrade From 12.2.0.1 to 19.2.0.0 Using DBUA | | Oracledbwr https://oracledbwr.
com/oracle-19c-database-upgrade-from-12-2-0-1-to-19-2-0-0-using-dbua/
ABOUT ME DATABASE RAC ASM UPGRADE
MULTITENANT RMAN DATAPUMP ORACLE CLOUD
PATCHING TUNING GOLDENGATE
Oracle 19c Database Upgrade

From 12.2.0.1 to 19.2.0.0 Using
DBUA
Search
Categories
Description:-
1 sur 29 12/08/2020 à 09:24

Oracle 19c Database Upgrade From 12.2.0.1 to 19.2.0.0 Using DBUA | | Oracledbwr https://oracledbwr.com/oracle-19c-database-upgrade-from-12-2-0-1-to-19-2-0-0-using-dbua/
[oracle@standby dbs]$ export ORACLE_SID=upgr

[oracle@standby dbs]$ sqlplus / as sysdba
SQL*Plus: Release 12.2.0.1.0 Production on Thu Mar 21 20:02:00 2019
Copyright (c) 1982, 2016, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 2449473536 bytes

Fixed Size 8623640 bytes
Variable Size 654313960 bytes
Database Buffers 1778384896 bytes
2 sur 29 12/08/2020 à 09:24

Redo Buffers 8151040 bytes

Database mounted.
Database opened.
Ensure backup is complete before upgrade.
Empty Recycle bin.
Run Gather statistics to finish upgrade soon.
SQL> SELECT * FROM v$backup WHERE status != 'NOT ACTIVE';
no rows selected
SQL> PURGE DBA_RECYCLEBIN ;
DBA_Recyclebin purged.
Archives
SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;
Select Month
PL/SQL procedure successfully completed.
Tags
SQL> !
Stop the running 12c listener
3 sur 29 12/08/2020 à 09:24

Run preupgrade tool and fixups
Oracle strongly recommends that you run the Pre-

Upgrade Information Tool before starting the
upgrade with DBUA. Although DBUA runs the Pre-
Upgrade Information Tool as part of the pre-
requisite checks, it is good practice to run the tool
ahead of time in order to analyze the database and
take actions that can decrease downtime for
upgrading.
Connect to 12.2.0.1 database environment as SYS,
Pre-upgrade checks :
Run the preupgrade tool .
[oracle@standby dbs]$ java -jar /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/preupgra

Report generated by Oracle Database Pre-Upgrade Information Tool Version
19.0.0.0.0 Build: 1 on 2019-03-21T20:07:45
Upgrade-To version: 19.0.0.0.0
=======================================
4 sur 29 12/08/2020 à 09:24

Status of the database prior to upgrade

=======================================
Database Name: UPGR
Container Name: upgr
Container ID: 0
Version: 12.2.0.1.0
DB Patch Level: No Patch Bundle applied
Compatible: 12.2.0
Blocksize: 8192
Platform: Linux x86 64-bit
Timezone File: 26
Database log mode: NOARCHIVELOG
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
5 sur 29 12/08/2020 à 09:24

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
==============
REQUIRED ACTIONS
================
None
RECOMMENDED ACTIONS
===================
1. (AUTOFIXUP) Gather statistics on fixed objects prior the upgrade.
None of the fixed object tables have had stats collected.
Gathering statistics on fixed objects, if none have been gathered yet, is

recommended prior to upgrading.
For information on managing optimizer statistics, refer to the 12.2.0.1

Oracle Database SQL Tuning Guide.
INFORMATION ONLY
================
6 sur 29 12/08/2020 à 09:24

2. To help you keep track of your tablespace allocations, the following

AUTOEXTEND tablespaces are expected to successfully EXTEND during the
upgrade process.
Min Size
Tablespace Size For Upgrade
---------- ---------- -----------
SYSAUX 490 MB 509 MB
SYSTEM 800 MB 914 MB
TEMP 131 MB 150 MB
UNDOTBS1 70 MB 439 MB
Minimum tablespace sizes for upgrade are estimates.
3. Check the Oracle Backup and Recovery User's Guide for information on how
to manage an RMAN recovery catalog schema.
If you are using a version of the recovery catalog schema that is older
than that required by the RMAN client version, then you must upgrade the
catalog schema.
It is good practice to have the catalog schema the same or higher version
than the RMAN client version you are using.
ORACLE GENERATED FIXUP SCRIPT

=============================
All of the issues in database UPGR
7 sur 29 12/08/2020 à 09:24

which are identified above as BEFORE UPGRADE "(AUTOFIXUP)" can be resolved by

executing the following
SQL>@/u01/app/oracle/cfgtoollogs/upgr/preupgrade/preupgrade_fixups.sql
=============
AFTER UPGRADE
=============
REQUIRED ACTIONS
================
None
RECOMMENDED ACTIONS
===================
4. Upgrade the database time zone file using the DBMS_DST package.
The database is using time zone file version 26 and the target 19 release
ships with time zone file version 32.
Oracle recommends upgrading to the desired (latest) version of the time

zone file. For more information, refer to "Upgrading the Time Zone File
and Timestamp with Time Zone Data" in the 19 Oracle Database
Globalization Support Guide.
5. To identify directory objects with symbolic links in the path name, run
$ORACLE_HOME/rdbms/admin/utldirsymlink.sql AS SYSDBA after upgrade.
8 sur 29 12/08/2020 à 09:24

Recreate any directory objects listed, using path names that contain no
symbolic links.
Some directory object path names may currently contain symbolic links.
Starting in Release 18c, symbolic links are not allowed in directory

object path names used with BFILE data types, the UTL_FILE package, or
external tables.
6. (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.
7. Gather statistics on fixed objects after the upgrade and when there is a
representative workload on the system using the command:
EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;
9 sur 29 12/08/2020 à 09:24

This recommendation is given for all preupgrade runs.
Fixed object statistics provide essential information to the Oracle

optimizer to help it find efficient SQL execution plans. Those
statistics are specific to the Oracle Database release that generates
them, and can be stale upon database upgrade.
For information on managing optimizer statistics, refer to the 12.2.0.1

Oracle Database SQL Tuning Guide.
ORACLE GENERATED FIXUP SCRIPT

=============================
All of the issues in database UPGR
which are identified above as AFTER UPGRADE "(AUTOFIXUP)" can be resolved by
executing the following
SQL>@/u01/app/oracle/cfgtoollogs/upgr/preupgrade/postupgrade_fixups.sql
==================
PREUPGRADE SUMMARY
==================
/u01/app/oracle/cfgtoollogs/upgr/preupgrade/preupgrade.log
/u01/app/oracle/cfgtoollogs/upgr/preupgrade/preupgrade_fixups.sql
/u01/app/oracle/cfgtoollogs/upgr/preupgrade/postupgrade_fixups.sql
Execute fixup scripts as indicated below:
10 sur 29 12/08/2020 à 09:24

Before upgrade:
Log into the database and execute the preupgrade fixups

@/u01/app/oracle/cfgtoollogs/upgr/preupgrade/preupgrade_fixups.sql
After the upgrade:
Log into the database and execute the postupgrade fixups

@/u01/app/oracle/cfgtoollogs/upgr/preupgrade/postupgrade_fixups.sql
Preupgrade complete: 2019-03-21T20:07:46
Run the preupgrade_fixup.sql
[oracle@standby dbs]$ !sq

sqlplus / as sysdba
SQL*Plus: Release 12.2.0.1.0 Production on Thu Mar 21 20:13:03 2019
Copyright (c) 1982, 2016, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
SQL> @/u01/app/oracle/cfgtoollogs/upgr/preupgrade/preupgrade_fixups.sql
Executing Oracle PRE-Upgrade Fixup Script
11 sur 29 12/08/2020 à 09:24

Auto-Generated by: Oracle Preupgrade Script

Version: 19.0.0.0.0 Build: 1
Generated on: 2019-03-21 20:07:39
For Source Database: UPGR

Source Database Version: 12.2.0.1.0
For Upgrade to Version: 19.0.0.0.0
Preup Preupgrade
Action Issue Is
Number Preupgrade Check Name Remedied Further DBA Action
------ ------------------------ ---------- -------------------------
1. pre_fixed_objects YES None.
2. tablespaces_info NO Informational only.
Further action is optional.
3. rman_recovery_version NO Informational only.
The fixup scripts have been run and resolved what they can. However,
there are still issues originally identified by the preupgrade that
have not been remedied and are still present in the database.
Depending on the severity of the specific issue, and the nature of
the issue itself, that could mean that your database is not ready
for upgrade. To resolve the outstanding issues, start by reviewing
the preupgrade_fixups.sql and searching it for the name of
the failed CHECK NAME or Preupgrade Action Number listed above.
12 sur 29 12/08/2020 à 09:24

There you will find the original corresponding diagnostic message

from the preupgrade which explains in more detail what still needs
to be done.

UPGRADE:
[oracle@standby ~]$ export ORACLE_HOME=/u01/app/oracle/product/19.0.0/dbhome_1

[oracle@standby ~]$ export ORACLE_SID=upgr
[oracle@standby ~]$ export PATH=$ORACLE_HOME/bin:$PATH
[oracle@standby ~]$ dbua
13 sur 29 12/08/2020 à 09:24

Upgrade Oracle Database
14 sur 29 12/08/2020 à 09:24

15 sur 29 12/08/2020 à 09:24

16 sur 29 12/08/2020 à 09:24

17 sur 29 12/08/2020 à 09:24

18 sur 29 12/08/2020 à 09:24

19 sur 29 12/08/2020 à 09:24

20 sur 29 12/08/2020 à 09:24

21 sur 29 12/08/2020 à 09:24

22 sur 29 12/08/2020 à 09:24

23 sur 29 12/08/2020 à 09:24

Post-upgrade checks:
Run “postupgrade_fixups.sql” to check post upgrade status.
SQL> @/u01/app/oracle/cfgtoollogs/upgr/preupgrade/postupgrade_fixups.sql
Session altered.
24 sur 29 12/08/2020 à 09:24

Package created.
No errors.
Package body created.
No errors.
Package created.
No errors.
Package body created.
25 sur 29 12/08/2020 à 09:24

No errors.
Executing Oracle POST-Upgrade Fixup Script
Auto-Generated by: Oracle Preupgrade Script

Version: 19.0.0.0.0 Build: 1
Generated on: 2019-03-21 20:07:45
For Source Database: UPGR

Source Database Version: 12.2.0.1.0
For Upgrade to Version: 19.0.0.0.0
Preup Preupgrade
Action Issue Is
Number Preupgrade Check Name Remedied Further DBA Action
------ ------------------------ ---------- ----------------------------
4. old_time_zones_exist YES None.
5. dir_symlinks YES None.
6. post_dictionary YES None.
7. post_fixed_objects NO Informational only.
The fixup scripts have been run and resolved what they can. However,
there are still issues originally identified by the preupgrade that
have not been remedied and are still present in the database.
Depending on the severity of the specific issue, and the nature of
the issue itself, that could mean that your database upgrade is not
26 sur 29 12/08/2020 à 09:24

fully complete. To resolve the outstanding issues, start by reviewing

the postupgrade_fixups.sql and searching it for the name of
the failed CHECK NAME or Preupgrade Action Number listed above.
There you will find the original corresponding diagnostic message
from the preupgrade which explains in more detail what still needs
to be done.
Session altered.
SQL> select VERSION,name,open_mode from v$instance,v$database;
VERSION NAME OPEN_MODE

----------------- --------- --------------------
19.0.0.0.0 UPGR READ WRITE
SQL> SELECT * FROM v$timezone_file;
FILENAME VERSION CON_ID

-------------------- ---------- ----------
timezlrg_32.dat 32 0
SQL> select TZ_VERSION from registry$database;
27 sur 29 12/08/2020 à 09:24

TZ_VERSION
----------
32
Catch Me On:- Hariprasath Rajaram
Telegram:https://t.me/joinchat/I_f4DkeGfZuxgMIoJSpQZg LinkedIn:https://www.linkedin.com/in/h
You may also like
Previous Post Next Post
28 sur 29 12/08/2020 à 09:24

Recent Posts
Get updated
29 sur 29 12/08/2020 à 09:24

Oracle 19c Database Upgrade From 12.2.0.1 To 19.2.0.0 Using DBUA

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle 19c Database Upgrade From 12.2.0.1 To 19.2.0.0 Using DBUA

Uploaded by

Copyright:

Available Formats

Oracle 19c Database Upgrade From 12.2.0.1 to 19.2.0.0 Using DBUA | | Oracledbwr https://oracledbwr.

ABOUT ME DATABASE RAC ASM UPGRADE

MULTITENANT RMAN DATAPUMP ORACLE CLOUD

PATCHING TUNING GOLDENGATE

Oracle 19c Database Upgrade

1 sur 29 12/08/2020 à 09:24

[oracle@standby dbs]$ export ORACLE_SID=upgr

SQL*Plus: Release 12.2.0.1.0 Production on Thu Mar 21 20:02:00 2019

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

Connected to an idle instance.

Total System Global Area 2449473536 bytes

2 sur 29 12/08/2020 à 09:24

Redo Buffers 8151040 bytes

Empty Recycle bin.

Run Gather statistics to finish upgrade soon.

SQL> SELECT * FROM v$backup WHERE status != 'NOT ACTIVE';

SQL> PURGE DBA_RECYCLEBIN ;

3 sur 29 12/08/2020 à 09:24

Run preupgrade tool and fixups

Oracle strongly recommends that you run the Pre-

Connect to 12.2.0.1 database environment as SYS,

Run the preupgrade tool .

[oracle@standby dbs]$ java -jar /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/preupgra

Upgrade-To version: 19.0.0.0.0

4 sur 29 12/08/2020 à 09:24

Status of the database prior to upgrade

Oracle Component Upgrade Action Current Status

5 sur 29 12/08/2020 à 09:24

Oracle Java Packages [to be upgraded] VALID

None of the fixed object tables have had stats collected.

Gathering statistics on fixed objects, if none have been gathered yet, is

For information on managing optimizer statistics, refer to the 12.2.0.1

6 sur 29 12/08/2020 à 09:24

2. To help you keep track of your tablespace allocations, the following

Minimum tablespace sizes for upgrade are estimates.

ORACLE GENERATED FIXUP SCRIPT

7 sur 29 12/08/2020 à 09:24

which are identified above as BEFORE UPGRADE "(AUTOFIXUP)" can be resolved by

Oracle recommends upgrading to the desired (latest) version of the time

8 sur 29 12/08/2020 à 09:24

Starting in Release 18c, symbolic links are not allowed in directory

6. (AUTOFIXUP) Gather dictionary statistics after the upgrade using the

Oracle recommends gathering dictionary statistics after upgrade.

Dictionary statistics provide essential information to the Oracle

9 sur 29 12/08/2020 à 09:24

This recommendation is given for all preupgrade runs.

Fixed object statistics provide essential information to the Oracle

For information on managing optimizer statistics, refer to the 12.2.0.1

ORACLE GENERATED FIXUP SCRIPT

Execute fixup scripts as indicated below:

10 sur 29 12/08/2020 à 09:24

Log into the database and execute the preupgrade fixups

After the upgrade:

Log into the database and execute the postupgrade fixups

Preupgrade complete: 2019-03-21T20:07:46

Run the preupgrade_fixup.sql

[oracle@standby dbs]$ !sq

SQL*Plus: Release 12.2.0.1.0 Production on Thu Mar 21 20:13:03 2019

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

11 sur 29 12/08/2020 à 09:24

Auto-Generated by: Oracle Preupgrade Script

For Source Database: UPGR

12 sur 29 12/08/2020 à 09:24