Document Provide the step by step to upgrade
11.2.0.3 to 12.1.0.1 on Windows Bit-64 Platform. Oracle 11.2.0.3 is out of
place upgrade from earlier releases which minimizes the risk and downtime as
11.2.0.3 is a full database software patch and is a full database software
installation. You need to download file number 1 and 2 out of 7 files .i.e. [1of7
and 2of7]. This patch is available on MOS under patch number 10404530.
Upgrade Compatibility Matrix for Upgrading to 12.1.x
1. Direct upgrade path to Oracle Database 12c Release 1
2. Indirect upgrade path to Oracle Database 12c Release 1
Upgrade Compatibility Matrix for Upgrading to 12.1.x
1. Direct upgrade path to Oracle Database 12c Release 1
Source Database
|
Destination
Database
|
10.2.0.5
|
12.1.x
|
11.1.0.7
|
12.1.x
|
11.2.0.2 (or
higher)
|
12.1.x
|
2. Indirect upgrade path to Oracle Database 12c Release 1
Source Database
|
Upgrade Path
|
Destination Database
|
11.2.0.1
|
=> 11.2.0.2 or higher =>
|
12.1.x
|
11.1.0.6
|
=> 11.1.0.7 or 11.2.0.2 or higher =>
|
12.1.x
|
10.2.0.4 (or earlier)
|
=> 10.2.0.5 or later direct upgrade version =>
|
12.1.x
|
10.1.0.5 (or earlier)
|
=> 10.2.0.5 or later direct upgrade version =>
|
12.1.x
|
9.2.0.8 (or earlier)
|
=> 9.2.0.8 --> 11.2.0.2 or higher =>
|
12.1.x
|
3. System Considerations and Requirements for Upgrading Oracle Database
There are few Checks and considerations that should be performed before starting an upgrade of Oracle Database i.e.
•Relocating Existing Data Files to the New Oracle Database Environment
•Upgrading PL/SQL Packages That Are Not Installed by Default
•Upgrading Oracle ASM Installed with Oracle Grid Infrastructure
•Considerations for Upgrading Oracle Clusterware and Oracle ASM Instances
•Upgrading with Read-Only and Offline Tablespaces
•Upgrading Using Standby Databases
•Upgrading Your Operating System
•Migrating Data to a Different Operating System
•Upgrading Databases That Use Oracle Streams Downstream Capture
•Upgrading Databases That Use Oracle Database Vault
4. Checking Current Version after 11.2.0.3 Database creation
5. Invoking DBUA
dbua executable is located in the ORACLE_HOME/bin directory. Start DBUA from the Oracle home where the new [12c] database software has been installed. Enter the command at a system prompt in the new home for Oracle Database 12c: The DBUA Select Operation page displays. Select the activity you want to perform “upgrade Oracle Database”
6. Select Database
Select Database Helps you select the database you want to upgrade. You need to select the appropriate home where the database is which need to be upgraded. You will get a dropdown for the list of homes as shown below in picture. You can select only one database at a time. If the database does not appear in the list, then make sure an entry with the database name exists in the oratab file in the etc directory
7. Performing pre-upgrade checks
This analysis takes several minutes to complete as it includes checks like:
• Empty database recycle bin.
• Invalid objects.
• Deprecated and desupported initialization parameters.
• Time zone data file version.
8. Prerequisite Checks
This page shows the validation and results, the severity, and if there is a problem whether the result is fixable, suggested actions. The Fixable column displays whether the result can be fixed or not. The Action drop-down list shows actions you can take.
9. Upgrade Options
Upgrade Options section provides the following:
9.1. Recompile Invalid Objects During Post-Upgrade:- Specify the parallelism for the recompilation of invalid objects during post upgrade. DBUA provides a recommended degree of Recompilation Parallelism, which it sets to one less than the number of CPU you have available
9.2. Upgrade Time Zone Data :- Select Upgrade Time Zone Data for DBUA to update the time zone data file for this release or else to it manually after upgrade
9.3. Gather Statistics Before Upgrade :- It reduces the overall time for the upgrade process.
9.4. Change Tablespace Offline/Read Only During Upgrade:-If you are upgrading a database for which you must transport tablespaces. In this case, the file headers must be made read/write before transporting.
9.5. File Locations:- The File Locations area for output that DBUA creates for diagnostics.
9.6. Custom Scripts tab to specify custom SQL scripts that you would like to run before and after the upgrade.
10. Management Options
Configure Enterprise Manager Database Express:- Oracle Enterprise Manager Database Express is a web-based database management application that is built into Oracle Database 12c
11. Move Database Files
In case of upgrading a single-instance database move Database Files page appears. In case of Real Application Clusters database, then the Move Database Files page does not display. You can skip the steps pertaining to moving database files and configuring the network to continue.
>> Move Database Files as Part of Upgrade:- You must also configure Storage Type for the database files either Filsystem or ASM
>> Move Fast Recovery Area as Part of Upgrade:- You can select Filesystem or ASM. If you select File System, then your fast recovery area is on the host file system and if ASM is selected, then your fast recovery area is on Oracle ASM storage, which must currently exist on your system. If you do not have an Oracle ASM instance, then you can create one using Automatic Storage Management Configuration Assistant (ASMCA) from the Oracle Cloud Infrastructure home and then restart DBUA
12. Network Configuration
Select the Listener displaying listener Name, Port , Oracle home, Status, and Migrate columns
13. Recovery Options
The Recovery Options page allows you to select the recovery method to use in case the upgrade process encounters a problem.
>> Use RMAN Backup:- Enter the full backup path location
>> Use Flashback and Guaranteed Restore Point :- Allows dbua to create a restore point before DBUA enters the upgrade process. Use Existing Guaranteed Restore Point and pick the named SCN from the drop-down list if Flashback Database and configured a fast recovery area as already configured
>> I have my own backup and restore strategy: - Not much to guess. you are on your own
14. Summary
Summary page shows the following information before it starts the upgrade:
• Name, version, and Oracle home of the source and target databases
• Database backup location, available space, and space required
• Warnings ignored
• Database components to be upgraded
• Initialization parameters changes
• Database files location
• Listener registration
Database Upgrade Summary
Source Database
|
Target Database
|
|
Name:
|
ORA11203
|
ORA11203
|
Release:
|
11.2.0.3.0
|
12.1.0.1.0
|
Oracle
Home:
|
d:\app\hcl\product\11.2.0\dbhome_4
|
D:\app\hcl\product\12.1.0\dbhome_3
|
Warnings Ignored
|
Inactive
DBIDs found in AWR. The inactive DBIDs in AWR may need additional update
after upgrade.
|
Database
contains schemas with objects dependent on DBMS_LDAP package. Refer to the
Oracle Database Upgrade Guide for instructions to configure Network ACLs.
|
Database Components
|
Version
|
Status
|
Oracle
Server
|
11.2.0.3.0
|
VALID
|
JServer
JAVA Virtual Machine
|
11.2.0.3.0
|
VALID
|
Oracle
XDK for Java
|
11.2.0.3.0
|
VALID
|
OLAP
Analytic Workspace
|
11.2.0.3.0
|
VALID
|
Oracle
Enterprise Manager Repository
|
11.2.0.3.0
|
VALID
|
Oracle
Text
|
11.2.0.3.0
|
VALID
|
Oracle
XML Database
|
11.2.0.3.0
|
VALID
|
Oracle
Java Packages
|
11.2.0.3.0
|
VALID
|
Oracle
Multimedia
|
11.2.0.3.0
|
VALID
|
Oracle
Spatial
|
11.2.0.3.0
|
VALID
|
Oracle
Workspace Manager
|
11.2.0.3.0
|
VALID
|
Expression
Filter
|
11.2.0.3.0
|
VALID
|
Rule
Manager
|
11.2.0.3.0
|
VALID
|
Oracle Application
Express
|
3.2.1.00.12
|
VALID
|
Oracle
OLAP API
|
11.2.0.3.0
|
VALID
|
The
following changes will be made in the initialization parameters:
|
Parameters
to be added:
|
Name
|
Value
|
local_listener
|
LISTENER_ORA11203
|
Parameters
to be updated:
|
Name
|
Old Value
|
New Value
|
sga_target
|
524288000
|
624951296
|
processes
|
150
|
300
|
db_recovery_file_dest_size
|
4322230272
|
4590m
|
Use Common Location for All Database Files
|
|
Database
Files Location
|
D:\app\hcl\product\12.1.0\oradata\ORA11203
|
The
time zone version and TIMESTAMP WITH TIME ZONE data of the Database will be
upgraded from version 14 to version 18.
|
The
Database will be managed by Enterprise Manager Database Express.
|
The
following listeners will be registered with the database:
|
Listener Name
|
LISTENER_12C
15. Progress Status
|
16. Upgrade Result
17. Validating Database Components
.....
No comments:
Post a Comment