Contents  Types of Upgrade  Compatability to upgrade 11g from 10g  Install 11g software  Preupgrade checkups  Upgrade  Post Upgrade Steps  Known Issues

1. Oracle Database Upgradation from 10.2.0.5
to 11g in windows 2003

2. Contents
 Types of Upgrade
 Compatability to upgrade 11g from 10g
 Install 11g software
 Preupgrade checkups
 Upgrade
 Post Upgrade Steps
 Known Issues

3. Types of Upgrade
1. Export Import
The export/import process can be used to transfer data between versions. Export the
data using the expdp utility from the source version and import using the 11g version
of impdp.
2. Using DBUA
Database Upgrade Assistant(DBUA) a GUI to upgrade the DB. This method is the best and
easy way to upgrade the database. It is the mostly practised method to upgrade database.
Oracle recommends to use this method.
3. Manual Method
As the name suggest manual upgrading the database using scripts.
Compatibility Matrix
Minimum Version of the database that can be directly upgraded to Oracle 11g Release 1
Minimum Version of the Oracle database software that can be directly upgraded to Oracle 11g
Release 2
Source Database Target Database
9.2.0.8 or higher 11.2.X
10.1.0.5 or higher 11.2.X
10.2.0.2 or higher 11.2.X
11.10.6 or higher 11.2.X
Step 1 Installing Oracle 11g
We cannot upgrade the existing Oracle Home, since 11g is not a patchset. We have to
install 11g oracle home as a seperate ORACLE_HOME in parallel to 10g Oracle Home.
Example my 10g Oracle Home is : D:appAVCSOFTWAREproduct10.2.0dbhome_1
then my 11g Oracel Home is : D:appAVCSOFTWAREproduct11.2.0dbhome_1
Just a parallel 11.1.0 directory can be created and we can install oracle home in this location

4. Start 11g installation.
Click on 11g setup
Screen 1 – Configuratuion Security Updates
select “Oracle Database 11g”
Screen 2 – Select Installation Method
Choose “Install Software Only”
Screen 3 – Grid Option
Singlel instance.
Screen 4 – Select Installation Type
Choose “Enterprise Edition”
Screen 5 – Installation Location
Oracle Base as parent directory of ORACLE HOME
Oracle Base : C:oracle11g
Screen 6 – Product Specific Pre-requisite Checks
It performs checks and if everything is ok click on Next
Screen 7 – Click on Finish
Screen 8 – Summary
Click on “Install”
This will complete the software installation for Oracle Database 11g.
Create listener using netca. If not configured will be prompted to create a listener for 11g
While upgrading to 11g.
Step 2 Back Up the Database:
Before proceeding backup the 10g database that is being upgrading. Have a good backup
1- Perform Cold Backup
(or)
2- Take a backup using RMAN
Connect to RMAN:
rman "target / nocatalog"
RUN
{
ALLOCATE CHANNEL ch1 TYPE DISK;
BACKUP DATABASE PLUS ARCHIVELOGS;
}

5. Step 3 Pre-Upgrade Utility
3.1 Check for the integrity of the source database prior to starting the upgrade
ORACLE_SID = [oracle] ? SID
sqlplus '/ as sysdba'
SQL> spool D:upgrade_info1.log
SQL> @?/rdbms/admin/utlrp.sql
SQL> spool off;
SQL> purge dba_recyclebin;
Run utlrp.sql (multiple times) to validate the invalid objects in the database, until there is no change in
the number of invalid objects.
3.2 Execute Pre Upgrade Script
Go to 11g ORACLE_HOME/rdbms/admin and copy the file utlu111i.sql to some temp
location.
cd ORACLE_11gHOME
cd rdbms/admin/
copy utlu111i.sql D:temp
The utility will give the output in the form of recommendations to be implemented before
starting the upgrade. Unless these requirements are met, the upgrade will fail. Most of the
time issue come up with time zone….Then login to the 10g oracle database and run the
above sql you copied.
sqlplus “/as sysdba”
SQL>spool D:upgrade_info2.log
SQL>@/11g_oracle_home/rdbms/admin/utlu111i.sql
spool off;
Check the output of the Pre-Upgrade Information Tool in upgrade_info2.log
and fix any issues.
Obsolete/Deprecated Parameters: [Update Oracle Database 11.1 init.ora or
spfile] **************************************************

6. –> “background_dump_dest” replaced by “diagnostic_dest”
–> “user_dump_dest” replaced by “diagnostic_dest”
–> “core_dump_dest” replaced by “diagnostic_dest”
To fix this obsolete parameter, comment out from initialization parameter file and replace
with new parameter like comment above three deprecated parameters and add
*.diagnostic_dest
WARNING: –> Database is using an old timezone file version.
…. Patch the 10.2.0.1.0 database to timezone file version 4
…. BEFORE upgrading the database. Re-run utlu111i.sql after
…. patching the database to record the new timezone file version.
To find time zone file version on source database (10g) run
SQL> select * from v$timezone_file;
If time zone file version is less than 4 then apply time zone patch .
For 10.2.0.5 version is 4. So we need not apply patch here.
3.3 Check invalid objects
SQL> select object_name, owner, object_type from all_objects where status like
‘INVALID';
SQL> select count(*) from dba_objects where status = ‘INVALID’;
SQL>select comp_name,version, status from dba_registry;
SQL> select count(*) from dba_objects where status=’VALID’;
3.4 Create & backup pfile from 10g and edit pfile to suit to 11g
If using spfile, create pfile connecting to 10g db
SQL> create pfile from spfile;
This will create pfile in 10g $ORACLE_HOME/dbs/init[SID].ora
Copy initialization file (pfile) from source (10g) to target (11g)

7. Adjust initialization parameter specific to 11g like
a) Remove *.background_dump_dest, *.core_dump_dest, *.user_dump_dest and add
*.diagnostic_dest=’/11g_base’ (11g Base Directory)
b) Change *.compatible=’10.2.0.1.0′ to *.compatible=’11.1.0′ or ’11.2.0’
c) audit_trail='db'
remote_login_passwordfile='EXCLUSIVE
Create the admin directory
cd C:oracle11gadminSID
mkdir pfile
mkdir audit
Step 4) Run Pre-Upgrade Utilityagain
After executing the recommended steps, run the pre-upgrade utility once again to make
sure, you don’t get any critical warnings.
Run the pre-upgrade utility script on 10g database while connecting from 10g oracle home.
If everything looks fine, Shut down the database from 10g Oracle Home. This time make
sure you don’t have the critical warnings like the one with TIMEZONE version.
 ORACLE_SID = SIDNAME
 sqlplus '/ as sysdba'
 SQL> @?/rdbms/admin/utlrp
 SQL> purge dba_recyclebin
5. Optimizer Statistics:
When upgrading to Oracle Database 11g Release 2 (11.2), optimizer statistics are collected
for dictionary tables that lack statistics. This statistics collection can be time consuming for
databases with a large number of dictionary tables, but statistics gathering only occurs for
those tables that lack statistics or are significantly changed during the upgrade
Gather Dictionary stats:
Connect as sys user and gather statistics
SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;
SQL> exec dbms_stats.gather_schema_stats('SYS',options=>'GATHER', estimate_percent
=> dbms_stats.auto_sample_size, method_opt => 'FOR ALL COLUMNS SIZE AUTO',
cascade => TRUE);

8. 6. Upgrade Database:
Set ORACLE_HOME=11g home
echo %ORACLE_HOME%
dbua
screen 1 : select the operation
choose Upgrade
screen 2 : select db to be upgraded
screen 3 : prerequisite check
If the prerequisite checks highlight any issues, take the appropriate action to fix the issues.
Screen 4 : Upgrade options
a. recompile invalid objects
b.degree od parallelism 60
c.upgrade timezone
d. if you have bkp already do not select
tick these 3
Screen 5 : Management Options
Configure Entreprise Manager
Screen 6 : Move db files
choose do not select move db files as part of upgrade
spefcify fra location let it be same create directory if not present create the directory
Give the location for Diagnostic_Dest C:oracle11g
Screen 6 : Network Configuration
select listener for 11g.
if you bkp already select i have my own bkp
Screen 7 : Recovery Options
Select i have my backup

9. Screen 8 : Summary
Click on Finish. If everything goes fine Check the upgrade results, then click the "Close"
button to leave the DBUA.
OLAP ERRORS CAN BE IGNORED
Post Upgrade Steps
Step 1
set oracle_home=oracle_home of 11g
set oracle_sid=orcl
Give the name of the db that is upgraded.
Check the listener is from 11g if not perform do the following
stop listener, start & check status and notice that it has STARTED FROM 11g HOME
step 2:
sqlplus / as sysdba
SQL> select insatnce_name,host,version FROM V$INSATNCE;--- IT SHOULD BE NEW
HOME
SQL> select comp_name,version,status from dba_registry-----to check for invalid objects.
SOME COMP_NAME LIKE OWB WILL BE OF OLD VERSION IT CAN BE DONE LATER
OLAP IS OFF IT IS OK.
SQL> select comp_name,version,status from dba_registry status='INVALID' OLAP WILL BE
OFF’;
SQL> select count(*) from dba_objects where status =’VALID’;
Check the count here and compare before the upgrade.
SQL> select banner from v$version;
BANNER ---------- it should show the 11g
Step 3: create Spfile from Pfile
Create a server parameter file with a initialization parameter file
SQL> create spfile from pfile;
This will create a spfile as a copy of the init.ora file located in %ORACLE_HOME%database

10. Start the Database with spfile:
SQL> shutdown immediate
SQL> startup
Check the 11g Alert log file for any Error. Database is ready to use now with Database Software
Oracle 11g.
SQL> show parameter spfile; -------------------- It should show the spfile
SQL> @?/rdbms/admin/utlu111s.sql
SQL> select count(*) from dba_objects wherestatus = ‘INVALID’;
SQL> @?/rdbms/admin/utlrp.sql
SQL> select count(*) from dba_objects where status = ‘INVALID’;
Backup upgraded (11g) database.
Create system statistics during a regular workload period -
otherwise non-appropriate values for the CBO will be used:
SQL> exec DBMS_STATS.GATHER_SYSTEM_STATS('start');
... – gather statistics while running a typical workload
SQL> exec DBMS_STATS.GATHER_SYSTEM_STATS('stop');
SQL> select pname NAME, pval1 VALUE, pval2 INFO
from aux_stats$;
NAME VALUE INFO
-------------------- ---------- ------------------------------
STATUS COMPLETED
DSTART 04-03-2009 12:30
DSTOP 05-03-2009 12:30
FLAGS 1
CPUSPEEDNW 1392.39
IOSEEKTIM 8.405
IOTFRSPEED 255945.605
...
Known Issues
errors after dbua and selecting the db
1.dbms_ldap package
2.gather stats
3.db has event or trace_event initialization parameters
ignore these errors
OLAP errors oralce analytical processing errors do come after summary these can be
ignored

11. Error ORA-06550 During Upgrade.
Description
Whilst running the upgrade you may encouner an ORA-06550 as detailled in Metalink
article 1066828.1.
Fix
This error can be ignored. However, you can avoid the error by applying patch 9315778 to
the 11.2 binaries prior to the upgrade starting.