Patch Number : 6810189
Download p6810189_10204_Linux-x86-64.zip
we don't have to perform. actions for the update of DST to v4, in case see more details in Oracle MetaLink document 553812.1
Case for 64bit RAC DB upgrade to 10.2.0.4
Stopping All Processes for an Oracle Clusterware Installation
$ emctl stop dbconsole
$ isqlplusctl stop
$ lsnrctl stop
$ srvctl stop database -d {DB_name}
$ srvctl stop nodeapps -n {Node_name} all node
-- AS root user
# $ORA_CRS_home/bin/crsctl stop crs
Backup System first
$ORACLE_BASE/*
EX.# tar zcvf u01_0626.tar.gz $ORACLE_BASE/*
$CRS_HOME/*
EX.# tar zcvf CRS_0626.tar.gz $ORA_CRS_HOME/*
$ unzip p6810189_10204_Linux-x86-64.zip
$ Disk1/runInstaller
[GUI]
(1)On the Welcome screen, click Next.
(2)On the Specify Home Details screen, select the CRS_HOME, then click Next.
(3)Click Next when the Selected Nodes screen appears.
(4)On the Product-specific Prerequisite Checks screen, correct any reported errors, and click Next.
(5)Don't registration and configuration on OCM (Oracle Configuration Manager)
(6)On the Summary screen, click Install.
- AS root (Run on each node)
# ORA_CRS_home/bin/crsctl stop crs
# ORA_CRS_home/install/root102.sh
(7)On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer.
Stopping All Processes for an Oracle RAC Installation
$ emctl stop dbconsole
$ isqlplusctl stop
$ service stop database -d {db_name}
$ service stop nodeapps -n {node_name} (全部的node)
$ cd patchset_directory/Disk1
$ ./runInstaller
(1)On the Welcome screen, click Next.
(2)On the Specify Home Details screen, select the name Oracle_DB_Home, then click Next.
(3)Click Next when the Selected Nodes screen appears.
(4)On the Product-specific Prerequisite Checks screen, correct any reported errors, and click Next.
(5)Don't registration and configuration on OCM (Oracle Configuration Manager)
(6)On the Summary screen, click Install.
Run /u01/app/oracle/10.2.0/db_1/root.sh on all node
(7)On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer
The Pre-Upgrade Information Tool is a SQL script. that ships with Oracle Database 10.2. Complete the following procedure to run the Pre-Upgrade Information Tool:
1. Start the database in the UPGRADE mode:
SQL> STARTUP UPGRADE
2. Set the system to spool results to a log file for later analysis:
SQL> SPOOL upgrade_info.log
3. Run the Pre-Upgrade Information Tool:
SQL> @?/rdbms/admin/utlu102i.sql
4. Turn off the spooling of script. results to the log file:
SQL> SPOOL OFF
Check DB information from upgrade_info.log
Log in as the Oracle software owner user.
For Oracle RAC installations, start listener on each node of the cluster as follows:
$ srvctl start listener -n node
If you are using Automatic Storage Management, start the Automatic Storage Management instance.
For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus / as sysdba
For Oracle RAC installations:
1.Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus / as sysdba
SQL> STARTUP NOMOUNT
2. Set the CLUSTER_DATABASE initialization parameter to FALSE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
3. Shut down the database:
SQL> SHUTDOWN
Enter the following SQL*Plus commands:
SQL> STARTUP UPGRADE
SQL> SPOOL patch.log
SQL> @?/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.
Restart the database:
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP
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> @?/rdbms/admin/utlrp.sql
SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;
In the output of the preceding command, the status of all the components should be VALID for a successful upgrade.
[oracle@test01 ~]$ rman target / catalog xxx/xxx@{catalog_db}
Recovery Manager: Release 10.2.0.4.0 - Production on Thu Jun 26 05:02:37 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: {DB_name} (DBID=13xxxxxxxx)
connected to recovery catalog database
RMAN> upgrade catalog;
recovery catalog owner is RMAN
enter UPGRADE CATALOG command again to confirm catalog upgrade
RMAN> upgrade catalog;
recovery catalog upgraded to version 10.02.00.04
DBMS_RCVMAN package upgraded to version 10.02.00.04
DBMS_RCVCAT package upgraded to version 10.02.00.04
RMAN> exit
Recovery Manager complete.
開啟資料庫
1. Set the CLUSTER_DATABASE initialization parameter to TRUE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
2. Restart the database:
SQL> SHUTDOWN IMMEDIATE
3. Start any database services that you want to use:
$ srvctl start nodeapps -n {node_name} (全部的Node)