10G To 11G

Upgrade Oracle 10g Release 2 from 10201 to 10204
Posted by Zahid on July 3, 2010. This post demonstrate a step by step guide to apply oracle patchset 10.2.0.4 (patch number 6810189) on 10.2.0.1 database. My current environment is Oracle 10gR2 (10.2.0.1) installed on Redhat Enterprise Linux 5 update 4 32-bit.
Preparing for the upgrade to 10.2.0.4

Stop all oracle components running like LISTENER, EM , ISQLPLUS and DB itself etc. /* Stop the isqlplus if running */ $ isqlplusctl stop iSQL*Plus 10.2.0.1.0 Copyright (c) 2003, 2005, Oracle. All rights reserved. Stopping iSQL*Plus ... iSQL*Plus stopped. /* Stop the EM dbconsole */ $ emctl stop dbconsole TZ set to US/Eastern Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0 Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved. http://ora10.home.com:1158/em/console/aboutApplication Stopping Oracle Enterprise Manager 10g Database Control ... ... Stopped. /* Stop the listener */ $ lsnrctl stop Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1))) The command completed successfully /* Shutdown the database itself */ $ sqlplus / as sysdba SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> Take a backup of Oracle Home and Database Once the oracle database is shutdown, take a cold backup of your database and a backup of your ORACLE_HOME. $cd /u01/apps/oracle/oradata/
/* All my data files , control files and log files are in a directory ora10g at the location /u01/apps/oracle/oradata/. I am going to make a tar archive of ora10g directory. If these files are at separate locations then add all those locations into the tar archive. And since this is just a test database and is very small in size so tar archive works much better then every thing else. But if it would be a production db and is big in size then I would consider other faster ways to take a cold backup of my data files. */ $ tar czf /home/oracle/ora10g.tar.gz ora10g $ echo $ORACLE_HOME /u01/apps/oracle/product/10.2.0/db_1 /* This is my ORACLE_HOME so I would make a tar archive of "db_1" directory. */ $ cd /u01/apps/oracle/product/10.2.0/ $ tar czf /home/oracle/oraHomeBackup.tar.gz db_1 Manage your data with TimeZone before upgrade
(Only perform this step if you have data or Scheduler jobs with TZ info) From 9i onwards Oracle has 2 datatypes that may have data stored affected by a update of the RDBMS DST (Daylight Saving Time) definitions, those are TIMESTAMP WITH LOCAL TIME ZONE (TSLTZ) and TIMESTAMP WITH TIME ZONE (TSTZ). If you have TZ data stored in your database you need to go through the following steps to ensure the integrity of your data while the database upgrade. Check which TIMEZONE version file you are currently using. SQL> select version from v$timezone_file; VERSION ---------2 If this gives 4 then you may simply proceed with the upgrade even if you have TZ data. If this gives higher then 4, look at the meta link note: Note 553812.1 If this gives lower then 4, perform the following steps: Download utltzpv4.sql and run it. SQL> @utltzpv4.sql DROP TABLE sys.sys_tzuv2_temptab CASCADE CONSTRAINTS * ERROR at line 1:
ORA-00942: table or view does not exist
Table created. DROP TABLE sys.sys_tzuv2_affected_regions CASCADE CONSTRAINTS * ERROR at line 1: ORA-00942: table or view does not exist
Table created. Your current timezone version is 2! . Do a select * from sys.sys_tzuv2_temptab; to see if any TIMEZONE data is affected by version 4 transition rules. . Any table with YES in the nested_tab column (last column) needs a manual check as these are nested tables. PL/SQL procedure successfully completed. Commit complete. SQL> /* Once the script finishes successfully execute the following query */ column table_owner format a4 column column_name format a18 select * from sys_tzuv2_temptab; TABL ---SYS SYS SYS SYS SYS SYS SYS SYS SYS TABLE_NAME -----------------------------SCHEDULER$_JOB SCHEDULER$_JOB SCHEDULER$_JOB SCHEDULER$_JOB SCHEDULER$_JOB SCHEDULER$_JOB_RUN_DETAILS SCHEDULER$_JOB_RUN_DETAILS SCHEDULER$_WINDOW SCHEDULER$_WINDOW COLUMN_NAME ROWCOUNT NES ------------------ ---------- --LAST_ENABLED_TIME 3 LAST_END_DATE 1 LAST_START_DATE 1 NEXT_RUN_DATE 1 START_DATE 1 REQ_START_DATE 1 START_DATE 1 LAST_START_DATE 2 NEXT_START_DATE 2
9 rows selected. If it returns no rows, there is nothing that needs to be done. Just proceed with the upgrade. If it retunrs the detail of columns that contain TZ data which may be affected by the upgrade, see metalink note: Note 553812.1 The Note 553812.1 states that if you see SYS owned SCHEDULER objects then it is safe to ignore them and proceed with the upgrade. But if you see user data or user created jobs here then you need to take a
backup of data before upgrade and restore it back after the upgrade. Remove any user created jobs and re-create them after the upgrade. Download Oracle Patchset 10.2.0.4 (6810189) Now is the time to prepare the oracle 10.2.0.4 patchset installer. You can download the patchset from For Linux x86 (32-bit): 10.2.0.4 for Linux x86 For Linux x86-64 (64-bit): 10.2.0.4 for Linux x86-64 Once downloaded login as root in another console and execute following: # xhost +SI:localuser:oracle
Install the patchset 10.2.0.4

Now come back to the oracle user console and move to the directory where you downloaded the patch and unzip the file. $ $ $ $ cd /home/oracle unzip p6810189_10204_Linux-x86.zip cd Disk1/ ./runInstaller
The first screen is welcome screen.
Provide the Oracle home details here (The oracle 10.2.0.1 home).
The installer will perform prerequisite checks on this screen. Make sure you see the message "The overall result of this check is passed" in the output.
Oracle configuration Manager allows you to associate your configuration with your metalink support account. You may skip this.
Installation Summary.
Installation progress.
Once progress shows 100%, you will be asked to perform some root specific actions.
Login as root # which dbhome /usr/local/bin/dbhome /* this shows the location of dbhome, oraenv and coraenv files rename them for 10.2.0.1 as the root.sh create new ones for 10.2.0.4 */ # cd /usr/local/bin/ # mv dbhome dbhome_10201 # mv oraenv oraenv_10201 # mv coraenv coraenv_10201 /* Now execute the script suggested by the installer. */ # /u01/apps/oracle/product/10.2.0/db_1/root.sh Running Oracle10 root.sh script... The following environment variables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /u01/apps/oracle/product/10.2.0/db_1 Enter the full pathname of the local bin directory: [/usr/local/bin]: Copying dbhome to /usr/local/bin ... Copying oraenv to /usr/local/bin ... Copying coraenv to /usr/local/bin ... Entries will be added to the /etc/oratab file as needed by Database Configuration Assistant when a database is created
Finished running generic part of root.sh script. Now product-specific root actions will be performed. When root.sh finishes successfully come back to installer and press ok. Then you should see the End of Installation page as below.
Press exit and your ORACLE_HOME is patched with 10.2.0.4 patchset. All your db's working under this ORACLE_HOME will become unusable unless you upgrade your database to 10.2.04 as well. $ sqlplus / as sysdba Connected to an idle instance. SQL> startup ORACLE instance started. Total System Global Area Fixed Size Variable Size Database Buffers Redo Buffers 608174080 1268896 171967328 427819008 7118848 bytes bytes bytes bytes bytes
Database mounted. ORA-01092: ORACLE instance terminated. Disconnection forced SQL> exit As you can see the database is unable to open and throwing the error ORA-01092. Lets look at the alert log file to know what actually happened. $ tail -f /u01/apps/oracle/admin/ora10g/bdump/alert_ora10g.log SMON: enabling cache recovery Fri Jul 2 15:30:15 2010 Errors in file /u01/apps/oracle/admin/ora10g/udump/ora10g_ora_12856.trc: ORA-00704: bootstrap process failure ORA-39700: database must be opened with UPGRADE option Fri Jul 2 15:30:15 2010 Error 704 happened during db open, shutting down database USER: terminating instance due to error 704 Instance terminated by USER, pid = 12856 ORA-1092 signalled during: ALTER DATABASE OPEN... $ The alert log states that the database has to be upgraded first using UPGRADE option to be able to OPEN normally.
Upgrade the database from 10.2.0.1 to 10.2.0.4

Now startup the database with upgrade option and run the pre-upgrade information tool to see if the database is okay for the upgrade and if there is some thing to be changed before starting the upgrade. $ cd $ORACLE_HOME/rdbms/admin $ sqlplus / as sysdba SQL> startup upgrade SQL> spool pre_upgrade.log SQL> @utlu102i.sql Oracle Database 10.2 Upgrade Information Utility 07-02-2010 17:39:25 . ********************************************************************** Database: ********************************************************************** --> name: ORA10G --> version: 10.2.0.1.0 --> compatible: 10.2.0.1.0 --> blocksize: 8192 . ********************************************************************** Tablespaces: [make adjustments in the current environment] ********************************************************************** --> SYSTEM tablespace is adequate for the upgrade. .... minimum required size: 488 MB .... AUTOEXTEND additional space required: 8 MB --> UNDOTBS1 tablespace is adequate for the upgrade. .... minimum required size: 400 MB
.... AUTOEXTEND additional space required: 370 MB --> SYSAUX tablespace is adequate for the upgrade. .... minimum required size: 245 MB .... AUTOEXTEND additional space required: 15 MB --> TEMP tablespace is adequate for the upgrade. .... minimum required size: 58 MB .... AUTOEXTEND additional space required: 38 MB --> EXAMPLE tablespace is adequate for the upgrade. .... minimum required size: 69 MB . ********************************************************************** Update Parameters: [Update Oracle Database 10.2 init.ora or spfile] ********************************************************************** -- No update parameter changes are required. . ********************************************************************** Renamed Parameters: [Update Oracle Database 10.2 init.ora or spfile] ********************************************************************** -- No renamed parameters found. No changes are required. . ********************************************************************** Obsolete/Deprecated Parameters: [Update Oracle Database 10.2 init.ora or spfile] ********************************************************************** -- No obsolete parameters found. No changes are required . ********************************************************************** Components: [The following database components will be upgraded or installed] ********************************************************************** --> Oracle Catalog Views [upgrade] VALID --> Oracle Packages and Types [upgrade] VALID --> JServer JAVA Virtual Machine [upgrade] VALID --> Oracle XDK for Java [upgrade] VALID --> Oracle Java Packages [upgrade] VALID --> Oracle Text [upgrade] VALID --> Oracle XML Database [upgrade] VALID --> Oracle Workspace Manager [upgrade] VALID --> Oracle Data Mining [upgrade] VALID --> OLAP Analytic Workspace [upgrade] VALID --> OLAP Catalog [upgrade] VALID --> Oracle OLAP API [upgrade] VALID --> Oracle interMedia [upgrade] VALID --> Spatial [upgrade] VALID --> Expression Filter [upgrade] VALID --> EM Repository [upgrade] VALID --> Rule Manager [upgrade] VALID . PL/SQL procedure successfully completed. SQL> spool off The output from utlu102i.sql shows that every thing is fine, no changes are required and the database is ready for upgrade. Lets start the upgrade process.
SQL> spool upgrade.log SQL> @catupgrd.sql . . . [output trimmed] . . . Oracle Database 10.2 Upgrade Status Utility 07-02-2010 18:13:40 . Component Status Version HH:MM:SS Oracle Database Server VALID 10.2.0.4.0 00:09:32 JServer JAVA Virtual Machine VALID 10.2.0.4.0 00:03:34 Oracle XDK VALID 10.2.0.4.0 00:00:29 Oracle Database Java Packages VALID 10.2.0.4.0 00:00:39 Oracle Text VALID 10.2.0.4.0 00:00:20 Oracle XML Database VALID 10.2.0.4.0 00:01:29 Oracle Workspace Manager VALID 10.2.0.4.3 00:00:39 Oracle Data Mining VALID 10.2.0.4.0 00:00:18 OLAP Analytic Workspace VALID 10.2.0.4.0 00:00:19 OLAP Catalog VALID 10.2.0.4.0 00:00:50 Oracle OLAP API VALID 10.2.0.4.0 00:00:45 Oracle interMedia VALID 10.2.0.4.0 00:03:48 Spatial VALID 10.2.0.4.0 00:01:29 Oracle Expression Filter VALID 10.2.0.4.0 00:00:09 Oracle Enterprise Manager VALID 10.2.0.4.0 00:01:16 Oracle Rule Manager VALID 10.2.0.4.0 00:00:07 . Total Upgrade Time: 00:25:52 DOC>####################################################################### DOC>####################################################################### DOC> DOC> The above PL/SQL lists the SERVER components in the upgraded DOC> database, along with their current version and status. DOC> DOC> Please review the status and version columns and look for DOC> any errors in the spool log file. If there are errors in the spool DOC> file, or any components are not VALID or not the current version, DOC> consult the Oracle Database Upgrade Guide for troubleshooting DOC> recommendations. DOC> DOC> Next shutdown immediate, restart for normal operation, and then DOC> run utlrp.sql to recompile any invalid application objects. DOC> DOC>####################################################################### DOC>####################################################################### DOC># SQL> spool off SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL>
When the upgrade script catupgrd.sql finishes shutdown the database and open the spool of the upgrade process and try to find out if any thing failed. If you see something failed try to fix it and re-run the upgrade process. The upgrade process may leave many objects invalid in the database. Perform a normal startup and run the utlrp.sql script to recompile any invalid objects. $ sqlplus / as sysdba Connected to an idle instance. SQL> startup SQL> spool recompile.log SQL> @utlrp.sql TIMESTAMP ------------------------------------------------------------------------------COMP_TIMESTAMP UTLRP_BGN 2010-07-02 18:23:16 DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC> DOC># The following PL/SQL block invokes UTL_RECOMP to recompile invalid objects in the database. Recompilation time is proportional to the number of invalid objects in the database, so this command may take a long time to execute on a database with a large number of invalid objects. Use the following queries to track recompilation progress: 1. Query returning the number of invalid objects remaining. This number should decrease with time. SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6); 2. Query returning the number of objects compiled so far. This number should increase with time. SELECT COUNT(*) FROM UTL_RECOMP_COMPILED; This script automatically chooses serial or parallel recompilation based on the number of CPUs available (parameter cpu_count) multiplied by the number of threads per CPU (parameter parallel_threads_per_cpu). On RAC, this number is added across all RAC nodes. UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel recompilation. Jobs are created without instance affinity so that they can migrate across RAC nodes. Use the following queries to verify whether UTL_RECOMP jobs are being created and run correctly: 1. Query showing jobs created by UTL_RECOMP SELECT job_name FROM dba_scheduler_jobs WHERE job_name like 'UTL_RECOMP_SLAVE_%'; 2. Query showing UTL_RECOMP jobs that are running SELECT job_name FROM dba_scheduler_running_jobs WHERE job_name like 'UTL_RECOMP_SLAVE_%';
PL/SQL procedure successfully completed. TIMESTAMP ------------------------------------------------------------------------------COMP_TIMESTAMP UTLRP_END 2010-07-02 18:23:50 PL/SQL procedure successfully completed. DOC> The following query reports the number of objects that have compiled DOC> with errors (objects that compile with errors have status set to 3 in DOC> obj$). If the number is higher than expected, please examine the error DOC> messages reported with each object (using SHOW ERRORS) to see if they DOC> point to system misconfiguration or resource constraints that must be DOC> fixed before attempting to recompile these objects. DOC># OBJECTS WITH ERRORS ------------------0 DOC> The following query reports the number of errors caught during DOC> recompilation. If this number is non-zero, please query the error DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors DOC> are due to misconfiguration or resource constraints that must be DOC> fixed before objects can compile successfully. DOC># ERRORS DURING RECOMPILATION --------------------------0 PL/SQL procedure successfully completed. SQL> spool off /* When the script utlrp.sql completes go ahead and verify if all the components are upgraded to 10.2.0.4 */ set lines 10000 set pages 1000 column comp_name format a40 column version format a12 column status format a6 select comp_name, version, status from sys.dba_registry; COMP_NAME ---------------------------------------Oracle Database Catalog Views Oracle Database Packages and Types Oracle Workspace Manager VERSION -----------10.2.0.4.0 10.2.0.4.0 10.2.0.4.3 STATUS -----VALID VALID VALID
JServer JAVA Virtual Machine Oracle XDK Oracle Database Java Packages Oracle Expression Filter Oracle Data Mining Oracle Text Oracle XML Database Oracle Rule Manager Oracle interMedia OLAP Analytic Workspace Oracle OLAP API OLAP Catalog Spatial Oracle Enterprise Manager 17 rows selected.
10.2.0.4.0 10.2.0.4.0 10.2.0.4.0 10.2.0.4.0 10.2.0.4.0 10.2.0.4.0 10.2.0.4.0 10.2.0.4.0 10.2.0.4.0 10.2.0.4.0 10.2.0.4.0 10.2.0.4.0 10.2.0.4.0 10.2.0.4.0
VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID
The above query shows that the database components are at 10.2.0.4 version now.
Restore the database back to 10.2.0.1 if any thing failed

Let's suppse the upgrade process fails, then you can always go back to 10.2.0.1 level be restoring the backup we took at the beginning of the process and start over the upgrade. Just shutdown the database and restore the backups as follows: $ echo $ORACLE_HOME /u01/apps/oracle/product/10.2.0/db_1 $ cd /u01/apps/oracle/product/10.2.0/ $ rm -fr db_1 $ tar xzf /home/oracle/oraHomeBackup.tar.gz * /* This will restore the old ORACLE_HOME */ $ cd /u01/apps/oracle/oradata/ $ rm -fr ora10g $ tar xzf /home/oracle/ora10g.tar.gz * /* This will restore a consistent copy of datafiles, controlfiles and redo log files */ Now start the database and see which version is it? $ sqlplus / as sysdba Connected to an idle instance. SQL> startup set lines 10000 set pages 1000 column comp_name format a40 column version format a12 column status format a6
select comp_name, version, status from sys.dba_registry; COMP_NAME ---------------------------------------Oracle Database Catalog Views Oracle Database Packages and Types Oracle Workspace Manager JServer JAVA Virtual Machine Oracle XDK Oracle Database Java Packages Oracle Expression Filter Oracle Data Mining Oracle Text Oracle XML Database Oracle Rules Manager Oracle interMedia OLAP Analytic Workspace Oracle OLAP API OLAP Catalog Spatial Oracle Enterprise Manager 17 rows selected. We are back again from where we started. VERSION -----------10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 10.2.0.1.0 STATUS -----VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID
Upgrade Oracle 10g from 10.2.0.1 to 10.2.0.4 (Single Instance)
Before database upgrade it is recommanded to backup the PRODUCTION database.
1. Stop all services of oracle
[oracle@ittestdb ~]$ echo $ORACLE_BASE /u01/app/oracle [oracle@ittestdb ~]$ echo $ORACLE_HOME /u01/app/oracle/product/10.2.0/db_1 [oracle@ittestdb ~]$ echo $ORACLE_SID orcl [oracle@ittestdb ~]$ [oracle@ittestdb ~]$ emctl stop dbconsole TZ set to Asia/Baghdad Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0 Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved. http://ittestdb.amardhaka.com:1158/em/console/aboutApplication Stopping Oracle Enterprise Manager 10g Database Control Stopped. [oracle@ittestdb ~]$ isqlplusctl stop iSQL*Plus 10.2.0.1.0 Copyright (c) 2003, 2005, Oracle. Stopping iSQL*Plus iSQL*Plus stopped. [oracle@ittestdb ~]$ All rights reserved.
[oracle@ittestdb ~]$ lsnrctl stop
LSNRCTL for Linux: Version 10.2.0.1.0 Production on 08-FEB-2010 13:17:18
Copyright (c) 1991, 2005, Oracle.
All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1))) The command completed successfully [oracle@ittestdb ~]$ sqlplus /as sysdba
SQL*Plus: Release 10.2.0.1.0 Production on Mon Feb 8 13:17:29 2010
All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 Production With the Partitioning, OLAP and Data Mining options
SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> exit Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 Production With the Partitioning, OLAP and Data Mining options [oracle@ittestdb ~]$ ps -ef|grep oracle root oracle oracle oracle 13754 32094 13755 13754 14525 13755 14526 13755 0 13:13 pts/1 0 13:13 pts/1 0 13:18 pts/1 0 13:18 pts/1 00:00:00 su oracle 00:00:00 -bash 00:00:00 ps -ef 00:00:00 grep oracle
[oracle@ittestdb ~]$
Step 2: Install the Database Patch Set
[oracle@ittestdb ~]$ export DISPLAY=10.13.5.95:0.0 [oracle@ittestdb ~]$ /u01/stage/patch/Disk1/runInstaller Starting Oracle Universal Installer
Checking installer requirements
Checking operating system version: must be redhat-3, SuSE-9, SuSE-10, redhat4, redhat-5, UnitedLinux-1.0, asianux-1, asianux-2 or asianux-3 Passed
All installer requirements met.
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2010-0208_01-22-19PM. Please wait [oracle@ittestdb ~]$ Oracle Universal Installer, Version 10.2.0.4.0 Production Copyright (C) 1999, 2008, Oracle. All rights reserved.
[oracle@ittestdb ~]$
Step 3 : Upgrade Database
[oracle@ittestdb ~]$ ps -ef|grep oracle root oracle oracle oracle 13754 32094 13755 13754 18304 13755 18305 13755 0 13:13 pts/1 0 13:13 pts/1 0 13:28 pts/1 0 13:28 pts/1 00:00:00 su oracle 00:00:00 -bash 00:00:00 ps -ef 00:00:00 grep oracle
[oracle@ittestdb ~]$ sqlplus /as sysdba
SQL*Plus: Release 10.2.0.4.0 Production on Mon Feb 8 13:28:53 2010
All Rights Reserved.
Connected to an idle instance.
SQL> STARTUP UPGRADE ORACLE instance started.
Total System Global Area 1224736768 bytes Fixed Size Variable Size 1267188 bytes 318769676 bytes
Database Buffers Redo Buffers Database mounted. Database opened. SQL>
889192448 bytes 15507456 bytes
SQL> STARTUP UPGRADE ORACLE instance started.
Total System Global Area 1224736768 bytes Fixed Size Variable Size Database Buffers Redo Buffers Database mounted. Database opened. SQL> SPOOL /u01/stage/patch/Disk1/upgrade_info.log SQL> @?/rdbms/admin/utlu102i.sql Oracle Database 10.2 Upgrade Information Utility . ********************************************************************** Database: ********************************************************************** > name: > version: > blocksize: . ********************************************************************** Tablespaces: [make adjustments in the current environment] ********************************************************************** > SYSTEM tablespace is adequate for the upgrade. . minimum required size: 488 MB . AUTOEXTEND additional space required: 8 MB > UNDOTBS1 tablespace is adequate for the upgrade. . minimum required size: 400 MB ORCL 10.2.0.1.0 8192 02-08-2010 13:30:50 1267188 bytes 318769676 bytes 889192448 bytes 15507456 bytes
> compatible: 10.2.0.1.0
. AUTOEXTEND additional space required: 370 MB > SYSAUX tablespace is adequate for the upgrade. . minimum required size: 246 MB . AUTOEXTEND additional space required: 16 MB > TEMP tablespace is adequate for the upgrade. . minimum required size: 58 MB . AUTOEXTEND additional space required: 38 MB > EXAMPLE tablespace is adequate for the upgrade. . minimum required size: 69 MB . ********************************************************************** Update Parameters: [Update Oracle Database 10.2 init.ora or spfile] ********************************************************************** No update parameter changes are required. . ********************************************************************** Renamed Parameters: [Update Oracle Database 10.2 init.ora or spfile] ********************************************************************** No renamed parameters found. No changes are required. . ********************************************************************** Obsolete/Deprecated Parameters: [Update Oracle Database 10.2 init.ora or spfile] ********************************************************************** No obsolete parameters found. No changes are required . ********************************************************************** Components: [The following database components will be upgraded or installed] ********************************************************************** > Oracle Catalog Views > Oracle Packages and Types > Oracle XDK for Java > Oracle Java Packages > Oracle Text > Oracle XML Database > Oracle Workspace Manager > Oracle Data Mining [upgrade] [upgrade] [upgrade] [upgrade] [upgrade] [upgrade] [upgrade] [upgrade] VALID VALID VALID VALID VALID VALID VALID VALID VALID
> JServer JAVA Virtual Machine [upgrade]
> OLAP Analytic Workspace > OLAP Catalog > Oracle OLAP API > Oracle interMedia > Spatial > Expression Filter > EM Repository > Rule Manager .
[upgrade] [upgrade] [upgrade] [upgrade] [upgrade] [upgrade] [upgrade] [upgrade]
VALID VALID VALID VALID VALID VALID VALID VALID
PL/SQL procedure successfully completed.
SQL> SPOOL OFF;
SQL> SPOOL /u01/stage/patch/Disk1/patch.log
SQL> @?/rdbms/admin/catupgrd.sql
..
177 178 179 180
PROCEDURE selectTablespace( tsname
IN varchar2 );
This procedure informs this package that the caller intends to do point-in-time recovery on the specified tablespace. This procedure
must 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 be called once for each tablespace in the recovery set. It alter selected tablespace read only, also checks datafiles in the selected tablespace. Input parameters: Exceptions: WRONG_ORDER (ORA-29301) wrong dbms_pitr package functions/procedure order. WRONG_TSNAME (ORA-29304) select tablespace does not exist NOT_READ_ONLY (ORA-29305) cannot alter the tablespace read only FILE_OFFLINE (ORA-29306) datafile is not online tsname The tablespace name.
SQL> SQL> SQL> SQL> SPOOL OFF
SQL> SHUTDOWN IMMEDIATE Database closed. Database dismounted. ORACLE instance shut down. SQL> STARTUP ORACLE instance started.
Total System Global Area 1224736768 bytes Fixed Size Variable Size 1267188 bytes 335546892 bytes
Database Buffers Redo Buffers Database mounted. Database opened. SQL>
872415232 bytes 15507456 bytes
To compile invalid objects
SQL> @?/rdbms/admin/utlrp.sql
..
TIMESTAMP
COMP_TIMESTAMP UTLRP_END
2010-02-08 15:02:23
DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#
OBJECTS WITH ERRORS
DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#
ERRORS DURING RECOMPILATION
SQL> SQL> select comp_name, version, status from sys.dba_registry;
COMP_NAME TATUS
VERSION
Oracle Database Catalog Views 10.2.0.4.0 VALID
Oracle Database Packages and Types 10.2.0.4.0 VALID
Oracle Workspace Manager 10.2.0.4.3 VALID
JServer JAVA Virtual Machine 10.2.0.4.0 VALID
Oracle XDK 10.2.0.4.0 VALID
Oracle Database Java Packages 10.2.0.4.0 VALID
Oracle Expression Filter 10.2.0.4.0 VALID
Oracle Data Mining 10.2.0.4.0 VALID
Oracle Text 10.2.0.4.0 VALID
Oracle XML Database 10.2.0.4.0 VALID
Oracle Rule Manager 10.2.0.4.0 VALID
Oracle interMedia 10.2.0.4.0 VALID
OLAP Analytic Workspace 10.2.0.4.0 VALID
Oracle OLAP API 10.2.0.4.0 VALID
OLAP Catalog 10.2.0.4.0 VALID
Spatial ALID
10.2.0.4.0
Oracle Enterprise Manager 10.2.0.4.0 VALID
SQL>exit
Now Start other services (listener, EM, iSQLPlus)
Upgrade Oracle from 10.2.0.1 To 10.2.0.4

1. Patch Set Overview Patch set release 10.2.0.4. Before installing this patch set you must be need 10.2.0.1 version. 2. Requirements Oracle DB : Oracle 10.2.0.1 (later) Operating System: Windows
3. Pre - Installation Tasks 1. Identify prior installation Before installing this patch you must install oracle 10.2.0.1 (or later version) 2. Download Patch set Download 6810189 patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory. 3. Shutdown oracle database. C:\>set oracle_sid= GOLDLINK C:\>sqlplus /nolog SQL*Plus: Release 10.2.0.1.0 - Production on Tue Nov 13 10:49:26 2007 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. SQL> connect sys@GOLDLINK as sysdba Enter password: Connected. SQL> SHUTDOWN
Database closed. Database dismounted. ORACLE instance shut down. 4. Stop all services C:\>set oracle_sid=GoldLink C:\>net stop OracleDBConsoleGOLDLINK The OracleDBConsoleGOLDLINK service is stopping................ The OracleDBConsoleGOLDLINK service was stopped successfully.
C:\>net stop OracleServiceGOLDLINK The OracleServiceGOLDLINK service is stopping. The OracleServiceGOLDLINK service was stopped successfully.
C:\>net stop OracleOraDB10g_Home1iSQL*Plus.. The OracleOraDb10g_home1iSQL*Plus service was stopped successfully. C:\>net stop OracleOraDB10g_Home1TNSListener The OracleOraDb10g_home1TNSListener service is stopping. The OracleOraDb10g_home1TNSListener service was stopped successfully. Note: while patch installation time If you face Distributed Transaction Coordinator still running. You should be stop this service C:\>net stop msdtc The Distributed Transaction Coordinator service is stopping. The Distributed Transaction Coordinator service was stopped successfully. 4. Backup your database. Oracle recommends that you create a backup of the Oracle 10g installation before you install the patch set. 5. Check Tablespace Sizes and Set Parameter Values Review the following sections before upgrading a database. 8. Upgrade the Database After you install the patch set, you must perform the following steps on every database
associated with the upgraded Oracle home: 1. Start all services 2. Connect sys user C:\> sqlplus /NOLOG SQL> CONNECT SYS/SYS_password AS SYSDBA 3. Enter the following SQL*Plus commands: SQL> STARTUP UPGRADE SQL> SPOOL patch.log SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catupgrd.sql SQL> SPOOL OFF Review the patch.log file for errors and inspect the list of components that is displayed at the end of catupgrd.sql script. This list provides the version and status of each SERVER component in the database. If necessary, rerun the catupgrd.sql script after correcting any problems. 4. Restart the database:
SQL> SHUTDOWN SQL> STARTUP 5. Compile Invalid Objects Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended. SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql SQL> select * from v$version; BANNER ---------------------------------------------------------------Oracle Database 10g Release 10.2.0.4.0 - Production
PL/SQL Release 10.2.0.4.0 - Production CORE 10.2.0.4.0 Production TNS for 32-bit Windows: Version 10.2.0.4.0 - Production NLSRTL Version 10.2.0.4.0 - Production
step by step oracle database 10g upgrade from 10.2.0.1 to 10.2.0.4

April 18th, 2011 in Oracle Database 10G posts Redhat Enterprise Linux by admin
Requirements: Oracle database 10g patch set 10.2.0.4 download from www.metalink.oracle.com Step 1: Prerequisites check to before applying the patch set (6810189). Check your dba_registry view oracle database components status is valid or not, version is 10.2.0.1. Have a look at the below output Column comp_name format a40 Column version format a12 Column status format a6 Select comp_name, version, status from sys.dba_registry; COMP_NAME VERSION STATUS
Oracle Database Catalog Views 10.2.0.1.0 VALID
Oracle Database Packages and Types 10.2.0.1.0 VALID Oracle Workspace Manager JServer JAVA Virtual Machine 10.2.0.1.0 VALID 10.2.0.1.0 VALID
Oracle XDK Oracle Database Java Packages Oracle Expression Filter Oracle Data Mining Oracle Text Oracle XML Database Oracle Rules Manager Oracle interMedia OLAP Analytic Workspace Oracle OLAP API OLAP Catalog Spatial Oracle Enterprise Manager 17 rows selected. Check your v$version view SQL> select * from v$version; BANNER
10.2.0.1.0 VALID 10.2.0.1.0 VALID 10.2.0.1.0 VALID 10.2.0.1.0 VALID 10.2.0.1.0 VALID 10.2.0.1.0 VALID 10.2.0.1.0 VALID 10.2.0.1.0 VALID 10.2.0.1.0 VALID 10.2.0.1.0 VALID 10.2.0.1.0 VALID 10.2.0.1.0 VALID 10.2.0.1.0 VALID
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 Prod PL/SQL Release 10.2.0.1.0 Production CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0 Production NLSRTL Version 10.2.0.1.0 Production Check your database objects are valid or not SQL> select object_name,status from dba_objects where status=INVALID; No rows selected In my environment there are no invalid objects. If you have any invalid objects then you have to really Validate your database objects through the below scripts SQL> exec utl_recomp.recomp_serial (); -> this is for all users objects across the database
Then stop all the process like sql, emctl, tnslistener and shutdown your database. $ sqlplus / as sysdba SQL> shutdown immediate Database closed Database dismounted. ORACLE instance shut down. $ isqlplusctl stop iSQL*Plus 10.2.0.1.0 Copyright (c) 2003, 2005, Oracle. All rights reserved. Stopping iSQL*Plus iSQL*Plus stopped. $ emctl stop dbconsole TZ set to US/Eastern
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0 Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved http://ora10.home.com:1158/em/console/aboutApplication Stopping Oracle Enterprise manager 10g database Control .Stoped $ lsnrctl stop Copyright (c) 1991, 2005, Oracle. All rights reserved. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1))) The command completed successfully Step 2: Cold Backup of your oracle database 10g and $ORACLE_HOME using Operating system Command Step 3: Manage your data with Time Zone before upgrade In my environment there are no data and scheduler jobs with Time Zone information thats why I skip the step. If you have huge volume of data and scheduler jobs means please follow the below steps SQL> select version from v$timezone_file; Version 2
If this gives 4 then you may simply proceed with the upgrade even if you have TZ data. If this gives higher then 4 look at the Meta link note: Note 553812.1 If this gives lower then 4 perform the following steps: Download utltzpv4.sql from www.metalink.oracle.com and run it. SQL> @utltzpv4.sql DROP TABLE sys.sys_tzuv2_temptab CASCADE CONSTRAINTS ERROR at line 1: ORA-00942: table or view does not exist Table created. DROP TABLE sys.sys_tzuv2_affected_regions CASCADE CONSTRAINTS ERROR at line 1: ORA-00942: table or view does not exist Table created. Your current timezone version is 2! Do a select * from sys.sys_tzuv2_temptab; to see if any TIMEZONE data is affected by version 4 transition rules. Any table with YES in the nested_tab column (last column) needs a manual check as these are nested tables. PL/SQL procedure successfully completed. Commit complete. SQL> Once the script finishes successfully execute the following query
column table_owner format a4 column column_name format a18 select * from sys_tzuv2_temptab; TABL TABLE_NAME COLUMN_NAME ROWCOUNT NES
---- ------------------------------ ------------------ ---------SYS SYS SYS SYS SYS SYS SYS SYS SYS SCHEDULER$_JOB SCHEDULER$_JOB SCHEDULER$_JOB SCHEDULER$_JOB SCHEDULER$_JOB SCHEDULER$_JOB_RUN_DETAILS SCHEDULER$_JOB_RUN_DETAILS SCHEDULER$_WINDOW SCHEDULER$_WINDOW LAST_ENABLED_TIME LAST_END_DATE LAST_START_DATE NEXT_RUN_DATE START_DATE REQ_START_DATE START_DATE LAST_START_DATE NEXT_START_DATE 3 1 1 1 1 1 1 2 2
9 rows selected. Step 3: Applying Oracle database 10g patch set (Patch number 6810189) After downloaded the patch set, you have login as a root user and execute the following # xhost +SI:localuser:oracle Install the patch set 10.2.0.4 $ cd /home/oracle $ unzip p6810189_10204_Linux-x86.zip $ cd Disk1/
$ ./runInstaller
Click Next to proceed the next step
Here you should provide your $ORACLE_HOME(10.2.0.1) detail
Click Next
Click Next
Click Install
Click OK and run the above script as a root user
Then startup database with upgrade option otherwise the below error will come and you can see the error in the alert log file $ sqlplus / as sysdba Connected to an idle instance. SQL> startup
ORACLE instance started. Total System Global Area 608174080 bytes Fixed Size Variable Size Database Buffers Redo Buffers Database mounted. ORA-01092: ORACLE instance terminated. Disconnection forced SQL> exit $ tail -f /opt/oracle/admin/test/bdump/alert_ora10g.log SMON: enabling cache recovery Fri Jul 2 15:30:15 2010 Errors in file /u01/apps/oracle/admin/ora10g/udump/ora10g_ora_12856.trc: ORA-00704: bootstrap process failure ORA-39700: database must be opened with UPGRADE option Fri Jul 2 15:30:15 2010 Error 704 happened during db open, shutting down database USER: terminating instance due to error 704 Instance terminated by USER, pid = 12856 ORA-1092 signalled during: ALTER DATABASE OPEN 1268896 bytes 171967328 bytes 427819008 bytes 7118848 bytes
Now startup the database with upgrade option and run the pre-upgrade information tool to see if there are any recommendation. If there is any recommendation then you have to really follow the recommendations. Lets start the upgrade process. $ cd $ORACLE_HOME/rdbms/admin SQL> spool upgrade.log SQL> @catupgrd.sql [output trimmed] Oracle Database 10.2 Upgrade Status Utility Component Oracle Database Server JServer JAVA Virtual Machine Oracle XDK Oracle Database Java Packages Oracle Text Oracle XML Database Oracle Workspace Manager Oracle Data Mining OLAP Analytic Workspace OLAP Catalog Oracle OLAP API Oracle interMedia Spatial Status VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID VALID
07-02-2010 18:13:40 Version HH:MM:SS 10.2.0.4.0 00:09:32
10.2.0.4.0 00:03:34 10.2.0.4.0 00:00:29 10.2.0.4.0 00:00:39 10.2.0.4.0 00:00:20 10.2.0.4.0 00:01:29 10.2.0.4.3 00:00:39 10.2.0.4.0 00:00:18 10.2.0.4.0 00:00:19 10.2.0.4.0 00:00:50 10.2.0.4.0 00:00:45 10.2.0.4.0 00:03:48 10.2.0.4.0 00:01:29
Oracle Expression Filter Oracle Enterprise Manager Oracle Rule Manager Total Upgrade Time: 00:25:52
VALID VALID VALID
10.2.0.4.0 00:00:09 10.2.0.4.0 00:01:16 10.2.0.4.0 00:00:07
DOC>##################################### DOC>###################################### DOC> DOC> The above PL/SQL lists the SERVER components in the upgraded DOC> database, along with their current version and status. DOC> DOC> Please review the status and version columns and look for DOC> any errors in the spool log file. If there are errors in the spool DOC> file, or any components are not VALID or not the current version, DOC> consult the Oracle Database Upgrade Guide for troubleshooting DOC> recommendations. DOC> DOC> Next shutdown immediate, restart for normal operation, and then DOC> run utlrp.sql to recompile any invalid application objects. DOC> DOC>########################################## DOC>######################################
DOC># SQL> spool off SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> When the upgrade script catupgrd.sql finishes shutdown the database and open the spool of the upgrade process and try to find out if any thing failed. If you see something failed try to fix it and re-run the upgrade process. The upgrade process may leave many objects invalid in the database. Perform a normal startup and run the utlrp.sql script to recompile any invalid objects. $ sqlplus / as sysdba Connected to an idle instance. SQL> startup SQL> spool recompile.log SQL> @utlrp.sql TIMESTAMP ============== COMP_TIMESTAMP UTLRP_BGN 2010-07-02 18:23:116 DOC> The following PL/SQL block invokes UTL_RECOMP to recompile invalid DOC> objects in the database. Recompilation time is proportional to the DOC> number of invalid objects in the database, so this command may take
DOC> a long time to execute on a database with a large number of invalid DOC> objects. DOC> DOC> Use the following queries to track recompilation progress: DOC> DOC> 1. Query returning the number of invalid objects remaining. This DOC> DOC> DOC> DOC> 2. Query returning the number of objects compiled so far. This number DOC> DOC> DOC> DOC> This script automatically chooses serial or parallel recompilation DOC> based on the number of CPUs available (parameter cpu_count) multiplied DOC> by the number of threads per CPU (parameter parallel_threads_per_cpu). DOC> On RAC, this number is added across all RAC nodes. DOC> DOC> UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel DOC> recompilation. Jobs are created without instance affinity so that they should increase with time. SELECT COUNT(*) FROM UTL_RECOMP_COMPILED; number should decrease with time. SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC> can migrate across RAC nodes. Use the following queries to verify DOC> whether UTL_RECOMP jobs are being created and run correctly: DOC> DOC> 1. Query showing jobs created by UTL_RECOMP DOC> DOC> DOC> DOC> 2. Query showing UTL_RECOMP jobs that are running DOC> DOC> DOC># PL/SQL procedure successfully completed. TIMESTAMP ============= COMP_TIMESTAMP UTLRP_END 2010-07-02 18:23:50 PL/SQL procedure successfully completed. DOC> The following query reports the number of objects that have compiled DOC> with errors (objects that compile with errors have status set to 3 in DOC> obj$). If the number is higher than expected, please examine the error DOC> messages reported with each object (using SHOW ERRORS) to see if they DOC> point to system misconfiguration or resource constraints that must be SELECT job_name FROM dba_scheduler_running_jobs WHERE job_name like UTL_RECOMP_SLAVE_%; SELECT job_name FROM dba_scheduler_jobs WHERE job_name like UTL_RECOMP_SLAVE_%;
DOC> fixed before attempting to recompile these objects. DOC># OBJECTS WITH ERROR =============== 0 DOC> The following query reports the number of errors caught during DOC> recompilation. If this number is non-zero, please query the error DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors DOC> are due to misconfiguration or resource constraints that must be DOC> fixed before objects can compile successfully. DOC># ERRORS DURING RECOMPILATION --------------------------0 PL/SQL procedure successfully completed. SQL> spool off Step 5: Post installation steps set lines 10000 set pages 1000 column comp_name format a40
column version format a12 column status format a6 select comp_name, version, status from sys.dba_registry; COMP_NAME ============ Oracle Database Catalog Views Oracle Database Packages and Types Oracle Workspace Manager JServer JAVA Virtual Machine Oracle XDK Oracle Database Java Packages Oracle Expression Filter Oracle Data Mining Oracle Text Oracle XML Database Oracle Rule Manager Oracle interMedia OLAP Analytic Workspace Oracle OLAP API OLAP Catalog Spatial VERSION STATUS
=========== ===== 10.2.0.4.0 VALID 10.2.0.4.0 VALID 10.2.0.4.3 VALID 10.2.0.4.0 VALID 10.2.0.4.0 VALID 10.2.0.4.0 VALID 10.2.0.4.0 VALID 10.2.0.4.0 VALID 10.2.0.4.0 VALID 10.2.0.4.0 VALID 10.2.0.4.0 VALID 10.2.0.4.0 VALID 10.2.0.4.0 VALID 10.2.0.4.0 VALID 10.2.0.4.0 VALID 10.2.0.4.0 VALID
Oracle Enterprise Manager 17 rows selected. SQL> select * from v$version; BANNER
10.2.0.4.0 VALID
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 Prod PL/SQL Release 10.2.0.4.0 Production CORE 10.2.0.4.0 Production
TNS for Linux: Version 10.2.0.4.0 Production NLSRTL Version 10.2.0.4.0 Production Check your database objects are valid or not SQL> select object_name,status from dba_objects where status=INVALID; No rows selected.
More 10.2.0.4 to 11.2.0.1 upgrades

Filed under: 10g, 11g, Oracle kkempf @ 9:38 am
Rate This
With the end of Premier support for RDBMS 10.2 coming in July of next year (Officially from Oracle here), I started doing some more 10g to 11g migrations. 6 upgrades later, I am happy to say that its been successful across the board. In the interest of brevity, Im going to skip all the detailed checks outlined in 837570.1 and cut to the chase: Make sure you have a backup before you start the upgrade. The rest of this assumes a vanilla database, meaning you dont have any of the issues outlined in 836570.1. Like you dont have duplicate items in SYS and SYSTEM schemas, you are smart enough to already have a SYSAUX tablespace, you understand what the new connect role is, you dont have TIMESTAMP WITH TIMEZONE Datatypes in the database, etc, etc, etc. 1. 2. Install 11g in a new home Run the 11g_home/rdbms/admin/utlu112i.sql script against your 10gR2 database and see what it says. In my case: a. b. c. d. e. 3. 4. 5. 6. 7. 8. 9. Archivelog formats now require %r in them user/background/core dump destination parameters are depricated (I simply removed them and went with the new defaults) minimum sga_target of 700M & minimum java_pool_size of 128M (I allowed this for the upgrade, then cut it back) Empty the recycle bin: purge dba_recyclebin exec dbms_stats.gather_schema_stats vs. SYS and SYSMAN schemas
Run 10g_home/rdbms/admin/utlrp to recompile invalids Shutdown the 10g instance Source the new Oracle Home so $ORACLE_HOME points to the 11.2 home Copy the new/modified initSID.ora file to the 11g_home/dbs directory; copy the listener.ora and tnsnames.ora file from the 10g home to the 11g_home/network/admin directory startup upgrade pfile=initSID.ora (11g version) Run 11g_home/rdbms/admin/catupgrd.sql (catalog upgrade, this script takes quite a while to finish, about 1.5 hours on a wimpy 2 CPU VM) Run 11g_home/rdbms/admin/utlu112s.sql (the doc incorrectly identifies this as utlu111s.sql)
10. Run 11g_home/rdbms/admin/utlrp.sql (recompile) 11. Check your compatible parameter (in my case I simply changed it from 10.2.0.2.0 to 11.2.0.1.0) and restart the database if required 12. Start your listener
Oracle Database 11.2 Post-Upgrade Status Tool . Component Status . Oracle Server . VALID JServer JAVA Virtual Machine . VALID Oracle Workspace Manager . VALID OLAP Analytic Workspace . OPTION OFF OLAP Catalog . OPTION OFF
12-15-2009 09:34:18 Version 11.2.0.1.0 11.2.0.1.0 11.2.0.1.0 10.2.0.2.0 10.2.0.2.0 HH:MM:SS 00:31:18 00:11:33 00:01:00 00:00:00 00:00:00
Oracle OLAP API . Oracle Enterprise Manager . Oracle XDK . Oracle Text . Oracle XML Database . Oracle Database Java Packages . Oracle Multimedia . Spatial . Oracle Expression Filter . Oracle Rule Manager . Gathering Statistics . Total Upgrade Time: 01:24:57
OPTION OFF VALID VALID VALID VALID VALID VALID OPTION OFF VALID VALID
10.2.0.2.0 11.2.0.1.0 11.2.0.1.0 11.2.0.1.0 11.2.0.1.0 11.2.0.1.0 11.2.0.1.0 10.2.0.2.0 11.2.0.1.0 11.2.0.1.0
00:00:00 00:12:34 00:01:29 00:01:17 00:04:45 00:00:33 00:04:37 00:00:00 00:00:21 00:00:11 00:15:12
Step By Step Manual Database Upgrade to 11.2.0.2

Compatibility Matrix
Minimum Version of the database that can be directly upgraded to Oracle 11g Release 2 Source Database 9.2.0.8 or higher 10.1.0.5 or higher 10.2.0.2 or higher 11.1.0.6 or higher Target Database 11.2.x 11.2.x 11.2.x 11.2.x
The following database version will require an indirect upgrade path. Source Database ---> Upgrade Path for Target Database--->Target Database 7.3.3 (or lower)-----> 7.3.4 ---> 9.2.0.8 ---->11.2.x 8.0.5 (or lower)----> 8.0.6 ---> 9.2.0.8 ---->11.2.x 8.1.7 (or lower)----> 8.1.7.4---> 10.2.0.4---->11.2.x 9.0.1.3 (or lower)----> 9.0.1.4-- ->10.2.0.4---->11.2.x 9.2.0.7(or lower)---->9.2.0.8---->11.2.x Here I am upgrading my Oracle 10.2.0.4 database to Oracle 11.2.0.2 1. Copy Pre upgrade Information gathering Script:
Log in to the system as the owner of the Oracle Database 11g Release 2 (11.2) Oracle home directory. Copy the Pre-Upgrade Information Tool (utlu112i.sql) and utltzuv2.sql from the Oracle Database 11gRelease 2 (11.2) ORACLE_HOME/rdbms/admin directory to a directory outside of the Oracle home, such as the temporary directory on your system.
$ORACLE_HOME/rdbms/admin/utlu112i.sql
2. Execute Pre Upgrade Script:
Should be change to the directory where utlu112i.sql had been copied in the previous step. Start SQL*Plus and connect to the database instance as a user with SYSDBA privileges. Then run and spool the utlu112i.sql file. Please note that the database should be started using the Source Oracle Home.
$ sqlplus '/ as sysdba' SQL> spool upgrade_info.log SQL> @utlu112i.sql SQL> spool off SQL>
Check the spool file and examine the output of the upgrade information tool.
3. Check for the integrity of the source database: Check for the integrity of the source database prior to starting the upgrade by downloading and running dbupgdiag.sql script from below My Oracle Support article Note 556610.1 Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql) (Avoid this step if dont have support access)
If the dbupgdiag.sql script reports any invalid objects, run $ORACLE_HOME/rdbms/admin/utlrp.sql (multiple times) to validate the invalid objects in the database, until there is no change in the number of invalid objects. $ cd $ORACLE_HOME/rdbms/admin $ sqlplus "/ as sysdba" SQL> @utlrp.sql
After validating the invalid objects, re-run dbupgdiag.sql in the database once again and make sure that everything is fine. 4. Check that National Characterset:
Check that National Characterset (NLS_NCHAR_CHARACTERSET) is UTF8 and AL16UTF16. select value from NLS_DATABASE_PARAMETERS where parameter = 'NLS_NCHAR_CHARACTERSET'; If this is UTF8 or AL16UTF16 then no action is needed. If is not UTF8 or AL16UTF16 then refer the following article Note 276914.1 The National Character Set in Oracle 9i and 10g.
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
$ sqlplus "/as sysdba" SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;
6. Ensure that no files need media recovery: Sql> SELECT * FROM v$recover_file;
7. Stop the listener for the database:
Make pfile from spfile;
$ lsnrctl stop
8. Suhtdown the Database:
Shutdown the database.
$ sqlplus "/as sysdba" SQL> shutdown immediate;
9. Back Up the Database: 1- Perform Cold Backup (or) 2- Take a backup using RMAN
Connect to RMAN: rman "target / nocatalog" RUN { ALLOCATE CHANNEL chan_name TYPE DISK; BACKUP DATABASE FORMAT '%U' TAG before_upgrade; BACKUP CURRENT CONTROLFILE TO ''; }
10 Backup and change pfile:
Make a backup of the init.ora file. Comment out obsolete parameters
* The DIAGNOSTIC_DEST initialization parameter replaces the USER_DUMP_DEST, BACKGROUND_DUMP_DEST.
Note: Once the Parameter file is modified as per your requirement, copy the file to $ORACLE_HOME/dbs (11g Oracle Home )
11 Set Environment Variables:
If your operating system is UNIX then complete this step, else skip to next Step. 1. Make sure the following environment variables point to the Oracle 11g Release directories:
- ORACLE_BASE - ORACLE_HOME - PATH $ export ORACLE_HOME=<location of oracle 11.2> $ export PATH=$ORACLE_HOME/bin:$PATH $ export ORACLE_BASE=<oracle_base set during installation></oracle_base set during installation></lo cation of oracle 11.2> Note : If ORACLE_BASE is not known, after setting Path towards 11g Oracle Home, execute 'orabase', which will point the location of base. $ orabase /uo1/app/oracle
2. Update the oratab entry, to set the new ORACLE_HOME pointing towards ORCL and disable automatic startup
Sample /etc/oratab #orcl:/opt/oracle/product/10.2/db_1:N orcl:/opt/oracle/product/11.2/db_1:N
Note : After /etc/oratab is updated to have sid and Oracle Home (11.2), you can execute oraenv (/usr/local/bin/oraenv) and set the environment. The input has to be the sid which is entered in /etc/oratab against 11g home. for Instance, [oracle@localhost ~]$ . oraenv ORACLE_SID = [orcl] ? orcl The Oracle base for ORACLE_HOME=/opt/oracle/product/11.2/db_1 is /u01/app/oracle [oracle@localhost ~]$
12 Upgrade Database:
At the operating system prompt, change to the $ORACLE_HOME/rdbms/admin directory of 11gR2 Oracle Home.
$ cd $ORACLE_HOME/rdbms/admin $ sqlplus "/ as sysdba" SQL> startup UPGRADE
Set the system to spool results to a log file for later verification after the upgrade is completed and start the upgrade script.
SQL> set echo on SQL> SPOOL upgrade.log SQL> @catupgrd.sql SQL> spool off
These measures are an important final step to ensure the integrity and consistency of the newly upgraded Oracle Database software. Also, if you encountered a message listing obsolete initialization parameters when you started the database for upgrade, then remove the obsolete initialization parameters from the parameter file before restarting. If necessary, convert the SPFILE to a PFILE so you can edit the file to delete parameters.
Post Upgrade Steps
13 Post Upgrade: Start the database and run the Post-Upgrade Status Tool $ORACLE_HOME/rdbms/admin/utlu112s.sql which provides a summary of the upgrade at the end of the spool log. It displays the status of the database components in the upgraded database and the time required to complete each component upgrade. Any errors that occur during the upgrade are listed with each component and must be addressed $ sqlplus "/as sysdba" SQL> STARTUP SQL> @utlu112s.sql
14 Recompile Invalid Objects: This script can be run concurrently with utlrp.sql. Run utlrp.sql to recompile any remaining stored PL/SQL and Java code in another session. SQL> @utlrp.sql
15 Check for the integrity of the source database:
Check for the integrity of the upgraded database by running dbupgdiag.sql script from below Metalink article Note 556610.1 Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql) If the dbupgdiag.sql script reports any invalid objects, run $ORACLE_HOME/rdbms/admin/utlrp.sql (multiple times) to validate the invalid objects in the database, until there is no change in the number of invalid objects. After validating the invalid objects, re-run dbupgdiag.sql in the upgraded database once again and make sure that everything is fine. 16 Configure & Start Listener.ora : Modify the listener.ora file: For the upgraded instance(s) modify the ORACLE_HOME parameter to point to the new ORACLE_HOME. Start the listener :
lsnrctl start
17 Crosscheck Environment Variables:
Set Environment Variables 1. Make sure the following environment variables point to the Oracle 11g Release directories: - ORACLE_BASE - ORACLE_HOME - PATH Also check that your oratab file and any client scripts that set the value of ORACLE_HOME point to the Oracle Database 11g Release 2 (11.2) home. Note : If you are upgrading a cluster database, then perform these checks on all nodes in which this cluster database has instances configured. 2. Modify /etc/oratab entry to use automatic startup SID:ORACLE_HOME:Y
For Instance, orcl:/opt/oracle/product/11.2/db_1:Y
18 Spfile from Pfile: Edit init.ora: - If you changed the CLUSTER_DATABASE parameter prior the upgrade set it back to TRUE - Migrate your initialization parameter file to a server parameter file. 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/dbs (UNIX) & %ORACLE_HOME%\database (Windows). 19 Start the Database with spfile: Shutdown the database: Sql> shutdown immediate Now start the database it will user spfile Sql> startup Check the Alert log file for any Error. Database is ready to use now.
Manual Upgrade Database from Oracle 10.2.0.4 to Oracle 11.2.0.2

More Sharing ServicesShare|Share on facebookShare on twitterShare on emailShare on print Introduction: This document applies for Oracle 10.2.0.4 Ent. Edition on Red Hat Linux 5. This document will guide you how to upgrade Oracle 10.2.0.4 Ent Edition single Instance to Oracle 11.2.0.2 Ent. Edition. The following topics guide you through the process of performing a manual upgrade. They assume that you have previously run the Pre-Upgrade Information Tool Backing up the Database Preparing the New Oracle Home
Manually Upgrading the Database Troubleshooting the Upgrade
Cancelling the Upgrade Backing Up the Database After running the Pre-Upgrade Information Tool and cleanly shutting down the instance, Oracle recommends that you back up the database as described in this section. If you encounter problems with the upgrade and wish to abandon the upgrade completely, then you must restore the database from this backup. Therefore, Oracle recommends that you back up your database now as a precaution. There are two ways to take backup: 1. Cold Backup 2. Rman Backup Cold Backup: Copy all the datafiles, control files and Redo log files to a different location. Rman Backup: Sign on to RMAN: 1. rman target / nocatalog 2. Issue the following RMAN commands: RUN { ALLOCATE CHANNEL chan_name TYPE DISK; BACKUP DATABASE FORMAT some_backup_directory%U TAG before_upgrade; BACKUP CURRENT CONTROLFILE FORMAT controlfile location and name; } Preparing the New Oracle Home After backing up the database to be upgraded, prepare the new Oracle home in a new location. Do this for any release of Oracle Database for which you are upgrading, whether the database is release 11.2 or earlier. To prepare the new Oracle home 1. Copy configuration files from the Oracle home of the database being upgraded to the new Oracle Database 11gRelease 2 (11.2) Oracle home: 2. If your parameter file resides within the old environments Oracle home, then copy it to the new Oracle home. By default, Oracle looks for the parameter file in the ORACLE_HOME/dbs directory on Linux or UNIX platforms. The parameter file can reside anywhere you wish, but it should not reside in the old environments Oracle home after you upgrade to Oracle Database 11g Release 2 (11.2).
Note: It might be necessary to create a text initialization parameter file (PFILE) from the server parameter file (SPFILE) so that you can edit the initialization parameters. Sql> CREATE pfile FROM spfile; 3. If you have a password file that resides within the old environments Oracle home, then move or copy the password file to the new Oracle Database 11g Release 2 (11.2) Oracle home.The name and location of the password file are operating system-specific. On Linux or UNIX platforms, the default password file is orapwsid, located in the ORACLE_HOME/dbs directory. In both cases, sid is your Oracle instance ID. 4. The Pre-Upgrade Information Tool displays any deprecated parameters and obsolete parameters it finds in the Deprecated Parameters and Obsolete Parameters sections. Make sure the COMPATIBLE initialization parameter is properly set for Oracle Database 11g Release 2 (11.2). The Pre-Upgrade Information Tool displays a warning in the Database section if COMPATIBLE is not properly set. 5. Adjust the values of the initialization parameters to at least the minimum values indicated by the Pre-Upgrade Information Tool. 6. Make sure all path names in the parameter file are fully specified. You should not have relative path names in the parameter file. 7. Make sure you save all of the files you modified after making these adjustments. Manually Upgrading the Database After preparing the new Oracle home, you are ready to proceed with the manual upgrade. To manually upgrade the database Shut down the instance: Sql> SHUTDOWN IMMEDIATE On Linux or UNIX operating system perform the following checks: Your ORACLE_SID is set correctly. The oratab file points to your Oracle Database 11g Release 2 (11.2) Oracle home
The following environment variables should point to the Oracle Database 11g Release 2 (11.2) directories:
ORACLE_HOME, PATH Any scripts that clients use to set the ORACLE_HOME value must point to the new Oracle home. Log in to the system as the owner of the Oracle Database 11g Release 2 (11.2) Oracle home directory. At a system prompt, change to the ORACLE_HOME/rdbms/admin directory. [oracle@ ~]$ cd $ ORACLE_HOME/rdbms/admin Start SQL*Plus. [oracle@ ~]$ export ORACLE_SID=[instance_name] [oracle@ ~]$ sqlplus sys as sysdba
SQL*Plus: Release 11.2.0.2.0 Production on Fri Apr 29 10:29:11 2011 Copyright (c) 1982, 2010, Oracle. All rights reserved. Enter password: Start the instance by issuing the following command: Sql> STARTUP UPGRADE ORACLE instance started. Total System Global Area 1000189952 bytes Fixed Size 1337492 bytes Variable Size 708839276 bytes Database Buffers 285212672 bytes Redo Buffers 4800512 bytes Database mounted. Database opened. Note: The UPGRADE keyword enables you to open a database based on an earlier Oracle Database release. It also restricts logons to AS SYSDBA sessions, disables system triggers, and performs additional operations that prepare the environment for the upgrade. You might be required to use the PFILE option to specify the location of your initialization parameter file. Once the database is started in upgrade mode, only queries on fixed views execute without errors until after the catupgrd.sql script is run. Before running catupgrd.sql, queries on any other view or the use of PL/SQL returns an error. Common Error & Solution for Database Upgrade: The following are common errors that might occur when attempting to start the new Oracle Database 11g Release 2 (11.2) database. Some of these errors are written to the alert log and not to your session. If you receive any of these errors, then issue the SHUTDOWN ABORT command to shut down the database and correct the problem. ORA-00401: the value for parameter compatible is not supported by this release Solution: The COMPATIBLE initialization parameter is set to a value less than 10.0.0. ORA-39701: database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE Solution: The CLUSTER_DATABASE initialization parameter is set to TRUE instead of FALSE.
ORA-39700: database must be opened with UPGRADE option Solution: The STARTUP command was issued without the UPGRADE keyword. ORA-00336: log file size xxxx blocks is less than minimum 8192 blocks Solution: A redo log file size is less than 4 MB: If errors appear listing obsolete initialization parameters, then make a note of the obsolete initialization parameters and continue with the upgrade. Remove the obsolete initialization parameters the next time you shut down the database. Sql> SPOOL upgrade.log
Run the Pre-Upgrade Information Tool by executing the utlu112i.sql script: Sql> @utlu112i.sql Run the catupgrd.sql script: Sql> @catupgrd.sql
Note: If you did not run the Pre-Upgrade Information Tool, the catupgrd.sql script terminates with one of the following errors: RA-00942: table or view does not exist ORA-00904: TZ_VERSION: invalid identifier ORA-01722: invalid number If you receive any of these errors, issue the SHUTDOWN ABORT statement, revert to the original Oracle home directory, and run the Pre-Upgrade Information Tool (utlu112i.sql) The catupgrd.sql script determines which upgrade scripts must be run, runs them, and then shuts down the database. You must run the script in the Oracle Database 11g Release 2 (11.2) environment. Restart the instance to reinitialize the system parameters for normal operation. Sql> STARTUP This restart, following the database shutdown performed as part of the catupgrd.sql script, flushes all caches, clears buffers, and performs other housekeeping activities. These measures are an important final step to ensure the integrity and consistency of the newly upgraded Oracle Database software. Note: If you encountered a message listing obsolete initialization parameters when
you started the database, then remove the obsolete initialization parameters from the parameter file before restarting. If necessary, convert the SPFILE to a PFILE so you can edit the file to delete parameters
Run utlu112s.sql, the Post-Upgrade Status Tool, which provides a summary of the upgrade at the end of the spool log. You must run utlu112s.sql only immediately after running catupgrd.sql. Run utlu112s.sql to display the results of the upgrade as follows: Sql> @utlu112s.sql
If the Post-Upgrade Status Tool returns errors or shows components that are not VALID or not the most recent release, then see Troubleshooting the Upgrade for more information. Run utlrp.sql to recompile any remaining stored PL/SQL and Java code. Sql> @utlrp.sql Verify that all expected packages and classes are valid: Sql> SELECT count(*) FROM dba_invalid_objects; Sql> SELECT distinct object_name FROM dba_invalid_objects; Note: If the pre-upgrade information tool detected INVALID objects and populated
the registry$sys_inv_objs and registry$nonsys_inv_objs tables, then execute ORACLE_HOME/rdbms/admin/utluiobj.sql to display only those objects which are newly invalid because of the upgrade process. The utluiobj.sql script only displays objects that are now INVALID but which were VALID before the upgrade. Exit SQL*Plus. Your database is now upgraded to the new Oracle Database 11g release. You are ready to complete the procedures described in Chapter 4, After Upgrading to the New Release. WARNING: If you retain the old Oracle software, then never start the upgraded database with the old software. Only start the database with the executables in the new Oracle Database installation. Also, before you remove the old Oracle environment, make sure you relocate any data files in that environment to the new Oracle Database environment. See the Oracle Database Administrators Guide for information about relocating data files. About the Post-Upgrade Status Tool The Post-Upgrade Status Tool, which is the utlu112s.sql script, displays the status of the database components in the upgraded database and the time required to complete each component upgrade. Any errors that occur during the upgrade are listed with each
component and must be addressed. The utlu112s.sql script must only be run immediately after catupgrd.sql The Post-Upgrade Status Tool displays a report similar to the following output: Oracle Database 11.2 Post-Upgrade Status Tool 10-18-2010 22:48:55 Component Status Version HH:MM:SS Oracle Server. VALID 11.2.0.2.0 00:17:31 JServer JAVA Virtual Machine. VALID 11.2.0.2.0 00:02:32 Oracle Application Express. VALID 3.2.1.00.12 00:23:25 Gathering Statistics. 00:05:12 Total Upgrade Time: 01:29:03 Note: Any time after utlrp.sql is run instead of using utl112s.sql to determine the STATUS of a component, run this query: SELECT COMP_NAME,VERSION,STATUS FROM DBA_REGISTRY; This will return the most up-to-date information. Troubleshooting the Upgrade: This section explains what to do if something goes wrong with your upgrade. This section contains the following topics: Resource Limits Edition Session Startup Error Manual Workaround for ORA-01408 Running the DBMS_DST Package After Upgrade Can Result in ORA-01822 DBUA May Mark Invalid Components with an X Before Entire Upgrade is Done Component Status Rerunning the Upgrade
Cancelling the Upgrade Resource Limits If you run out of resources during the upgrade, then increase the resource allocation. After increasing the resource allocation, you should perform a SHUTDOWN ABORT and restart the instance (in UPGRADE mode) before rerunning the catupgrd.sql script or restarting DBUA. The resources that generally require increases for a new Oracle Database release are as follows: SYSTEM and SYSAUX tablespaces Typically you receive one of the following messages during the upgrade if your SYSTEM tablespace size is insufficient: ORA-01650: unable to extend rollback segment string by string in tablespace string ORA-01651: unable to extend save undo segment by string for tablespace string
ORA-01652: unable to extend temp segment by string in tablespace string ORA-01653: unable to extend table string.string by string in tablespace string ORA-01654: unable to extend index string.string by string in tablespace string ORA-01655: unable to extend cluster string.string by string in tablespace string To avoid these errors, set AUTOEXTEND ON MAXSIZE UNLIMITED for the SYSTEM and SYSAUX tablespaces. ORA-04031: unable to allocate string bytes of shared memory (string,string,string,string) You might require larger shared memory pool sizes in some cases. The error message indicates which shared memory initialization parameter must be increased. If you are using an undo tablespace, then be sure it is at least 400 MB. Rerunning the Upgrade You can rerun the upgrade with the catupgrd.sql script as described in the following steps. To rerun the upgrade 1. 2. 3. 4. Shut down the database as follows: Sql> SHUTDOWN IMMEDIATE Restart the database in UPGRADE mode: Sql> STARTUP UPGRADE
5. Set the system to spool results to a log file for later verification of success: 6. Sql> SPOOL upgrade.log 7. Rerun catupgrd.sql: Sql> @catupgrd.sql Note: You can rerun the catupgrd.sql script as many times as necessary. The first time you run the script, there should be no error messages returned. If you rerun the script, then the ORA-00001 message is displayed. You can safely ignore this message. Cancelling the Upgrade If you completed the steps in Backing Up the Database to back up your database, then the easiest way to cancel the upgrade is to restore that backup as described in the following procedure. To cancel the upgrade by restoring the previous backup Restore Usingin RMAN: 1. Log in to the system as the owner of the Oracle home directory of the previous
release. 2. Sign on to RMAN: 3. 4. rman target / nocatalog Issue the following RMAN commands:
5. STARTUP NOMOUNT RUN { RESTORE CONTROLFILE FROM save_controlfile_location; ALTER DATABASE MOUNT; RESTORE DATABASE FROM TAG before_upgrade ALTER DATABASE OPEN RESETLOGS; } Restore Using Cold Backup: Copy database backup files to original location and database is restored.
How to Upgrade a 10.2 Database to an 11.2 Database

Oracle Database How To Guides How to Upgrade a 10.2 Database to an 11.2 Database Fold Table of Contents Background & Overview Assumptions & Pre-Requisites Useful Information Step-By-Step Guide Example Install Example Upgrade File Listings Oracle .profile oratab listener.ora initSID.ora File Systems Known Issues Error ORA-06550 During Upgrade. Description
Fix
Background & Overview

The following documentation provides instructions for upgrading an Oracle 10.2.0.4 database to an Oracle 11.2 database residing on Sun Solaris 10.
Assumptions & Pre-Requisites

This document expects and assumes the following: The instructions are carried out by a qualified DBA. Access to the internet is available. All necessary client software, e.g. Telnet and X-Server is available. The resultant database will be standalone, i.e. not part of a cluster or failover configuration. All references to SID should be replaced with correct database name as derived using a suitable database naming standard. There is only ONE database installed on the server.
Useful Information
This section outlines useful information and changes to previous 10g documentation found on this site. Some have been made for cosmetic reasons, others for more practical considerations. A new directory structure exists. See below. A new init.ora parameter called diag_dest has been set and maps to the diag directory in the new directory structure mentioned above. A listener.ora file has a new parameter called ADR_BASE_LISTENER. This maps to the base of the diag directory. There are a number of new maintenance jobs in 11g. These can be turned off as part of this step-by-step guide. Read the Known Issues section below.
Step-By-Step Guide
1. Ensure the new directory structure exists. See below. 2. Download the binaries for the Oracle 11g Database into/u01/app/oracle/SOFTWARE/DATABASE_11G
Enterprise Edition for Oracle Solaris Operating System (SPARC) (64bit)

solaris.sparc64_11gR2_database_1of2.zip := 1,373,903,591 bytes; cksum - 2779246655 solaris.sparc64_11gR2_database_2of2.zip := 1,048,619,225 bytes; cksum - 3179998886 3. Unzip the downloaded files using the following commands cd /u01/app/oracle/SOFTWARE/DATABASE_11G unzip solaris.sparc64_11gR2_database_1of2.zip unzip solaris.sparc64_11gR2_database_2of2.zip
4. Unset the
ORACLE_HOME and TNS_ADMIN
unset ORACLE_HOME unset TNS_ADMIN
5. Start
x-server.
6. Start the installer. cd /u01/app/oracle/SOFTWARE/DATABASE_11G/database export DISPLAY= Enter Your IP Address ./runInstaller
7. Follow the instructions as demonstrated in the Example Install section below.
Before continuing apply any oneoff patches, patch bundles or CPU patch bundles recommended by Oracle or the application vendor. At the time of writing this guide, the following PSU is available: 9654983
8. If PSU 11.2.0.1.2 has been applied then patch avoid ORA-06550druing the upgrade. 9. Ensure all Pre-Upgrade Requirements are Met. . oraenv
9315778 will need to be applied to
ORACLE_SID = [oracle] ? SID

sqlplus '/ as sysdba' SQL> @?/rdbms/admin/utlrp SQL> purge dba_recyclebin SQL> alter database datafile '/u03/oradata/SID/system/d1/system_01.dbf' resize 1000m;
10. Download the Latest Upgrade Check Script from Metalink article 884522.1 11. Perform an upgrade check on the exiting
10g database.
. oraenv

sqlplus '/ as sysdba' SQL> startup SQL> spool /tmp/upgrade_check.log SQL> @/u01/app/oracle/product/11.2.0/dbhome_1/rdbms/admin/utlu112i.sql
12. Review the output and resolve any issues. 13. Start the listener . oraenv

lsnrctl start
14. Start DBUA. cd /u01/app/oracle/product/11.2.0/dbhome_1/bin export DISPLAY= Enter Your IP Address dbua
15. Follow the instructions as demonstrated in the Example Upgrade section below. 16. Update the Oracle
.profile
Update the .profile using the listing below as a template. Log off and log back onto Oracle to pick up the new .profile
17. Create the admin directories cd /u01/app/oracle/admin/SID mkdir pfile mkdir audit
18. Reconfigure the new listener . oraenv

lsnrctl stop lsnrctl start
19. Create new . oraenv
spfile

sqlplus '/ as sysdba' create pfile='/u01/app/oracle/admin/SID/pfile/initSID.ora' from spfile shutdown immediate quit
cd /u01/app/oracle/admin/SID/pfile mv initSID.ora initSID.POST_UPGRADE Create a pfile using the listing below. cd $ORACLE_HOME/dbs rm spfileSID.ora rm initSID.ora ln -s /u01/app/oracle/admin/SID/pfile/initSID.ora sqlplus '/ as sysdba' startup create spfile='/u01/app/oracle/admin/SID/pfile/spfileSID.ora' from pfile; shutdown immediate quit cd $ORACLE_HOME/dbs rm initSID.ord ln -s /u01/app/oracle/admin/SID/pfile/spfileSID.ora cd /u01/app/oracle/admin/SID/pfile rm initSID.ora sqlplus '/ as sysdba' startup quit
20. Remove the old binaries rm -rf OLD_ORACLE_HOME
21. Check the database is registered with the listener lsnrctl status
22. Ensure DST update is not in progress . oraenv

sqlplus '/ as sysdba' SQL> select property_name, substr(property_value, 1, 30) value from database_properties where property_name like 'DST_%' order by property_name; o NB DST_SECONDARY_TT_VERSION should be set to 0 o NB DST_UPGRADE_STATE should be set to NONE
23. Prepare the DST Timezone Update . oraenv

sqlplus '/ as sysdba' SQL> exec DBMS_DST.BEGIN_PREPARE(&version); o NB For 11.2.0.1, the latest version is 11. For 11.2.0.2 the latest version is 14.
24. Ensure the prepare has completed successfully.
. oraenv

sqlplus '/ as sysdba' SQL> select property_name, substr(property_value, 1, 30) value from database_properties where property_name like 'DST_%' order by property_name; o NB DST_SECONDARY_TT_VERSION should be set to the version being upgraded to. E.g. 11 o NB DST_UPGRADE_STATE should be set to prepare
25. Clear out the DST upgrade logging tables prior to checkinng for affected data . oraenv

sqlplus '/ as sysdba' SQL> truncate table sys.dst$trigger_table; SQL> truncate table sys.dst$affected_tables; SQL> truncate table sys.dst$error_table;
26. Check for data that may be affected by the DST update . oraenv

sqlplus '/ as sysdba' SQL> BEGIN DBMS_DST.FIND_AFFECTED_TABLES (affected_tables => 'sys.dst$affected_tables', log_errors => TRUE, log_errors_table => 'sys.dst$error_table'); END; / SQL> select * from sys.dst$affected_tables; o NB This will show a list of tables affected by the DST update. Hopefully none. SQL> SELECT * FROM sys.dst$error_table; o NB This will show type errors that occured in the rows reported in dst$affected_tables.
27. End the prepare state in preparation for the upgrade. . oraenv

sqlplus '/ as sysdba' SQL> EXEC DBMS_DST.END_PREPARE; SQL> select property_name, substr(property_value, 1, 30) value from database_properties where property_name like 'DST_%' order by property_name; o NB DST_SECONDARY_TT_VERSION should be set to 0 o NB DST_UPGRADE_STATE should be set to NONE
28. Upgrade the DST timezone. . oraenv

sqlplus '/ as sysdba' SQL> shutdown immediate
SQL> SQL> SQL> SQL> SQL> SQL> SQL>
startup upgrade purge dba_recyclebin truncate table sys.dst$trigger_table; truncate table sys.dst$affected_tables; truncate table sys.dst$error_table; EXEC DBMS_DST.BEGIN_UPGRADE(11); select property_name, substr(property_value, 1, 30) value from database_properties where property_name like 'DST_%' order by property_name; SQL> shutdown immediate; SQL> startup SQL> set serveroutput on SQL> VAR numfail number SQL> BEGIN DBMS_DST.UPGRADE_DATABASE(:numfail,parallel => TRUE,log_errors => TRUE,log_errors_table => 'SYS.DST$ERROR_TABLE',log_triggers_table => 'SYS.DST$TRIGGER_TABLE',error_on_overlap_time => FALSE,error_on_nonexisting_time => FALSE); DBMS_OUTPUT.PUT_LINE('Failures:'|| :numfail); END; / SQL> VAR fail number SQL> BEGIN DBMS_DST.END_UPGRADE(:fail); DBMS_OUTPUT.PUT_LINE('Failures:'|| :fail); END; / SQL> select * from v$timezone_file; o NB This should report the new timezone file version. E.g. 11
29. Check for Depricated, non-default parameters.

sqlplus '/ as sysdba' SQL> SELECT name FROM v$parameter WHERE isdeprecated = 'TRUE' and isdefault='FALSE' o NB This should return 0 rows. If not, migrate to a more suitable init.ora.
30. Disable the default
11g maintenance jobs if required.
sqlplus /nolog SQL> connect sys as sysdba SQL> BEGIN SQL> dbms_auto_task_admin.disable(client_name => 'auto optimizer stats collection', operation => NULL,window_name => NULL); SQL> dbms_auto_task_admin.disable(client_name => 'auto space advisor', operation => NULL, window_name => NULL); SQL> dbms_auto_task_admin.disable(client_name => 'sql tuning advisor', operation => NULL, window_name => NULL); SQL> END; SQL> /
31. Run Gather Stats against 'SYS. sqlplus /nolog
SQL> connect sys as sysdba 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);
Example Install
Un-tick the I wish to receive security updates via My Oracle Support box. Click Next.
Click Yes to remain uninformed.
Select Install database software only. Click Next.
Ensure Single instance database installation is selected. Click Next.
Ensure languages Englsih and English (United Kingdom) are selected. Click Next.
Ensure Enterprise Edition is selected. Click Next.
Set Oracle Base to /u01/app/oracle Allow Software Location to default Click Next.
Ensure Database Administrator (OSDBA) Group is set to dba Ensure Database Operator (OSOPER) Group is set to dba Click Next
This page may not be displayed. Review and fix any issues. Click Next
Note: The installer may report a failed check on OS Patch 124861-15. Its possible that this
failed check can be ignored. Review Metalink document 969497.1
Review the summary. If required save the response file by selecting Save Response File Click Finish
This screen moves on automatically when complete.
Ask Unix Administrator to run root.sh.
Click OK.
Click Close.
Example Upgrade
Click Next.
Select the database you wish to upgrade. Click Next.
Review the warnings and fix if applicable. Click Yes.
Ensure Recompile invalid objects at the end of upgrade is ticked. Turn off archiving if required. Mostly this will not be necessary. Ensure Backup database is NOT ticked. o NB You should backup the database prior to this step using the normal backup method. Click Next.
If you left archiving on, Click Yes to continue.
Ensure Do Not Move Database Files as Part of Upgrade is selected. Click Next.
Ensure Specify Flash Recovery Area is Un-Ticked. Ensure the Diagnostics Destination is set to /u01/app/oracle Click Next.
Review the Database Upgrade Summary. Click Finish.
Monitor the upgrade progress. NOTE This screen will move on automatically.
Click Ignore. NOTE - Review the Known Issues section below regarding this error message.
Review the Upgrade Results Click Close.
File Listings Oracle .profile

#----------------------------------------------------------------------# Configure Terminal Settings. #------------------------------------------------------------------stty susp ^Z
-----
stty quit ^C stty erase ^? export TERM=vt100-w export ORACLE_TERM=vt100 #------------------------------------------------------------------# Configure Shell Settings. #------------------------------------------------------------------set -o vi export PATH=/bin:/usr/sbin:/usr/bin:/usr/local/bin:$PATH export EDITOR=vi export HOSTNAME=`hostname` export PS1='$LOGNAME@$HOSTNAME:$ORACLE_SID> ' export TMPDIR=/tmp export TEMP=/tmp umask 022 #------------------------------------------------------------------# Configure Aliases. #------------------------------------------------------------------alias ll="ls -la" alias bdf="df -k" #------------------------------------------------------------------# Configure Oracle Settings. #-------------------------------------------------------------------
-----
-----
export export export export export export export
ORACLE_BASE=/u01/app/oracle SQLPATH=$ORACLE_BASE/scripts/dba/sql ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_1 TNS_ADMIN=$ORACLE_HOME/network/admin ORACLE_HOME_LISTNER=$ORACLE_BASE/product/11.2.0/dbhome_1 PATH=$ORACLE_HOME/bin:$PATH ORATAB=/var/opt/oracle/oratab
oratab
SID:/u01/app/oracle/product/11.2.0/dbhome_1:Y
listener.ora
SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = <SID>) (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1) (SID_NAME = <SID>) ) ) LISTENER = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>)(PORT = 1521)) ) ADR_BASE_LISTENER = /u01/app/oracle
initSID.ora
########################################### # Cache and I/O ########################################### db_block_size=8192 memory_target=1606418432 db_block_checking=MEDIUM db_block_checksum='FULL' ########################################### # Cursors and Library Cache ########################################### open_cursors=500 ########################################### # Database Identification ########################################### compatible='11.2.0.0.0' db_name='SID' ########################################### # Diagnostics and Statistics ########################################### diagnostic_dest='/u01/app/oracle' ########################################### # File Configuration ########################################### control_files='+DATA/SID/control01.ctl','+DATA/SID/control02.ctl', '+DATA/SID/control03.ctl' ########################################### # Processes ########################################### processes=1000 ########################################### # System Managed Undo and Rollback Segments ########################################### undo_tablespace='UNDO' ########################################### # Security and Auditing ########################################### audit_trail='db' remote_login_passwordfile='EXCLUSIVE' ########################################### # Enabling Archivelog mode ########################################### log_archive_dest='+FRA/SID/arch/d1' log_archive_format=arch_%t_%s_%r.log ########################################### # Defer Segment Creation ###########################################
deferred_segment_creation=FALSE
File Systems
/--- /var --- /opt | --- /u01 --- /app | | | | | | | | ---/dbhome_1 | | | | | | | /u09) | | | | | | /scripts ---/base ---/rfc | | --- /u02 --- /oradata | | | --- /u03 --- /oradata | | | | | | | | | --- /u04 --- /oradata | --- /u05 --- /oradata | --- /u06 --- /oradata | --- /u07 --- /oradata | --- /u08 --- /oradata | --- /oracle --- /oracle --- /software | --- /dba --- /scripts | --- /sql | --- /diag | --- /product --- /11.2.0 | --- /admin --- /SID --- /adump | --- /create | --- /exp | (link to | --- /parfile | --- /pfile | ---
--- /SID --- /redo --- /d1 | --- /redo --- /d2 --- /SID --- /indx --| --| --| --| --/d1 /sysaux /system --- /d1 --- /d1
/tools --- /d1 /users --- /d1
--- /SID --- /undo --- /d1 --- /SID --- /temp --- /d1 --- /SID --- /arch --- /d1 --- /SID --- /data --- /d1 --- /SID --- /index --- /d1
--- /u09 --- /oradata --- /SID --- /exp --- /d1 | --- /u10 --- /oradata --- /SID --- /flash --- /d1
Known Issues
Error ORA-06550 During Upgrade.
Description
Whilst running the upgrade you may encouner an article 1066828.1.
ORA-06550 as detailled in Metalink
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.
RDBMS Upgrade : 10.2.0.4 to 11.2.0.2

nitiserver[oracle]_test> mkdir -p /nitiserver/dba01/oracle/test/upgrade11gR2 nitiserver[oracle]_test> cp /nitiserver/testdb/oracle/product/11.2.0.2/rdbms/admin/utlu112i.sql $ORACLE_HOME/test/upgrade11gR2 nitiserver[oracle]_test> cd $ORACLE_HOME/test/upgrade11gR2 nitiserver[oracle]_test> pwd /nitiserver/dba01/oracle/test/upgrade11gR2 nitiserver[oracle]_test> ls -ltr total 204 -rw-r--r-- 1 oracle dba 204205 Apr 15 03:43 utlu112i.sql nitiserver[oracle]_test> sqlplus "/ as sysdba" SQL*Plus: Release 10.2.0.4.0 - Production on Fri Apr 15 03:43:48 2012 Copyright (c) 1982, 2007, Oracle. All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production With the Partitioning, OLAP, Data Mining Scoring Engine and Real Application Testing options SQL> spool upgrade_info.log SQL> @utlu112i.sql Oracle Database 11.2 Pre-Upgrade Information Tool 04-15-2012 03:44:22 Script Version: 11.2.0.2.0 Build: 001 . **********************************************************************
Database: ********************************************************************** --> name: test --> version: 10.2.0.4.0 --> compatible: 10.2.0.2.0 --> blocksize: 8192 --> platform: Linux IA (32-bit) --> timezone file: V4 . ********************************************************************** Tablespaces: [make adjustments in the current environment] ********************************************************************** --> SYSTEM tablespace is adequate for the upgrade. .... minimum required size: 389 MB --> UNDOTBS1 tablespace is adequate for the upgrade. .... minimum required size: 211 MB --> TEMP tablespace is adequate for the upgrade. .... minimum required size: 61 MB --> SYSAUX tablespace is adequate for the upgrade. .... minimum required size: 318 MB . ********************************************************************** Flashback: OFF ********************************************************************** ********************************************************************** Update Parameters: [Update Oracle Database 11.2 init.ora or spfile] Note: Pre-upgrade tool was run on a lower version 32-bit database. ********************************************************************** --> If Target Oracle is 32-Bit, refer here for Update Parameters: WARNING: --> "shared_pool_size" needs to be increased to at least 236 MB . --> If Target Oracle is 64-Bit, refer here for Update Parameters: WARNING: --> "shared_pool_size" needs to be increased to at least 472 MB . ********************************************************************** Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile] ********************************************************************** -- No renamed parameters found. No changes are required. . ********************************************************************** Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile] ********************************************************************** --> background_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest" --> user_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest" . ********************************************************************** Components: [The following database components will be upgraded or installed] ********************************************************************** --> Oracle Catalog Views [upgrade] VALID
--> Oracle Packages and Types [upgrade] VALID --> OLAP Analytic Workspace [upgrade] VALID --> Oracle OLAP API [upgrade] VALID . ********************************************************************** Miscellaneous Warnings ********************************************************************** WARNING: --> Database is using a timezone file older than version 14. .... After the release migration, it is recommended that DBMS_DST package .... be used to upgrade the 10.2.0.4.0 database timezone version .... to the latest version which comes with the new release. WARNING: --> Database contains INVALID objects prior to upgrade. .... The list of invalid SYS/SYSTEM objects was written to .... registry$sys_inv_objs. .... The list of non-SYS/SYSTEM objects was written to .... registry$nonsys_inv_objs. .... Use utluiobj.sql after the upgrade to identify any new invalid .... objects due to the upgrade. .... USER testBA has 2 INVALID objects. .... USER SYSTEM has 11 INVALID objects. .... USER testBAPRD has 27 INVALID objects. .... USER SYS has 2 INVALID objects. . ********************************************************************** Recommendations ********************************************************************** Oracle recommends gathering dictionary statistics prior to upgrading the database. To gather dictionary statistics execute the following command while connected as SYSDBA: EXECUTE dbms_stats.gather_dictionary_stats; ********************************************************************** Oracle recommends reviewing any defined events prior to upgrading. To view existing non-default events execute the following commands while connected AS SYSDBA: Events: SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2 WHERE UPPER(name) ='EVENT' AND isdefault='FALSE' Trace Events: SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2 WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE' Changes will need to be made in the init.ora or spfile. **********************************************************************
SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS; SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
SQL> SHUTDOWN IMMEDIATE
############################################################################# cd /nitiserver/oracle/bin cp test_11202 test nitiserver[oracle]_test> vi /etc/oratab # This file is used by ORACLE utilities. It is created by root.sh # and updated by the Database Configuration Assistant when creating # a database. # A colon, ':', is used as the field terminator. A new line terminates # the entry. Lines beginning with a pound sign, '#', are comments. # # Entries are of the form: # $ORACLE_SID:$ORACLE_HOME:<N|Y>: # # The first and second fields are the system identifier and home # directory of the database respectively. The third filed indicates # to the dbstart utility that the database should , "Y", or should not, # "N", be brought up at system boot time. # # Multiple entries with the same $ORACLE_SID are not allowed. # #test:/nitiserver/testdb/oracle/product/test_10.2.0.4:N test:/nitiserver/testdb/oracle/product/11.2.0.2:N #################################################################################### ## nitiserver[oracle]_test> cat /etc/oraInst.loc #inventory_loc=/nitiserver/testdb/oracle/product/test_10.2.0.4/oraInventory inventory_loc=/nitiserver/testdb/oracle/product/11.2.0.2/oraInventory inst_group=dba #################################################################################### ######## Change the init paramete diagnostic_dest=/nitiserver/dump01/oracle/test/bdump diagnostic_dest=/nitiserver/dump01/oracle/test/udump core_dump_dest=/nitiserver/dump01/oracle/test/cdump compatible=11.2.0.2.0 shared_pool_size=263402291 #################################################################################### ########## nitiserver[oracle]_test> ln -s $SID_HOME/pfile/init$ORACLE_SID.ora
$ORACLE_HOME/dbs/init$ORACLE_SID.ora nitiserver[oracle]_test> ls -ltr $ORACLE_HOME/dbs/ total 4 -rw-r--r-- 1 oracle dba 2851 May 15 2009 init.ora lrwxrwxrwx 1 oracle dba 50 Apr 15 04:37 inittest.ora -> /nitiserver/dba01/oracle/test/pfile/inittest.ora nitiserver[oracle]_test> cd $SID_HOME/upgrade11gR2 nitiserver[oracle]_test> pwd /nitiserver/dba01/oracle/test/upgrade11gR2 SQL> STARTUP UPGRADE; ORA-00371: not enough shared pool memory, should be atleast 263402291 bytes #################################################################################### ############# [oracle@nitiserver ~]$ sqlplus SQL*Plus: Release 11.2.0.2.0 Production on Fri Apr 15 06:36:42 2012 Copyright (c) 1982, 2010, Oracle. All rights reserved. Enter user-name: / as sysdba Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> !echo $ORACLE_SID test SQL> STARTUP UPGRADE; ORACLE instance started. Total System Global Area 481275904 bytes Fixed Size 1344952 bytes Variable Size 339741256 bytes Database Buffers 134217728 bytes Redo Buffers 5971968 bytes Database mounted. Database opened. SQL> SET SERVEROUTPUT ON SQL> purge dba_recyclebin; DBA Recyclebin purged. SQL> TRUNCATE TABLE SYS.DST$TRIGGER_TABLE; Table truncated. SQL> TRUNCATE TABLE SYS.DST$AFFECTED_TABLES; Table truncated. SQL> TRUNCATE TABLE SYS.DST$ERROR_TABLE; Table truncated. SQL> EXEC DBMS_DST.BEGIN_UPGRADE(11); An upgrade window has been successfully started.
PL/SQL procedure successfully completed. SQL> column PROPERTY_NAME format a30 column VALUE format a30 SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value FROM DATABASE_PROPERTIES WHERE PROPERTY_NAME LIKE 'DST_%' ORDER BY PROPERTY_NAME; SQL> SQL> 2 3 4 PROPERTY_NAME VALUE ------------------------------ -----------------------------DST_PRIMARY_TT_VERSION 11 DST_SECONDARY_TT_VERSION 4 DST_UPGRADE_STATE UPGRADE SQL> EXEC DBMS_DST.BEGIN_UPGRADE(14); BEGIN DBMS_DST.BEGIN_UPGRADE(14); END; * ERROR at line 1: ORA-56920: a prepare or upgrade window or an on-demand or datapump-job loading of a secondary time zone data file is in an active state ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79 ORA-06512: at "SYS.DBMS_DST", line 1158 ORA-06512: at line 1 SQL> SELECT OWNER, TABLE_NAME, UPGRADE_IN_PROGRESS FROM ALL_TSTZ_TABLES WHERE UPGRADE_IN_PROGRESS='YES'; 2 3 no rows selected SQL> SHUTDOWN IMMEDIATE Database closed. Database dismounted. ORACLE instance shut down. SQL> STARTUP ORACLE instance started. Total System Global Area 481275904 bytes Fixed Size 1344952 bytes Variable Size 339741256 bytes Database Buffers 134217728 bytes Redo Buffers 5971968 bytes Database mounted. Database opened. SQL> set serveroutput on VAR numfail number BEGIN SQL> SQL> 2 DBMS_DST.UPGRADE_DATABASE(:numfail, 3 parallel => TRUE, 4 log_errors => TRUE, 5 log_errors_table => 'SYS.DST$ERROR_TABLE', 6 log_triggers_table => 'SYS.DST$TRIGGER_TABLE',
7 error_on_overlap_time => FALSE, 8 error_on_nonexisting_time => FALSE); 9 DBMS_OUTPUT.PUT_LINE('Failures:'|| :numfail); 10 END; 11 / Failures:0 PL/SQL procedure successfully completed. SQL> VAR fail number BEGIN DBMS_DST.END_UPGRADE(:fail); DBMS_OUTPUT.PUT_LINE('Failures:'|| :fail); END; SQL> 2 3 4 5 6 ; 7 8 / ; * ERROR at line 6: ORA-06550: line 6, column 1: PLS-00103: Encountered the symbol ";" SQL> VAR fail number BEGIN DBMS_DST.END_UPGRADE(:fail); DBMS_OUTPUT.PUT_LINE('Failures:'|| :fail); END; SQL> 2 3 4 5 / An upgrade window has been successfully ended. Failures:0 PL/SQL procedure successfully completed. SQL> SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value FROM DATABASE_PROPERTIES WHERE PROPERTY_NAME LIKE 'DST_%' ORDER BY PROPERTY_NAME; SELECT * FROM v$timezone_file; 2 3 4 PROPERTY_NAME VALUE ------------------------------ -----------------------------DST_PRIMARY_TT_VERSION 11 DST_SECONDARY_TT_VERSION 0 DST_UPGRADE_STATE NONE SQL> SQL> FILENAME VERSION -------------------- ---------timezlrg_11.dat 11 SQL> EXEC DBMS_DST.BEGIN_UPGRADE(14); BEGIN DBMS_DST.BEGIN_UPGRADE(14); END; *
ERROR at line 1: ORA-56926: database must be in UPGRADE mode in order to start an upgrade window ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79 ORA-06512: at "SYS.DBMS_DST", line 1195 ORA-06512: at line 1 SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> SQL> startup ORACLE instance started. Total System Global Area 481275904 bytes Fixed Size 1344952 bytes Variable Size 339741256 bytes Database Buffers 134217728 bytes Redo Buffers 5971968 bytes Database mounted. Database opened. SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> SQL> startup ORACLE instance started. Total System Global Area 481275904 bytes Fixed Size 1344952 bytes Variable Size 339741256 bytes Database Buffers 134217728 bytes Redo Buffers 5971968 bytes Database mounted. Database opened. SQL> SELECT comp_name, version, status FROM dba_registry; COMP_NAME -------------------------------------------------------------------------------VERSION STATUS ------------------------------ ----------Oracle Database Catalog Views 11.2.0.2.0 VALID Oracle Database Packages and Types 11.2.0.2.0 VALID OLAP Analytic Workspace 11.2.0.2.0 VALID COMP_NAME -------------------------------------------------------------------------------VERSION STATUS ------------------------------ ----------Oracle OLAP API
11.2.0.2.0
VALID
SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> STARTUP UPGRADE; ORACLE instance started. Total System Global Area 481275904 bytes Fixed Size 1344952 bytes Variable Size 339741256 bytes Database Buffers 134217728 bytes Redo Buffers 5971968 bytes Database mounted. Database opened. SQL> purge dba_recyclebin; DBA Recyclebin purged. SQL> TRUNCATE TABLE SYS.DST$TRIGGER_TABLE; Table truncated. SQL> TRUNCATE TABLE SYS.DST$AFFECTED_TABLES; Table truncated. SQL> TRUNCATE TABLE SYS.DST$ERROR_TABLE; Table truncated. SQL> EXEC DBMS_DST.BEGIN_UPGRADE(14); PL/SQL procedure successfully completed. SQL> column PROPERTY_NAME format a30 column VALUE format a30 SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value FROM DATABASE_PROPERTIES WHERE PROPERTY_NAME LIKE 'DST_%' ORDER BY PROPERTY_NAME; SQL> SQL> 2 3 4 PROPERTY_NAME VALUE ------------------------------ -----------------------------DST_PRIMARY_TT_VERSION 14 DST_SECONDARY_TT_VERSION 11 DST_UPGRADE_STATE UPGRADE SQL> SQL> SELECT OWNER, TABLE_NAME, UPGRADE_IN_PROGRESS FROM ALL_TSTZ_TABLES WHERE UPGRADE_IN_PROGRESS='YES'; 2 3 no rows selected SQL> SHUTDOWN IMMEDIATE startup Database closed. Database dismounted. ORACLE instance shut down. SQL> ORACLE instance started.
Total System Global Area 481275904 bytes Fixed Size 1344952 bytes Variable Size 339741256 bytes Database Buffers 134217728 bytes Redo Buffers 5971968 bytes Database mounted. Database opened. SQL> set serveroutput on VAR numfail number BEGIN SQL> SQL> 2 DBMS_DST.UPGRADE_DATABASE(:numfail, 3 parallel => TRUE, 4 log_errors => TRUE, 5 log_errors_table => 'SYS.DST$ERROR_TABLE', 6 log_triggers_table => 'SYS.DST$TRIGGER_TABLE', 7 error_on_overlap_time => FALSE, 8 error_on_nonexisting_time => FALSE); 9 DBMS_OUTPUT.PUT_LINE('Failures:'|| :numfail); 10 END; 11 / Failures:0 PL/SQL procedure successfully completed. SQL> VAR fail number BEGIN DBMS_DST.END_UPGRADE(:fail); DBMS_OUTPUT.PUT_LINE('Failures:'|| :fail); END; / SQL> 2 3 4 5 An upgrade window has been successfully ended. Failures:0 PL/SQL procedure successfully completed. SQL> SELECT PROPERTY_NAME, SUBSTR(property_value, 1, 30) value FROM DATABASE_PROPERTIES WHERE PROPERTY_NAME LIKE 'DST_%' ORDER BY PROPERTY_NAME; 2 3 4 PROPERTY_NAME VALUE ------------------------------ -----------------------------DST_PRIMARY_TT_VERSION 14 DST_SECONDARY_TT_VERSION 0 DST_UPGRADE_STATE NONE SQL> SQL> SELECT * FROM v$timezone_file; FILENAME VERSION -------------------- ---------timezlrg_14.dat 14 #################################################################################### #############
COMP_NAME VERSION STATUS --------------------------------------------- ------------------------------ ----------Oracle Database Catalog Views 11.2.0.2.0 VALID Oracle Database Packages and Types 11.2.0.2.0 VALID OLAP Analytic Workspace 11.2.0.2.0 VALID Oracle OLAP API 11.2.0.2.0 VALID #################################################################################### ############### LSNRCTL> start LSTNtest Starting /nitiserver/testdb/oracle/product/11.2.0.2/bin/tnslsnr: please wait... TNSLSNR for Linux: Version 11.2.0.2.0 - Production System parameter file is /nitiserver/testdb/oracle/product/11.2.0.2/network/admin/test_nitiserver/listener.ora Log messages written to /nitiserver/testdb/oracle/product/11.2.0.2/log/diag/tnslsnr/nitiserver/lstntest/alert/log.xml Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=nitiserver)(PORT=1599))) Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=nitiserver)(PORT=1599))) STATUS of the LISTENER -----------------------Alias LSTNtest Version TNSLSNR for Linux: Version 11.2.0.2.0 - Production Start Date 15-APR-2012 05:37:37 Uptime 0 days 0 hr. 0 min. 0 sec Trace Level off Security ON: Local OS Authentication SNMP ON Listener Parameter File /nitiserver/testdb/oracle/product/11.2.0.2/network/admin/test_nitiserver/listener.ora Listener Log File /nitiserver/testdb/oracle/product/11.2.0.2/log/diag/tnslsnr/nitiserver/lstntest/alert/log.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=nitiserver)(PORT=1599))) Services Summary... Service "test." has 1 instance(s). Instance "test", status UNKNOWN, has 1 handler(s) for this service... The command completed successfully #################################################################################### #################### [oracle@nitiserver test_nitiserver]$ tnsping test TNS Ping Utility for Linux: Version 11.2.0.2.0 - Production on 15-APR-2012 05:38:30 Copyright (c) 1997, 2010, Oracle. All rights reserved. Used parameter files: Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = ( ADDRESS = (PROTOCOL = TCP) ( HOST = nitiserver)(PORT
= 1599)) ( CONNECT_DATA = ( SID = test))) OK (0 msec)
10.2.0.4 to 11.2.0.2 Standalone DB upgrade using dbua

Followed Complete checklist to upgrade the database to 11g R2 using DBUA [ID 870814.1]
1. Check dba_registry for correctness of status and version at the source 10.2.0.4 database. Take necessary steps to validate them. 2. Copy from 11g Env: $ORACLE_HOME/rdbms/admin/utlu112i.sql to some other location e.g. /tmp 3. From 10g Env: cd /tmp $ sqlplus '/ as sysdba' SQL> spool upgrade_prereq.log SQL> @utlu112i.sql SQL> spool off 4. Review the upgrade_prereq.log and fix them. I will put some lines from my log file where it suggested some changes: .. .. Update Parameters: [Update Oracle Database 11.2 init.ora or spfile] Note: Pre-upgrade tool was run on a lower version 64-bit database. ****************************************************************** **** WARNING: --> "shared_pool_size" needs to be increased to at least 472 MB WARNING: --> "db_cache_size" needs to be increased to at least 50331648 bytes ==> dbua would take care of this. ****************************************************************** **** Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]
****************************************************************** **** --> background_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest" --> user_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest" ==> dbua would take care of this ****************************************************************** **** Miscellaneous Warnings ****************************************************************** **** WARNING: --> Database is using a timezone file older than version 14. .... After the release migration, it is recommended that DBMS_DST package .... be used to upgrade the 10.2.0.4.0 database timezone version .... to the latest version which comes with the new release. ==> Checked "Actions FOR DST Updates When Upgrading To Or Applying The 11.2.0.2 Patchset (Doc ID 1201253.1)" . Check step B.3b). It says we can skip the DST related upgrade instructions. dbua gives an option of upgrading the timezone version and TIMESTAMP WITH TIME ZONE data. WARNING: --> Database contains INVALID objects prior to upgrade. .... The list of invalid SYS/SYSTEM objects was written to .... registry$sys_inv_objs. .... The list of non-SYS/SYSTEM objects was written to .... registry$nonsys_inv_objs. .... Use utluiobj.sql after the upgrade to identify any new invalid .... objects due to the upgrade. WARNING: --> EM Database Control Repository exists in the database. .... Direct downgrade of EM Database Control is not supported. Refer to the .... Upgrade Guide for instructions to save the EM data prior to upgrade.
WARNING: --> Your recycle bin contains 93 object(s). .... It is REQUIRED that the recycle bin is empty prior to upgrading .... your database. The command: PURGE DBA_RECYCLEBIN .... must be executed immediately prior to executing your upgrade. WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package. .... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs. ==> This actually needs be done post upgrade. http://download.oracle.com/docs/cd/E11882_01/server.112/e17222/upgrade.htm# BABJHIHH 5. Gather dictionary stats prior to upgrade: On 10g ENV: sqlplus "/as sysdba" EXECUTE dbms_stats.gather_dictionary_stats; 6. purge dba_recyclebin 7. Run dbua ==> I saw few errors during oracle server upgrade but I could ignore those. May be because my 10g db had many invalid objects. As most of them were ORA04063. ==>Also EM configuration failed. Will write another post for this one. 8. Change compatible. I havent done this yet, as I would leave it to 10.2.0.4 for few days so that in case I want to downgrade it.
As described in Oracle Database Upgrade Guide 11g Release 1 (11.1), there are three upgrade methods offered while you want to upgrade database from 10g to 11g.
1. Database Upgrade Assistant (DBUA) 2. Manual Upgrade (Oracle provided scripts) 3. Export/Import (exp/imp, or expdp/impdp)
Besides benefits mentioned in above upgrade document, Im thinking we are beneficial from using export/import approach. The reasons we decided using this method are:
we want to set up identical testing databases on development server first we want to keep original production databases unchanged anyway for safety reason
With this approach, we first installed Oracle 11g software on development server and created empty database by using provided standard template New_Database.dbt, which could be found at $ORACLE_HOME/assistants/dbca/templates. After that, we followed the following steps to move data from 10g database to newly created 11g database. Step 1: Pre-create tablespaces on target 11g database

using the Generate_Create_Tablespaces.sql to generate tablespace script editing generated script to remove entries for SYSTEM, USERS tablespaces
Step 2: Export full database of source 10g database expdp system@database directory=DATA_PUMP_DIR full=y dumpfile=export.dmp logfile=export.log Step 3: Copy dumpfile over network to development server Step 4: Grant IMPORT_FULL_DATABASE system privilege to user SYSTEM of target 11g database Step 5: Import full database to target 11g database Note: If you have co-existing oracle home/version on development server, please make sure switching to Oracle 11g environment, which will assure to use data pump at 11g version to import data. Impdp system@database directory=DATA_PUMP_DIR full=y dumpfile=export.dmp logfile=import.log
Step by Step Upgrading Oracle 10g to Oracle 11g

Posted by Debashis Paul * A Passionate Blogger * under Oracle in Windows, Oracle11g | Tags: 10g R1 to 11g upgrade, 11g EMCA configuration, 11g enterprise manager emca, creating oracle 11g TNS, Database Upgrade Assistant, oracle 11.1.0.6.0 installation upgrade, oracle 11g install, Oracle 11g Net Asistant, oracle 11g tns create, oracle enterprise manager console 11g, SOA suite version oracle, upgrade oracle 10g to 11g | 1 Comment
6 Votes
Hell ! Yes , my Oracle 10g in Windows XP SP2 is the older one i.e 10.1.0.2 which doesnt Support the SOA Suite installation . Oracle suggest to upgrade this to 10R2 (10.2.0.4 or higher ) . But bit lethargic about this upgrade as I do have to again download the Patch from Metalink i.e of size ~972 MB . Since I have had Oracle 11g installer so best possible option is to throw my Oracle 10g DB and install 11g afresh . But again the pain is to export all Db objects and again import into new DB .What if the new DB failed to import in 11g ? What if there is Unicode/Non-Unicode character set incompatibility occurs ? I know patchset available but I cant rely on my knowledge about applying those pathset successfully ! After lots of brainstorming the final thought come is that there might be some way to upgrade the DB from already installed 10g to 11g using the available installer rather using the upgrade patchset for 11g. So finally kickoff 11g installation after executing the setup file and follow the onscreen instruction step by step . Here you goes
So I have installed 11g softwares without having any Database . My aim is to upgrade the existing 10g instance as 11g . 1) Copy file : utlu111i.sql to d:\temp (any temporary location) from D:\Oradb11g\RDBMS\ADMIN .
2) Connected into Oracle 10g instance while DB is up and running and execute the .sql file from SQL prompt and get the below stat .
3) To resolve the below warning : 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. Execute : SQL> select * from v$timezone_file; SQL> SELECT CASE COUNT(DISTINCT(tzname)) WHEN 183 then 1 WHEN 355 then 1
WHEN 347 then 1 WHEN 377 then 2 WHEN 186 then case COUNT(tzname) WHEN 636 then 2 WHEN 626 then 3 ELSE 0 end WHEN 185 then 3 WHEN 386 then 3 WHEN 387 then case COUNT(tzname) WHEN 1438 then 3 ELSE 0 end WHEN 391 then case COUNT(tzname) WHEN 1457 then 4 ELSE 0 end WHEN 392 then case COUNT(tzname) WHEN 1458 then 4 ELSE 0 end WHEN 188 then case COUNT(tzname) WHEN 637 then 4 ELSE 0 end WHEN 189 then case COUNT(tzname) WHEN 638 then 4 ELSE 0 end ELSE 0 end VERSION FROM v$timezone_names;
If the output of this is < 4 then prior to upgrade we need to apply the Timezone patch .So I need to apply it prior to go ahead . For my Windows 32 bit the patch(5731187) could be found at Metalink. Download the file : p5731187_10105_WINNT.zip and un-archive to location as : D:\temp\5731187 . 4) Copy the files from location : D:\temp\5731187\files\oracore\zoneinfo and paste it to existing Oracle 10g location D:\oracle\oracore\zoneinfo . Make sure to keep backup of existing folder so that you could revert if any problem occurs . 5) Stop the DB instance and Start . After that execute Step 2&3 again and the warning should be removed and timzone file version should be upgraded. Otherwise assist Oracle Support . 6) To remove below warning execute the below command from sysdba users . WARNING: > Database contains stale optimizer statistics. . Refer to the 11g Upgrade Guide for instructions to update . statistics prior to upgrading the database.
. Component Schemas with stale statistics: . SYS . SYSMAN 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); PL/SQL procedure successfully completed. SQL> EXEC DBMS_STATS.GATHER_SCHEMA_STATS(SYSMAN); PL/SQL procedure successfully completed. 7) I skip the other warnings .To avoid showing other warnings use Oracle Documentation about Pre-Upgrade Information Final) Now lets perform the Database upgrade steps using : Database Upgrade Assistant(DBUA) a GUI to upgrade the DB and it can be found under Start -) All Programs -) Oracle 11g Home -) Configuration and Migration Tool and follow through the onscreen steps .
N.B : You if are interested about the Manual upgradation using the scripts rather using the DBUA you can take the reference of onlineappsdba or Advait Blog . After running for quite a long time (more than ~1 hr) the upgrade finishes . But alas ! life is no longer easy and another problem crops up .Enterprise Manager console is not getting configured as there are some problem with 11g TNS service .Apart from this, everything looks fine after post upgradation messages !
So lets wash hands and think more . The problem was I supposed to delete the Oracle11g TNS Service for 11g from Windows Registry after Software installation only and before creating the DB using DBUA .That is the reason why the
TNS fails and this inturn cause the configuration failure for EMCA . The nuisance created by me and need to solve by me only . This problem might not crops up in your case ,I suppose .Otherwise follow the below steps to create the
TNS . Run the Net Configuration Assistant from Program files OracleHome entry of start menu .Otherwise run : D:\Oradb11g\bin\launch.exe . Create the TNS service is pretty easy there .Add new service with a name and the entry will be added automatically in Windows service list . Check by running : services.msc from Windows Run option . N.B : Dont try to tweak registry and copy 10g TNS listener or modify it to point to 11g . Its pretty hard believe me until you dont know the impact in Windows Heart i.e at Registry ! Also dont try to create service manually by using sc.exe windows utility . Rely on Oracle Native Net Config Assistant all time Hence My Oracle 11g TNS is ready DB is up and running fineSee below :
Now lets resolve the problem of EMCA.Follow the below command line utilities to drop the Enterprise Manager Repository and reconfigure it .Its pretty simple again if you know the right way of doing it and finally reconfigure it .
And finally all is done and lets Cheers !
Follow Me on:
Upgrade Steps From 10g to 11gR2

1. BACKUP BINARIES, DB,TNSNAMES,LISTENER,INIT,SPFILE,PWFILE THAT ARE BEING UPGRADED 2. COMPATIBLE PARAMETER MUST BE SET TO MINIMUM 10.0.0.0. THE RECOMMENDED IS 11.2.0 FOR 11gR2 PARAMETER FILE.
Part A.
Install the New Oracle Database Software & Apply any patches necessary.
Part B.
Run the Pre-Upgrade Information Tool

tool)
(You Must Run This
1. Copy the Pre-Upgrade Information Tool (ufrom the Oracle Database 11gR2 )t directory: $ORACLE_HOME/rdbms/admin to a temporary directory /tmp. 2. Set your environment to the one that is being upgraded. Assuming 10g. 3. Change directory to /tmp that you copied u in Step 1. to t 4. Start SQL*Plus and login as / as sysdba 5. Spool the results to a log file: o SQL> SPOOL upgrade_info.log 6. Run the Pre-Upgrade Information Tool: o SQL> @utlul12i.sql o SQL> SPOOL OFF
Check the output of the Pre-Upgrade Information Tool in upgrade_info.lo g . The following is an example of the output generated by the Pre-Upgrade Information Tool:

Upgrading to the New Release 3-9

3-10 Oracle Database Upgrade Guide

Upgrading to the New Release 3-11
1 .
Check the warning messages and rectify them as needed. The following points must be addressed correctly otherwise there maybe problems. Example: CONNECT role now only has create session privilege.
If you have any db links with passwords, you may want to back up the sys.link$ table to save the information. Oracle recommends gathering stats before the upgrade: EX B M DEC
Deprecated CONNECT Role Access Control to Network Utility Packages Database Links with passwords TIMESTAMP WITH TIME ZONE Data Type Optimizer Statistics Invalid Objects Save Oracle Enterprise Manager Database Control Data Complete Materialized View Refreshes Ensure No Files Need Media Recovery Ensure No Files Are in Backup Mode Resolve Outstanding Distributed Transactions Sync Standby Database with the Primary Database Purging the Database Recycle Bin
Part C.
Prepare the new 11gR2 ORACLE_HOME

1. Copy configuration files (init file, tnsnames, listener, pwfile) from old Oracle Home to new. 2. Update init files with new COMPATIBLE parameter, fix any deprecated ones, and adjust the values to at least the minimum values indicated by the Pre-Upgrade Tool. 3. Update any relative path names in parameter file to fully path names.
Part D.
Upgrade the Database

1. Shutdown the database: o SQL> SHUTDOWN IMMEDIATE; 2. Make sure the following checks:
o The oratab file points to Oracle Database 11g Release 2 Oracle Home o The following environment variables point to the Oracle 11g Release 2 directories: ORACLE_HOME PATH 3. Change to the $ORACLE_HOME/rdbms/admin directory and start SQL*Plus o sqlplus / as sysdba 4. Start the instance by issuing following command (you may get messages that parameters are obsolete, fix those and start up the db again): o SQL> STARTUP UPGRADE; o SQL> SPOOL upgrade.log 5. Run the catupgrd.sql script: o SQL> @catupgrd.sql 6. Once completed, shutdown the database and restart it. o SQL> SHUTDOWN IMMEDIATE; o SQL> STARTUP; 7. Run the Post-Upgrade Status Tool to provide a summary of the upgrade. (If there are any INVALID components, then check upgrade manual for fixes.) o SQL> @utlul12s.sql 8. Run catuppst.sql to perform upgrade actions that do not require db to be in upgrade mode: o SQL> $ORACLE_HOME/rdbms/admin/catuppst.sql 9. Run utlrp to recompile any remaining stored PL/SQL and other objects. o SQL> $ORACLE_HOME/rdbms/admin/utlrp.sql 10. Verify that all objects are valid: o SQL> SELECT count(*) FROM dba_invalid_objects; o SQL> SELECT distinct object_name FROM dba_invalid_objects;
Upgrade Oracle Database 10g to 11g Manual Upgrade

We are going to use Manual Upgrade Install 11g database software in different ORACLE_HOME from source Database
oracle@apt-amd-02:/opt/app/oracle/product/11.1/rdbms/admin> pwd /opt/app/oracle/product/11.1/rdbms/admin oracle@apt-amd-02:/opt/app/oracle/product/11.1/rdbms/admin> ls -lt utlu111i.sql -rw-r--r-- 1 oracle oinstall 138636 2007-07-11 09:01 utlu111i.sql oracle@apt-amd-02:/opt/app/oracle/product/11.1/rdbms/admin> pwd /opt/app/oracle/product/11.1/rdbms/admin oracle@apt-amd-02:/opt/app/oracle/product/11.1/rdbms/admin> sqlplus /nolog SQL*Plus: Release 10.2.0.4.0 - Production on Tue Apr 27 09:28:04 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved. SQL> spool anujupgrade.lst SQL> @utlu111i.sql Oracle Database 11.1 Pre-Upgrade Information Tool 04-27-2010 09:29:25 . ********************************************************************** Database: ********************************************************************** --> name: VIHAAN --> version: 10.2.0.4.0 --> compatible: 10.2.0.3.0 --> blocksize: 8192 --> platform: Linux x86 64-bit --> timezone file: V4 . ********************************************************************** Tablespaces: [make adjustments in the current environment] ********************************************************************** --> SYSTEM tablespace is adequate for the upgrade. .... minimum required size: 727 MB .... AUTOEXTEND additional space required: 247 MB --> UNDOTBS1 tablespace is adequate for the upgrade. .... minimum required size: 473 MB .... AUTOEXTEND additional space required: 443 MB --> SYSAUX tablespace is adequate for the upgrade. .... minimum required size: 425 MB .... AUTOEXTEND additional space required: 175 MB --> TEMP tablespace is adequate for the upgrade. .... minimum required size: 61 MB .... AUTOEXTEND additional space required: 41 MB --> EXAMPLE tablespace is adequate for the upgrade. .... minimum required size: 69 MB . ********************************************************************** Update Parameters: [Update Oracle Database 11.1 init.ora or spfile] ********************************************************************** WARNING: --> "sga_target" needs to be increased to at least 672 MB . ********************************************************************** Renamed Parameters: [Update Oracle Database 11.1 init.ora or spfile] ********************************************************************** -- No renamed parameters found. No changes are required. .
********************************************************************** Obsolete/Deprecated Parameters: [Update Oracle Database 11.1 init.ora or spfile] ********************************************************************** --> "background_dump_dest" replaced by "diagnostic_dest" --> "user_dump_dest" replaced by "diagnostic_dest" --> "core_dump_dest" replaced by "diagnostic_dest" . ********************************************************************** Components: [The following database components will be upgraded or installed] ********************************************************************** --> Oracle Catalog Views [upgrade] VALID --> Oracle Packages and Types [upgrade] VALID --> JServer JAVA Virtual Machine [upgrade] VALID --> Oracle XDK for Java [upgrade] VALID --> Oracle Workspace Manager [upgrade] VALID --> OLAP Analytic Workspace [upgrade] VALID --> OLAP Catalog [upgrade] VALID --> EM Repository [upgrade] VALID --> Oracle Text [upgrade] VALID --> Oracle XML Database [upgrade] VALID --> Oracle Java Packages [upgrade] VALID --> Oracle interMedia [upgrade] VALID --> Spatial [upgrade] VALID --> Data Mining [upgrade] VALID --> Expression Filter [upgrade] VALID --> Rule Manager [upgrade] VALID --> Oracle OLAP API [upgrade] VALID . ********************************************************************** Miscellaneous Warnings ********************************************************************** WARNING: --> Database contains stale optimizer statistics. .... Refer to the 11g Upgrade Guide for instructions to update .... statistics prior to upgrading the database. .... Component Schemas with stale statistics: .... SYS .... OLAPSYS .... SYSMAN .... CTXSYS .... XDB .... MDSYS WARNING: --> Database contains INVALID objects prior to upgrade. .... USER PUBLIC has 1 INVALID objects. .... USER SYS has 2 INVALID objects. WARNING: --> Database contains schemas with objects dependent on network
packages. .... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs. WARNING: --> EM Database Control Repository exists in the database. .... Direct downgrade of EM Database Control is not supported. Refer to the .... 11g Upgrade Guide for instructions to save the EM data prior to upgrade. . PL/SQL procedure successfully completed. SQL> select * from v$timezone_file; If time zone file version is less than 4 then apply time zone patch 5632264 manually select object_name, owner, object_type from all_objects where status like 'INVALID';
SQL> select object_name, owner, object_type from all_objects where status like 'INVALID'; OBJECT_NAME OWNER ------------------------------ -----------------------------OBJECT_TYPE ------------------DBMS_REGISTRY SYS PACKAGE BODY DBA_REGISTRY_DATABASE SYS VIEW DBA_REGISTRY_DATABASE PUBLIC SYNONYM col COMP_NAME format a50 set linesize 200 set pagesize 200 SQL> r 1* select comp_name,version, status from dba_registry COMP_NAME VERSION STATUS -------------------------------------------------- ------------------------------------------------------------------------Oracle Database Catalog Views 10.2.0.4.0 VALID Oracle Database Packages and Types 10.2.0.4.0 VALID Oracle Workspace Manager 10.2.0.4.3 VALID JServer JAVA Virtual Machine 10.2.0.4.0 VALID Oracle XDK 10.2.0.4.0 VALID Oracle Database Java Packages 10.2.0.4.0 VALID
Oracle Expression Filter 10.2.0.4.0 VALID Oracle Data Mining 10.2.0.4.0 VALID Oracle Text 10.2.0.4.0 VALID Oracle XML Database 10.2.0.4.0 VALID Oracle Rules Manager 10.2.0.4.0 VALID Oracle interMedia 10.2.0.4.0 VALID OLAP Analytic Workspace 10.2.0.4.0 VALID Oracle OLAP API 10.2.0.4.0 VALID OLAP Catalog 10.2.0.4.0 VALID Spatial 10.2.0.4.0 VALID Oracle Enterprise Manager 10.2.0.4.0 VALID 17 rows selected.
1.7 If you are using spfile, create pfile SQL> create pfile from spfile ; This will create pfile in 10g $ORACLE_HOME/dbs/init[SID].ora
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
vihaan.__db_cache_size=377487360 vihaan.__java_pool_size=4194304 vihaan.__large_pool_size=4194304 vihaan.__shared_pool_size=142606336 vihaan.__streams_pool_size=0 *.control_files='/opt/app/oracle/datafile/vihaan/control01.ctl','/opt/app/oracle/datafile/vihaa n/control02.ctl','/opt/app/oracle/datafile/vihaan/control03.ctl' *.db_block_size=8192 *.db_domain='apt-amd-02' *.db_file_multiblock_read_count=16
*.db_name='vihaan' *.dispatchers='(PROTOCOL=TCP) (SERVICE=vihaanXDB)' *.job_queue_processes=10 *.nls_language='ENGLISH' *.nls_territory='UNITED KINGDOM' *.open_cursors=300 *.pga_aggregate_target=199229440 *.processes=150 *.remote_login_passwordfile='EXCLUSIVE' *.sga_target=536870912 *.undo_management='AUTO' *.undo_tablespace='UNDOTBS1' *.compatible='11.1.0' *.diagnostic_dest='/opt/app/oracle/admin/vihaan/diagnostic'
oracle@apt-amd-02:/opt/app/oracle/product/10.2/dbs> mkdir -p /opt/app/oracle/admin/vihaan/diagnostic oracle@apt-amd-02:/opt/app/oracle/product/10.2/dbs> cd /opt/app/oracle/admin/vihaan/ oracle@apt-amd-02:/opt/app/oracle/admin/vihaan> ls -lt total 8 drwxr-xr-x 2 oracle oinstall 6 2010-04-27 09:43 diagnostic drwxr-x--- 2 oracle oinstall 4096 2010-04-27 09:29 adump drwxr-x--- 2 oracle oinstall 4096 2010-04-27 09:20 udump drwxr-x--- 2 oracle oinstall 141 2010-04-27 09:20 bdump drwxr-x--- 2 oracle oinstall 35 2010-04-26 13:26 pfile drwxr-x--- 2 oracle oinstall 6 2010-04-26 13:20 cdump drwxr-x--- 2 oracle oinstall 6 2010-04-26 13:20 dpdump
2. Upgrade Database Shut down source database (10g) - Your downtime starts here SQL> connect sys/sys as sysdba Connected. SQL> shutdown immediate ; Database closed. Database dismounted. ORACLE instance shut down.
2.2 Set your environment variables to Oracle Database 11g Release 1 (11.1) :
export ORACLE_HOME=/u01/oracle/11gbase/11.1.0 export ORACLE_SID=TEST export PATH=$ORACLE_HOME/bin:$PATH export ORACLE_BASE=/opt/app/oracle export ORACLE_HOME=/opt/app/oracle/product/10.2 #export ORACLE_HOME=/opt/app/oracle/product/11.1 export ORACLE_SID=vihaan export PATH=$ORACLE_HOME/bin:$PATH:. export LIBXCB_ALLOW_SLOPPY_LOCK=1 export TZ=GMT comment the oracle 10g home and uncomment 11g
2.3 Start Upgrade oracle@apt-amd-02:~> pwd /home/oracle oracle@apt-amd-02:~> sqlplus / as sysdba SQL*Plus: Release 11.1.0.6.0 - Production on Tue Apr 27 09:50:25 2010 Copyright (c) 1982, 2007, Oracle. All rights reserved. Connected to an idle instance. SQL> startup upgrade pfile='/tmp/initvihaan.ora' ; ORACLE instance started. Total System Global Area 534462464 bytes Fixed Size 2146112 bytes Variable Size 150995136 bytes Database Buffers 377487360 bytes Redo Buffers 3833856 bytes Database mounted. Database opened.
Check shared_pool & java_pool size, to set new values
SQL> spool anujupgrade.log SQL> @?/rdbms/admin/catupgrd.sql after catupgrd.sql database will be shutdown .
SQL> /*****************************************************************************/ SQL> /* Step 10 - SHUTDOWN THE DATABASE..!!!!! SQL> */ SQL> /*****************************************************************************/ SQL> shutdown immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL> SQL> SQL> SQL> DOC DOC>############################################################# ########## DOC>############################################################# ########## DOC> DOC> The above sql script is the final step of the upgrade. Please DOC> review any errors in the spool log file. If there are any errors in DOC> the spool file, consult the Oracle Database Upgrade Guide for DOC> troubleshooting recommendations. DOC> DOC> Next restart for normal operation, and then run utlrp.sql to DOC> recompile any invalid application objects. DOC> DOC>############################################################# ########## DOC>############################################################# ########## DOC># SQL> SQL> SQL> SQL> SQL> SQL> Rem Set errorlogging off SQL> SET ERRORLOGGING OFF; SQL> SQL> Rem *********************************************************************
SQL> Rem END catupgrd.sql SQL> Rem ********************************************************************* SQL> =====
SQL> startup pfile='/tmp/initvihaan.ora' ; ORACLE instance started. Total System Global Area 534462464 bytes Fixed Size 2146112 bytes Variable Size 150995136 bytes Database Buffers 377487360 bytes Redo Buffers 3833856 bytes Database mounted. Database opened. SQL> @?/rdbms/admin/utlu111s.sql
Oracle Database 11.1 Post-Upgrade Status Tool 04-27-2010 12:11:48 . Component Status Version HH:MM:SS . Oracle Server . VALID 11.1.0.6.0 00:42:49 JServer JAVA Virtual Machine . VALID 11.1.0.6.0 00:20:34 Oracle Workspace Manager . VALID 10.2.0.4.3 00:00:01 OLAP Analytic Workspace . VALID 11.1.0.6.0 00:00:55 OLAP Catalog . VALID 11.1.0.6.0 00:01:40 Oracle OLAP API . VALID 11.1.0.6.0 00:00:26 Oracle Enterprise Manager . ORA-06550: line 5, column 35: . PL/SQL: ORA-00942: table or view does not exist . ORA-06550: line 5, column 1: . PL/SQL: SQL Statement ignored . ORA-00001: unique constraint (SYSMAN.PARAMETERS_PRIMARY_KEY) violated
. ORA-06512: at "SYSMAN.MGMT_TIME_SYNC", line 108 . ORA-06512: at "SYSMAN.MGMT_TIME_SYNC", line 166 . ORA-06512: at line 2 . VALID 11.1.0.6.0 00:20:30 Oracle XDK . VALID 11.1.0.6.0 00:01:37 Oracle Text . VALID 11.1.0.6.0 00:01:41 Oracle XML Database . VALID 11.1.0.6.0 00:13:43 Oracle Database Java Packages . VALID 11.1.0.6.0 00:00:42 Oracle Multimedia . VALID 11.1.0.6.0 00:09:04 Spatial . VALID 11.1.0.6.0 00:06:41 Oracle Expression Filter . VALID 11.1.0.6.0 00:00:15 Oracle Rules Manager . VALID 11.1.0.6.0 00:00:13 Gathering Statistics . 00:05:25 Total Upgrade Time: 02:06:28 PL/SQL procedure successfully completed. SQL> SQL> SET SERVEROUTPUT OFF SQL> SET VERIFY ON
Workaround: These errors do not result in any data loss. Therefore, you can ignore these errors.
=============================== or apply Patch 7449757 oracle@apt-amd-02:~> unzip p7449757_111070_Generic.zip Archive: p7449757_111070_Generic.zip creating: 7449757/ creating: 7449757/etc/ creating: 7449757/etc/xml/
inflating: 7449757/etc/xml/ShiphomeDirectoryStructure.xml inflating: 7449757/etc/xml/GenericActions.xml creating: 7449757/etc/config/ inflating: 7449757/etc/config/actions.xml inflating: 7449757/etc/config/inventory.xml inflating: 7449757/README.txt creating: 7449757/files/ creating: 7449757/files/rdbms/ creating: 7449757/files/rdbms/admin/ inflating: 7449757/files/rdbms/admin/i1002000.sql oracle@apt-amd-02:~> cd 7449757/ oracle@apt-amd-02:~/7449757> pwd /home/oracle/7449757 oracle@apt-amd-02:~/7449757> /opt/app/oracle/product/11.1/OPatch/opatch apply Invoking OPatch 11.1.0.6.0
====
SQL> @?/rdbms/admin/catuppst.sql SQL> @?/rdbms/admin/utlrp.sql
SQL> create spfile from pfile='/tmp/initvihaan.ora' ; File created.
Check invalid objects SQL> select count(*) from dba_objects where status like 'INVALID'; COUNT(*) ---------0
Post Upgrade steps Check status of database components SQL>select comp_name,version, status from dba_registry; SQL> col COMP_NAME format a40 SQL> set pagesize 200
SQL> set linesize 200 SQL> col STATUS format a15 SQL> select comp_name,version, status from dba_registry COMP_NAME VERSION STATUS ---------------------------------------- ------------------------------ --------------Oracle Enterprise Manager 11.1.0.6.0 VALID OLAP Catalog 11.1.0.6.0 VALID Spatial 11.1.0.6.0 VALID Oracle Multimedia 11.1.0.6.0 VALID Oracle XML Database 11.1.0.6.0 VALID Oracle Text 11.1.0.6.0 VALID Oracle Data Mining 11.1.0.6.0 VALID Oracle Expression Filter 11.1.0.6.0 VALID Oracle Rules Manager 11.1.0.6.0 VALID Oracle Workspace Manager 10.2.0.4.3 VALID Oracle Database Catalog Views 11.1.0.6.0 VALID Oracle Database Packages and Types 11.1.0.6.0 VALID JServer JAVA Virtual Machine 11.1.0.6.0 VALID Oracle XDK 11.1.0.6.0 VALID Oracle Database Java Packages 11.1.0.6.0 VALID OLAP Analytic Workspace 11.1.0.6.0 VALID Oracle OLAP API 11.1.0.6.0 VALID 17 rows selected.
Copy tnsnames.ora, listener.ora, sqlnet.ora and include file from source (10g) oracle_home to target (11g) oracle_home
=== useful link # 429825.1 Complete Checklist for Manual Upgrades to 11gR1 # 744693.1 ORA-00001 For SYS.DIANA_VERSION$ During RDBMS Upgrade From 11.1.0.6 To 11.1.0.7 # 413671.1 Applying version 4 Time Zone Files on an Oracle Database # 396387.1 Workarounds when Database time zone patches are not available for your patchset # 396671.1 Usage of utltzuv2.sql before updating time zone files in Oracle 10 # 730057.1 Upgrading to 11g Fails with ORA-01722: invalid number Check Metalink note: Complete Checklist for Manual Upgrades to 11gR1 - 429825.1
Posted by Anuj Singh at Tuesday, April 27, 2010
2 comments:
Anuj Singh said...
SQL> exec dbms_stats.gather_dictionary_stats; PL/SQL procedure successfully completed. SQL> exec dbms_stats.gather_fixed_objects_stats; PL/SQL procedure successfully completed.
2 September 2011 16:45
Anuj Singh said...
for schema stats exec dbms_stats.gather_schema_stats (ownname=>'PROD1', estimate_percent=>100,method_opt=>'for all columns size skewonly', degree => DBMS_STATS.AUTO_DEGREE ,cascade=>true) ;
Manually upgrade Database (10.2.0.4) to Oracle database 11g2 on RHEL 5
1. Run utlrp.sql to recompile any remaining stored PL/SQL and Java code.
SQL> @utlrp.sql
2. Check dba_registry
column comp_name format a40 set pagesize 50 set line 2000 select trim(comp_name) comp_name , version , status from dba_registry;
3. Verify that all expected packages and classes are valid:

SQL> select count(*) from dba_objects where status <>VALID; SQL>select owner,object_type,count(*) from dba_objects where status <>VALID group by owner,object_type order by 1,2;
4. Backup the database. 5. Analyze the existing instance using the

SQL>@$ORACLE_11G_HOME/rdbms/admin/utlu112i.sql script
6. Shut down the instance:

SQL> SHUTDOWN IMMEDIATE
7. If your operating system is Linux or UNIX, then make the following checks:
a. The oratab file points to your Oracle Database 11g Rel. 2 Oracle home. b. Your ORACLE_SID is set correctly c. The following environment variables point to the Oracle Database 11g2 directories: ORACLE_HOME PATH d. Any scripts that clients use to set the ORACLE_HOME value must point to the New Oracle home. Note: If you are upgrading a cluster database, then perform these checks on all nodes in which this cluster database has instances configured.
8. Log in to the system as the owner of the Oracle Database 11g Release 2 (11.2)
Oracle home directory. At a system prompt, change to the $ORACLE_HOME/rdbms/admin directory.
9. Copy init or spfile file to 11g ORACLE_HOME.
10. Connect to the database instance as a user with SYSDBA privileges.

Start the instance by issuing the following command: SQL> STARTUP UPGRADE
11. Set the system to spool results to a log file for later verification of success:
SQL> SPOOL upgrade.log
12. Run the catupgrd.sql script:

SQL> @catupgrd.sql This scripts runs the desired upgrade scripts and Shuts Down the database.
13. Restart the instance to reinitialize the system parameters for normal operation.
SQL> STARTUP
14. Run utlu112s.sql to display the results of the upgrade:

SQL> @$ORACLE_HOME/rdbms/admin/utlu112s.sql
15. (Optional ) Run catuppst.sql, located in the ORACLE_HOME/rdbms/admin directory, to

perform upgrade actions that do not require the database to be in UPGRADE mode: SQL> @rdbms/admin/catuppst.sql
16. Run utlrp.sql to recompile any remaining stored PL/SQL and Java code.
SQL> @utlrp.sql
17. Verify that all expected packages and classes are valid:
SQL> SELECT count(*) FROM dba_invalid_objects; SQL> SELECT distinct object_name FROM dba_invalid_objects;
18. Exit SQL* Plus
Upgrade Oracle from 10.2.0.1 To 10.2.0.4

1. Patch Set Overview Patch set release 10.2.0.4. Before installing this patch set you must be need 10.2.0.1 version. 2. Requirements Oracle DB : Oracle 10.2.0.1 (later) Operating System: Windows
3. Pre - Installation Tasks 1. Identify prior installation Before installing this patch you must install oracle 10.2.0.1 (or later version) 2. Download Patch set Download 6810189 patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory. 3. Shutdown oracle database. C:\>set oracle_sid= GOLDLINK C:\>sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Nov 13 10:49:26 2007 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. SQL> connect sys@GOLDLINK as sysdba Enter password: Connected. SQL> SHUTDOWN Database closed. Database dismounted. ORACLE instance shut down. 4. Stop all services C:\>set oracle_sid=GoldLink C:\>net stop OracleDBConsoleGOLDLINK The OracleDBConsoleGOLDLINK service is stopping................ The OracleDBConsoleGOLDLINK service was stopped successfully.
C:\>net stop OracleServiceGOLDLINK The OracleServiceGOLDLINK service is stopping. The OracleServiceGOLDLINK service was stopped successfully.
C:\>net stop OracleOraDB10g_Home1iSQL*Plus.. The OracleOraDb10g_home1iSQL*Plus service was stopped successfully. C:\>net stop OracleOraDB10g_Home1TNSListener The OracleOraDb10g_home1TNSListener service is stopping. The OracleOraDb10g_home1TNSListener service was stopped successfully. Note: while patch installation time If you face Distributed Transaction Coordinator still running. You should be stop this service C:\>net stop msdtc The Distributed Transaction Coordinator service is stopping. The Distributed Transaction Coordinator service was stopped successfully. 4. Backup your database & Old oracle binaries. Oracle recommends that you create a backup of the Oracle 10g installation before you install the patch set.
--- Check Tablespace Sizes and Set Parameter Values Review the following sections before upgrading a database.
5. Install the new patch Binaries on same Oracle Home Install the new patch binaries on same oracle home.
6. Upgrade the Database After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home: 1. Start all services 2. Connect sys user C:\> sqlplus /NOLOG SQL> CONNECT SYS/SYS_password AS SYSDBA 3. Enter the following SQL*Plus commands: SQL> STARTUP UPGRADE SQL> SPOOL patch.log SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catupgrd.sql SQL> SPOOL OFF Review the patch.log file for errors and inspect the list of components that is displayed at the end of catupgrd.sql script. This list provides the version and status of each SERVER component in the database. If necessary, rerun the catupgrd.sql script after correcting any problems. 4. Restart the database: SQL> SHUTDOWN SQL> STARTUP 5. Compile Invalid Objects
Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended. SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql SQL> select * from v$version; BANNER ---------------------------------------------------------------Oracle Database 10g Release 10.2.0.4.0 - Production PL/SQL Release 10.2.0.4.0 - Production CORE 10.2.0.4.0 Production TNS for 32-bit Windows: Version 10.2.0.4.0 - Production NLSRTL Version 10.2.0.4.0 - Production
PSU Patch_Implementation_steps 10.2.0.5_ UNIX

A common DBA task is to patch Oracle homes and databases. These patches can be one of the many bug fixes or the quarterly CPU. Regardless of the reason, the following must be done for every database the DBA is responsible for:
1. 2. 3. 4. 5. 6. 7.
The DBA must move the patch software to the server and unzip the file. Make sure the environment is setup properly to run Opatch. Shutdown the listener and database. Patch the Oracle home. Restart the database and listener Run Catcpu.sql. Run Utlrp.sql to compile PL/SQL.
http://www.dba-oracle.com/t_patching_cloning_oracle_home.htm
=================================================================== ====================================================== step 1 --- copy the patch patch software to the server and unzip the file. unzip p10249537_10205_LINUX.zip step 2 --- Shutdown DB ( Shut down all database of ORACLE_HOME) sqlplus /nolog & Listner
conn / as sysdba SQL> create pfile from spfile; SQL> alter database backup controlfile to trace; SQL> shutdown immediate;
$lsnrctl LSNRCTL> status LSNRCTL> stop
step 3 --- Take the backup of ORACLE Binaries & Database ( RMAN or COLD) inventory backup ---------------cat /etc/oraInst.loc tar -cvzf /u01/oradata/backup/myOracleInventoryClonePSU.tar.gz /u01/app/oracle/oraInventory ORACLE_HOME Binaries backup --------------------------tar -cvzf /u01/oradata/backup/myOracleHomeClonePSU.tar.gz /u01/app/oracle/product/10.2.0/db_1 Database Cold Backup --------------------tar -cvzf /u01/oradata/backup/myOracleDATABASEClonePSU.tar.gz /u01/oradata/stumarket
step 4 --- Patch Installation Instructions #Ensure that the $PATH has the following executables: make, ar, ld, and nm. #The location of these executables depends on your operating system. On many operating systems, they are located in /usr/ccs/bin, in which case you can set your PATH as follows: #export PATH=$PATH:/usr/ccs/bin
$ export PATH=$PATH:/usr/bin
#Check applied patches $ORACLE_HOME/OPatch/opatch lsinventory ********************************************************* [oracle@aud1ora01 ~]$ $ORACLE_HOME/OPatch/opatch lsinventory Invoking OPatch 10.2.0.4.9
Oracle Interim Patch Installer version 10.2.0.4.9 Copyright (c) 2009, Oracle Corporation. All rights reserved. Oracle Home : /u01/app/oracle/product/10.2.0/db_1 Central Inventory : /u01/app/oracle/oraInventory from : /etc/oraInst.loc OPatch version : 10.2.0.4.9 OUI version : 10.2.0.5.0 OUI location : /u01/app/oracle/product/10.2.0/db_1/oui Log file location : /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2011-02-14_17-3620PM.log Patch history file: /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt Lsinventory Output file location : /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/lsinv/lsinventory2011-02-14_17-36-20PM.txt -------------------------------------------------------------------------------Installed Top-level Products (2): Oracle Database 10g Oracle Database 10g Release 2 Patch Set 4 There are 2 products installed in this Oracle Home. Interim patches (2) : Patch 9963497 : applied on Thu Feb 10 17:58:14 GMT+05:30 2011 Unique Patch ID: 13098966 Created on 2 Aug 2010, 03:38:02 hrs PST8PDT Bugs fixed: 9963497 Patch 10249537 : applied on Thu Feb 10 17:58:10 GMT+05:30 2011 Unique Patch ID: 13098966 Created on 14 Dec 2010, 08:51:21 hrs PST8PDT Bugs fixed: 10249537, 9952270 10.2.0.1.0 10.2.0.5.0a
-------------------------------------------------------------------------------OPatch succeeded. ************************************************************ #One-off Patch Conflict Detection and Resolution $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /home/oracle/10248542 ************************************************************* [oracle@aud1ora01 10248542]$ $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir /home/oracle/10248542 Invoking OPatch 10.2.0.4.9 Oracle Interim Patch Installer version 10.2.0.4.9 Copyright (c) 2009, Oracle Corporation. All rights reserved.
PREREQ session Oracle Home : /u01/app/oracle/product/10.2.0/db_1 Central Inventory : /u01/app/oracle/oraInventory from : /etc/oraInst.loc OPatch version : 10.2.0.4.9 OUI version : 10.2.0.5.0 OUI location : /u01/app/oracle/product/10.2.0/db_1/oui Log file location : /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2011-02-14_17-3936PM.log Patch history file: /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt Invoking prereq "checkconflictagainstohwithdetail" ZOP-40: The patch(es) has conflicts/supersets with other patches installed in the Oracle Home (or) among themselves. Prereq "checkConflictAgainstOHWithDetail" failed. Summary of Conflict Analysis: Patches that can be applied now without any conflicts are : 10248542 Following patches are not required, as they are subset of the patches in Oracle Home or subset of the patches in the given list : 9963497, 10249537 Following patches will be rolled back from Oracle Home on application of the patches in the given list : 9963497, 10249537 Conflicts/Supersets for each patch are: Patch : 10248542 Bug Superset of 9963497 Super set bugs are: 9963497 Bug Superset of 10249537 Super set bugs are: 10249537, 9952270 OPatch succeeded. ************************************************************* # Update the opatch cp p6880880_102000_LINUX.zip $ORACLE_HOME cd $ORACLE_HOME unzip p6880880_102000_LINUX.zip $ORACLE_HOME/OPatch/opatch version Invoking OPatch 10.2.0.5.1 OPatch Version: 10.2.0.5.1 ===================================
#Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
$ cd 10248542 $ $ORACLE_HOME/OPatch/opatch apply
******************************************** [oracle@aud1ora01 10249537]$ $ORACLE_HOME/OPatch/opatch apply Invoking OPatch 10.2.0.4.9 Oracle Interim Patch Installer version 10.2.0.4.9 Copyright (c) 2009, Oracle Corporation. All rights reserved. UTIL session Oracle Home : /u01/app/oracle/product/10.2.0/db_1 Central Inventory : /u01/app/oracle/oraInventory from : /etc/oraInst.loc OPatch version : 10.2.0.4.9 OUI version : 10.2.0.5.0 OUI location : /u01/app/oracle/product/10.2.0/db_1/oui Log file location : /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2011-02-10_17-5737PM.log Patch history file: /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt Invoking utility "napply" Checking conflict among patches... Checking if Oracle Home has components required by patches... Skip patch 10327179 from list of patches to apply: This patch is not needed. Checking skip_duplicate Checking skip_subset Checking conflicts against Oracle Home... OPatch continues with these patches: 10249537 9963497 Do you want to proceed? [y|n] y User Responded with: Y Running prerequisite checks... OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only. Backing up files affected by the patch 'NApply' for restore. This might take a while... Execution of 'sh /home/oracle/10249537/10249537/custom/scripts/pre -apply 10249537 ': Return Code = 0 Applying patch 10249537... ApplySession applying interim patch '10249537' to OH '/u01/app/oracle/product/10.2.0/db_1' Backing up files affected by the patch '10249537' for rollback. This might take a while...
Patching component oracle.rdbms, 10.2.0.5.0... Copying file to "/u01/app/oracle/product/10.2.0/db_1/rdbms/admin/bundledata_CPU.xml" Copying file to "/u01/app/oracle/product/10.2.0/db_1/cpu/CPUJan2011/catcpu.sql" Copying file to "/u01/app/oracle/product/10.2.0/db_1/cpu/CPUJan2011/catcpu_rollback.sql" Patching component oracle.rdbms.rsf, 10.2.0.5.0... Copying file to "/u01/app/oracle/product/10.2.0/db_1/cpu/CPUJan2011/rollback_all.lst" Copying file to "/u01/app/oracle/product/10.2.0/db_1/cpu/CPUJan2011/rollback_new.lst" ApplySession adding interim patch '10249537' to inventory Verifying the update... Inventory check OK: Patch ID 10249537 is registered in Oracle Home inventory with proper meta-data. Files check OK: Files from Patch ID 10249537 are present in Oracle Home. Applying patch 9963497... ApplySession applying interim patch '9963497' to OH '/u01/app/oracle/product/10.2.0/db_1' Backing up files affected by the patch '9963497' for rollback. This might take a while... Patching component oracle.rdbms, 10.2.0.5.0... Copying file to "/u01/app/oracle/product/10.2.0/db_1/rdbms/admin/prvtjob.plb" ApplySession adding interim patch '9963497' to inventory Verifying the update... Inventory check OK: Patch ID 9963497 is registered in Oracle Home inventory with proper meta-data. Files check OK: Files from Patch ID 9963497 are present in Oracle Home. The local system has been patched and can be restarted. UtilSession: N-Apply done. OPatch succeeded. [oracle@aud1ora01 10249537]$ ************************************************************************************* Step 5 -- Post Installation Instructions Loading Modified SQL Files into the Database -------------------------------------------#For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus. Connect as SYSDBA and run the catbundle.sql script as follows: cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> @catbundle.sql psu apply SQL> @utlrp.sql ################################################################## Check the following log files in $ORACLE_HOME/cfgtoollogs/catbundle for any errors: catbundle_CPU_<database SID>_APPLY_<TIMESTAMP>.log catbundle_CPU_<database SID>_GENERATE_<TIMESTAMP>.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS.
Note --Check the following log file for errors: /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/catbundle/catbundle_CPU_UMARKET_APPLY_2011Feb10_ 18_04_02.log ################################################################## Step 6 -- Cross check patch implementation. $ORACLE_HOME/OPatch/opatch lsinventory ****************************************************************** [oracle@aud1ora01 admin]$ $ORACLE_HOME/OPatch/opatch lsinventory Invoking OPatch 10.2.0.4.9 Oracle Interim Patch Installer version 10.2.0.4.9 Copyright (c) 2009, Oracle Corporation. All rights reserved. Oracle Home : /u01/app/oracle/product/10.2.0/db_1 Central Inventory : /u01/app/oracle/oraInventory from : /etc/oraInst.loc OPatch version : 10.2.0.4.9 OUI version : 10.2.0.5.0 OUI location : /u01/app/oracle/product/10.2.0/db_1/oui Log file location : /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2011-02-10_18-0749PM.log Patch history file: /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt Lsinventory Output file location : /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/lsinv/lsinventory2011-02-10_18-07-49PM.txt -------------------------------------------------------------------------------Installed Top-level Products (2): Oracle Database 10g Oracle Database 10g Release 2 Patch Set 4 There are 2 products installed in this Oracle Home. Interim patches (2) : Patch 9963497 : applied on Thu Feb 10 17:58:14 GMT+05:30 2011 Unique Patch ID: 13098966 Created on 2 Aug 2010, 03:38:02 hrs PST8PDT Bugs fixed: 9963497 Patch 10249537 : applied on Thu Feb 10 17:58:10 GMT+05:30 2011 Unique Patch ID: 13098966 Created on 14 Dec 2010, 08:51:21 hrs PST8PDT Bugs fixed: 10249537, 9952270 10.2.0.1.0 10.2.0.5.0a
-------------------------------------------------------------------------------OPatch succeeded.
************************************************************************************** ******** col col col col col col action_time for a28 action for a6 namespace for a9 version for a10 id for 99999999 comments for a10
select * from registry;
************************************************************************************** ******** ACTION_TIME ACTION NAMESPACE VERSION ID COMMENTS BUNDLE_SERIES ---------------------------- ------ --------- ---------- --------- ---------- -----------------------------10-FEB-11 06.04.02.693640 PM APPLY SERVER 10.2.0.5 2 CPUJan2011 CPU
CPU Patch_Implementation_steps 10.2.0.5_ UNIX

A common DBA task is to patch Oracle homes and databases. These patches can be one of the many bug fixes or the quarterly CPU. Regardless of the reason, the following must be done for every database the DBA is responsible for:
1. 2. 3. 4. 5. 6. 7.
The DBA must move the patch software to the server and unzip the file. Make sure the environment is setup properly to run Opatch. Shutdown the listener and database. Patch the Oracle home. Restart the database and listener Run Catcpu.sql. Run Utlrp.sql to compile PL/SQL.
http://www.dba-oracle.com/t_patching_cloning_oracle_home.htm
=================================================================== ====================================================== step 1 --- copy the patch patch software to the server and unzip the file. unzip p10249537_10205_LINUX.zip step 2 --- Shutdown DB ( Shut down all database of ORACLE_HOME) & Listner
sqlplus /nolog conn / as sysdba SQL> create pfile from spfile; SQL> alter database backup controlfile to trace; SQL> shutdown immediate;
$lsnrctl LSNRCTL> status LSNRCTL> stop
step 3 --- Take the backup of ORACLE Binaries & Database ( RMAN or COLD) inventory backup ---------------cat /etc/oraInst.loc tar -cvzf /u01/oradata/backup/myOracleInventoryClone.tar.gz /u01/app/oracle/oraInventory ORACLE_HOME Binaries backup --------------------------tar -cvzf /u01/oradata/backup/myOracleHomeClone.tar.gz /u01/app/oracle/product/10.2.0/db_1 Database Cold Backup --------------------tar -cvzf /u01/oradata/backup/myOracleDATABASEClone.tar.gz /u01/oradata/stumarket
step 4 --- Patch Installation Instructions #Ensure that the $PATH has the following executables: make, ar, ld, and nm. #The location of these executables depends on your operating system. On many operating systems, they are located in /usr/ccs/bin, in which case you can set your PATH as follows: #export PATH=$PATH:/usr/ccs/bin
$ export PATH=$PATH:/usr/bin
#Check applied patches $ORACLE_HOME/OPatch/opatch lsinventory *********************************************************
[oracle@aud1ora01 10249537]$ $ORACLE_HOME/OPatch/opatch lsinventory Invoking OPatch 10.2.0.4.9 Oracle Interim Patch Installer version 10.2.0.4.9 Copyright (c) 2009, Oracle Corporation. All rights reserved. Oracle Home : /u01/app/oracle/product/10.2.0/db_1 Central Inventory : /u01/app/oracle/oraInventory from : /etc/oraInst.loc OPatch version : 10.2.0.4.9 OUI version : 10.2.0.5.0 OUI location : /u01/app/oracle/product/10.2.0/db_1/oui Log file location : /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2011-02-10_17-5635PM.log Patch history file: /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt Lsinventory Output file location : /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/lsinv/lsinventory2011-02-10_17-56-35PM.txt -------------------------------------------------------------------------------Installed Top-level Products (2): Oracle Database 10g Oracle Database 10g Release 2 Patch Set 4 There are 2 products installed in this Oracle Home. 10.2.0.1.0 10.2.0.5.0a
There are no Interim patches installed in this Oracle Home. -------------------------------------------------------------------------------OPatch succeeded. ************************************************************
#Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
$ cd 10249537 $ ORACLE_HOME/OPatch/opatch napply -skip_subset -skip_duplicate ******************************************** [oracle@aud1ora01 10249537]$ $ORACLE_HOME/OPatch/opatch napply -skip_subset -skip_duplicate Invoking OPatch 10.2.0.4.9 Oracle Interim Patch Installer version 10.2.0.4.9 Copyright (c) 2009, Oracle Corporation. All rights reserved. UTIL session Oracle Home : /u01/app/oracle/product/10.2.0/db_1 Central Inventory : /u01/app/oracle/oraInventory from : /etc/oraInst.loc
OPatch version : 10.2.0.4.9 OUI version : 10.2.0.5.0 OUI location : /u01/app/oracle/product/10.2.0/db_1/oui Log file location : /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2011-02-10_17-5737PM.log Patch history file: /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt Invoking utility "napply" Checking conflict among patches... Checking if Oracle Home has components required by patches... Skip patch 10327179 from list of patches to apply: This patch is not needed. Checking skip_duplicate Checking skip_subset Checking conflicts against Oracle Home... OPatch continues with these patches: 10249537 9963497 Do you want to proceed? [y|n] y User Responded with: Y Running prerequisite checks... OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only. Backing up files affected by the patch 'NApply' for restore. This might take a while... Execution of 'sh /home/oracle/10249537/10249537/custom/scripts/pre -apply 10249537 ': Return Code = 0 Applying patch 10249537... ApplySession applying interim patch '10249537' to OH '/u01/app/oracle/product/10.2.0/db_1' Backing up files affected by the patch '10249537' for rollback. This might take a while... Patching component oracle.rdbms, 10.2.0.5.0... Copying file to "/u01/app/oracle/product/10.2.0/db_1/rdbms/admin/bundledata_CPU.xml" Copying file to "/u01/app/oracle/product/10.2.0/db_1/cpu/CPUJan2011/catcpu.sql" Copying file to "/u01/app/oracle/product/10.2.0/db_1/cpu/CPUJan2011/catcpu_rollback.sql" Patching component oracle.rdbms.rsf, 10.2.0.5.0... Copying file to "/u01/app/oracle/product/10.2.0/db_1/cpu/CPUJan2011/rollback_all.lst" Copying file to "/u01/app/oracle/product/10.2.0/db_1/cpu/CPUJan2011/rollback_new.lst" ApplySession adding interim patch '10249537' to inventory Verifying the update... Inventory check OK: Patch ID 10249537 is registered in Oracle Home inventory with proper meta-data. Files check OK: Files from Patch ID 10249537 are present in Oracle Home. Applying patch 9963497... ApplySession applying interim patch '9963497' to OH '/u01/app/oracle/product/10.2.0/db_1' Backing up files affected by the patch '9963497' for rollback. This might take a while... Patching component oracle.rdbms, 10.2.0.5.0... Copying file to "/u01/app/oracle/product/10.2.0/db_1/rdbms/admin/prvtjob.plb" ApplySession adding interim patch '9963497' to inventory Verifying the update... Inventory check OK: Patch ID 9963497 is registered in Oracle Home inventory with proper meta-data. Files check OK: Files from Patch ID 9963497 are present in Oracle Home.
The local system has been patched and can be restarted. UtilSession: N-Apply done. OPatch succeeded. [oracle@aud1ora01 10249537]$ ************************************************************************************* Step 5 -- Post Installation Instructions Loading Modified SQL Files into the Database -------------------------------------------#For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus. Connect as SYSDBA and run the catbundle.sql script as follows: cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> @catbundle.sql cpu apply SQL> @utlrp.sql ################################################################## Check the following log files in $ORACLE_HOME/cfgtoollogs/catbundle for any errors: catbundle_CPU_<database SID>_APPLY_<TIMESTAMP>.log catbundle_CPU_<database SID>_GENERATE_<TIMESTAMP>.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. Note --Check the following log file for errors: /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/catbundle/catbundle_CPU_UMARKET_APPLY_2011Feb10_ 18_04_02.log ################################################################## Step 6 -- Cross check patch implementation. $ORACLE_HOME/OPatch/opatch lsinventory ****************************************************************** [oracle@aud1ora01 admin]$ $ORACLE_HOME/OPatch/opatch lsinventory Invoking OPatch 10.2.0.4.9 Oracle Interim Patch Installer version 10.2.0.4.9 Copyright (c) 2009, Oracle Corporation. All rights reserved. Oracle Home : /u01/app/oracle/product/10.2.0/db_1 Central Inventory : /u01/app/oracle/oraInventory from : /etc/oraInst.loc OPatch version : 10.2.0.4.9 OUI version : 10.2.0.5.0 OUI location : /u01/app/oracle/product/10.2.0/db_1/oui
Log file location : /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2011-02-10_18-0749PM.log Patch history file: /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt Lsinventory Output file location : /u01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/lsinv/lsinventory2011-02-10_18-07-49PM.txt -------------------------------------------------------------------------------Installed Top-level Products (2): Oracle Database 10g Oracle Database 10g Release 2 Patch Set 4 There are 2 products installed in this Oracle Home. Interim patches (2) : Patch 9963497 : applied on Thu Feb 10 17:58:14 GMT+05:30 2011 Unique Patch ID: 13098966 Created on 2 Aug 2010, 03:38:02 hrs PST8PDT Bugs fixed: 9963497 Patch 10249537 : applied on Thu Feb 10 17:58:10 GMT+05:30 2011 Unique Patch ID: 13098966 Created on 14 Dec 2010, 08:51:21 hrs PST8PDT Bugs fixed: 10249537, 9952270 10.2.0.1.0 10.2.0.5.0a
-------------------------------------------------------------------------------OPatch succeeded. ************************************************************************************** ******** col col col col col col action_time for a28 action for a6 namespace for a9 version for a10 id for 99999999 comments for a10
select * from registry; ************************************************************************************** ******** ACTION_TIME ACTION NAMESPACE VERSION ID COMMENTS BUNDLE_SERIES ---------------------------- ------ --------- ---------- --------- ---------- -----------------------------10-FEB-11 06.04.02.693640 PM APPLY SERVER 10.2.0.5 2 CPUJan2011 CPU
UPGRADATION 10gR2 to 11gR1

Pre-Requisite:
You should have the Oracle database 10g, which you want to migrate. OS level should be RHEL 4.0 Also here we are upgrading to Oracle Database 11g Beta 6 (11.1.0.6)
Step 1) Installing Oracle 11g Home We cannot upgrade the existing Oracle Home, since 11g is not a patchset. We have to install 11g oracle home as a separate ORACLE_HOME in parallel to 10g Oracle Home.
Step 2) Pre-Upgrade Utility In 11g Home you installed, go to $ORACLE_HOME/rdbms/admin and copy the file utlu111i.sql to some temp location. for more about utlu111i.sql :
http://oracleflash.com/38/Oracle-11g-Release-1-Pre-Upgrade-tool-utlu111i-sql.html
Step 3) Executing the recommended steps Following are the critical steps to be executed based on above warnings. These commands are to be executed while connecting to database from 10g Oracle Home 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.
Finding the Version of existing timezone files: SQL> select version from v$timezone_file;
version -----------2
here oracle 10.2.0.1 has timezone file version of 2
Before you upgrade your timezone file version, you must run utltzuv2.sql to see if there is data that will be affected by the timezone file version upgrade. The script utltzuv2.sql creates a table
named sys.sys_tzuv2_temptab, and fills it with data that may get affected by the timezone file version.
SQL > select * from sys.sys_tzuv2_temptab ; no rows selected
here we see no rows but if we see any rows then we need to take that data backup and restore after timezone file version upgrade
Step 4) Run Pre-Upgrade Utility again
Run utlrp.sql to validate the objects if there is any invalidate objects. SQL> @?/rdbms/admin/utlrp.sql To View the INVALID Objects use: SQL> select count(*) from dba_objects
Create pfile from spfile --It creates pfile for database in ORACLE_HOME/dbs location(init<dbname>.ora) Shutdown -shut down the database in oracle 10g. Copy the pfile of database from ORACLE_HOME/dbs(10g) to ORACLE_HOME/dbs(11g) using cp command. In that make changes shown below, 1. 2. 3. 4. Remove BDUMP, CDUMP, UDUMP and their locations Add Diagnostic_dest=/$ORACLE_BASE/diag-location for diagnostic dest Change audit_file_dest location Change compatibility to 11g and save it.
After executing the recommended steps, run the pre-upgrade utility once again to make sure, you dont get any critical warnings. If everything looks fine, shut down the database from 10g Oracle Home.
Step 5) Starting Upgrade
Source the following variables for 11g Oracle Home [oracle@ocvmrh2178 db_1]$ export ORACLE_HOME=/home/oracle/oracle/product/product/11.1.0/db_1 [oracle@ocvmrh2178 db_1]$ export PATH=$ORACLE_HOME/bin:$PATH [oracle@ocvmrh2178 db_1]$ export ORACLE_SID=orcl [oracle@ocvmrh2178 db_1]$ export TNS_ADMIN=$ORACLE_HOME/network/admin connected to the database sys as sysdba sqlplus / as sysdba > will be connected to idle instance SQL> startup upgrade SQL> SPOOL upgrade.log SQL> @catupgrd.sql Once the upgrades finishes. It will shut down the database automatically. Login again as sysdba and startup in normal mode. Check the dba_registry for the components and its status SQL> select COMP_NAME, STATUS, VERSION from DBA_REGISTRY;
Step 6) Post-Upgrade Steps Once the upgrade completes, restart the instance to reinitialize the system parameters for normal operation. SQL> STARTUP
Run utlu111s.sql to display/verify the results of the upgrade: SQL> @?/rdbms/admin/utlu111s.sql Run catuppst.sql, located in the ORACLE_HOME/rdbms/admin directory, to perform upgrade actions that do not require the database to be in UPGRADE mode: SQL> @?/rdbms/admin/catuppst.sql Run utlrp.sql to recompile invalid objects
SQL> select count(*) from dba_objects where status = INVALID;

10G To 11G

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

10G To 11G

Încărcat de

Drepturi de autor:

Formate disponibile

Upgrade Oracle 10g Release 2 from 10201 to 10204

Preparing for the upgrade to 10.2.0.4

ORA-00942: table or view does not exist

Install the patchset 10.2.0.4

The first screen is welcome screen.

Upgrade the database from 10.2.0.1 to 10.2.0.4

Restore the database back to 10.2.0.1 if any thing failed

Upgrade Oracle 10g from 10.2.0.1 to 10.2.0.4 (Single Instance)

Before database upgrade it is recommanded to backup the PRODUCTION database.

1. Stop all services of oracle

[oracle@ittestdb ~]$ lsnrctl stop

LSNRCTL for Linux: Version 10.2.0.1.0 Production on 08-FEB-2010 13:17:18

Copyright (c) 1991, 2005, Oracle.

All rights reserved.

SQL*Plus: Release 10.2.0.1.0 Production on Mon Feb 8 13:17:29 2010

Copyright (c) 1982, 2005, Oracle.

All rights reserved.

Step 2: Install the Database Patch Set

Checking installer requirements

All installer requirements met.

Step 3 : Upgrade Database

[oracle@ittestdb ~]$ sqlplus /as sysdba

SQL*Plus: Release 10.2.0.4.0 Production on Mon Feb 8 13:28:53 2010

Copyright (c) 1982, 2007, Oracle.

All Rights Reserved.

Connected to an idle instance.

SQL> STARTUP UPGRADE ORACLE instance started.

Database Buffers Redo Buffers Database mounted. Database opened. SQL>

889192448 bytes 15507456 bytes

SQL> STARTUP UPGRADE ORACLE instance started.

> compatible: 10.2.0.1.0

> JServer JAVA Virtual Machine [upgrade]

[upgrade] [upgrade] [upgrade] [upgrade] [upgrade] [upgrade] [upgrade] [upgrade]

VALID VALID VALID VALID VALID VALID VALID VALID

PL/SQL procedure successfully completed.

SQL> SPOOL OFF;

SQL> SPOOL /u01/stage/patch/Disk1/patch.log

177 178 179 180

PROCEDURE selectTablespace( tsname

SQL> SQL> SQL> SQL> SPOOL OFF

Database Buffers Redo Buffers Database mounted. Database opened. SQL>

872415232 bytes 15507456 bytes

To compile invalid objects

DOC> point to system misconfiguration or resource constraints that must be

DOC> fixed before attempting to recompile these objects.

OBJECTS WITH ERRORS

DOC> recompilation. If this number is non-zero, please query the error

DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors

DOC> are due to misconfiguration or resource constraints that must be

DOC> fixed before objects can compile successfully.

ERRORS DURING RECOMPILATION

SQL> SQL> select comp_name, version, status from sys.dba_registry;

Oracle Database Catalog Views 10.2.0.4.0 VALID

Oracle Database Packages and Types 10.2.0.4.0 VALID

Oracle Workspace Manager 10.2.0.4.3 VALID

JServer JAVA Virtual Machine 10.2.0.4.0 VALID

Oracle XDK 10.2.0.4.0 VALID

Oracle Database Java Packages 10.2.0.4.0 VALID

Oracle Expression Filter 10.2.0.4.0 VALID

Oracle Data Mining 10.2.0.4.0 VALID

Oracle Text 10.2.0.4.0 VALID

Oracle XML Database 10.2.0.4.0 VALID

Oracle Rule Manager 10.2.0.4.0 VALID