Note:
The 32-bit version of the patch set must be installed only on the 32-bit version of the database software, regardless of whether the operating system is 32-bit or 64-bit. The 64-bit version of the patch set must be installed only on the 64-bit version of the database software that runs on the 64-bit operating system.
Oracle Universal Installer Version Requirements :
This patch set includes Oracle Universal Installer release 10.1.0.3.
You must use this Oracle Universal Installer to install this patch set and not the Installer from the 9.2.0.x maintenance release media or Oracle home.
This is not a complete software distribution. You must install it in an existing Oracle9i release 2 (9.2.0.x.x) installation. Users applying this patch set must use Oracle Universal Installer release 10.1.0.3 (provided as part of this patch set) or later to ensure that their Oracle home can be patched in the future. Oracle Universal Installer release 10.1.0.3 is also installed when you install this patch set.
System Requirements
The following are the system requirements for this patch set:
Operating System
Solaris 2.6, Solaris 7, Solaris 8, or Solaris 9
Oracle9i
Oracle9i release 2 (9.2.0.1.0) or later
Pre-installation Tasks
Upgrade and SYS Schema
This is a generic issue applicable to the upgrade mode, for example, ALTER DATABASE OPEN MIGRATE. During an upgrade from release 9.2.0.1 or later, the catpatch.sql script can take a long time if there are statistics for the SYS schema. Delete the statistics on all of the objects in the SYS schema, and then re-collect the statistics after normal database open, if necessary.
To drop and re-create the statistics, enter the following commands in SQL*Plus:
EXEC DBMS_STATS.DELETE_SCHEMA_STATS('SYS');
EXEC DBMS_STATS.GATHER_SCHEMA_STATS('SYS');
BACKUP
control file backup
spfile backup
archive log
export backup
oracle installation backup
Special Considerations for Oracle Real Application Clusters
If you plan to install this patch in an Oracle Real Application Clusters environment, read the following sections before proceeding:
If the directory /usr/ucb is in the search path on a UNIX system, then ensure that it is listed after /usr/bin and /usr/ccs/bin in the $PATH setting.
$ echo $PATH
/usr/bin:/etc:.:/bin:/usr/bin:/usr/sbin:/opt/bin:/usr/ccs/bin:/opt/local/GNU/bin
:/opt/local/bin:/opt/NSCPnav/bin:/oracle/oracleapp/product/9.2.0.1.0/bin:/usr/lo
cal/samba/bin:/usr/ucb:/usr/local/bin:.
Pre-installation Considerations for Oracle Real Application Clusters
This patch set enables you to install the included patches on multiple nodes in a cluster if release 9.2.0.1 or higher is already installed on those nodes. Oracle Universal Installer detects whether the system where you are installing the software is part of a cluster environment. If it is, then the Oracle Universal Installer displays the available nodes from the cluster.
Note:
You must install this patch set on the same set of nodes that the base release was installed on.
Pre-installation Considerations for Oracle Real Application Clusters with Sun Clusterware
The UDLM 3.3.4.7 patch must be installed before applying this patch set for Oracle Real Application Clusters environments. The UDLM patch is included in this patch set. The installation instructions are located in the /Disk1/racpatch/README.udlm file.
$ pkginfo -l ORCLudlm
PKGINST: ORCLudlm
NAME: Oracle UNIX Distributed Lock Manager
CATEGORY: system
ARCH: sparc
VERSION: Dev Release 10/29/03, 64bit 3.3.4.7 reentrant
BASEDIR: /opt
VENDOR: Oracle Corporation
DESC: Oracle UNIX Distributed Lock Manager
PSTAMP: Built on 10/29/03 using Solaris 2.8
INSTDATE: Jun 29 2004 13:16
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 46 installed pathnames
3 shared pathnames
12 directories
7 executables
8493 blocks used (approx)
Identify the Oracle9i Installation
This is not a complete software distribution. You must install it in an existing Oracle9i Oracle home. To identify Oracle home directories, view the /var/opt/oracle/oratab file.
If you are installing this patch set on an existing Oracle Real Application Clusters (RAC) installation, you must run the Installer from the same node from which you performed the initial installation.
Check Post-release Updates
Before installing this patch set in a production environment, review document 189908.1, ALERT: Oracle9i Release 2 (9.2) Support Status and Alerts, available on the OracleMetaLink Web site at:
http://metalink.oracle.com/
To locate this document:
Click Advanced at the top of the OracleMetalink page.
Enter 189908.1 in the Document ID field, then click Submit.
This document is created by Oracle Support Services and provides information about the status of issues discovered after this patch set was released. If you are unable to access this site, then contact Oracle Support Services before installing this patch set in a production environment.
Download and Extract the Installation Software
To download and extract the patch set installation software:
Download the p3948480_9206_solaris64.zip patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory.
Enter the following commands to unzip and extract the installation files:
$ unzip p3948480_9206_solaris64.zip
Set the ORACLE_HOME and ORACLE_SID Environment Variables
Enter the following commands to set the ORACLE_HOME and ORACLE_SID environment variables:
Bourne, Bash, or Korn shell:
$ ORACLE_HOME=oracle_home
$ ORACLE_SID=sid
$ export ORACLE_HOME ORACLE_SID
C shell:
% setenv ORACLE_HOME oracle_home
% setenv ORACLE_SID sid
In these examples, oracle_home is the Oracle home directory where the Oracle9i installation that you want to upgrade is installed, and sid is the SID of the database that you want to upgrade.
These steps may not be required if profile path is set correctly
Shut Down Oracle Databases
Shut down any existing Oracle database instances with normal or immediate priority. On RAC systems, shut down all instances on each node.
Stop All Processes
Stop all listener and other processes running in the Oracle home directory where you want to install the patch set.
Back Up the System
Oracle recommends that you create a backup of the Oracle9i installation before you install the patch set. After the patch set is installed, there is no way to remove it.
Installation Tasks
You can install the patch set either interactively or non-interactively. See one of the following sections for information about how to complete the installation
Installing the Patch Set Interactively
To install the Oracle9i patch set interactively:
Note:
If you attempt to install this patch set in an Oracle home directory that does not contain an Oracle9i installation, the Installer displays a warning dialog with the following error:
There are no patches that need to be applied from the
patchset Oracle9i patch set 9.2.0.6.0
The Oracle Universal Installer does not allow the installation to proceed. Click OK, then click Cancel to end the installation.
Log in as the Oracle software owner (typically oracle).
Use Xreflection from a PC to connect to the Sun server .That is an easy way.
If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:
Bourne, Bash, or Korn shell:
$ DISPLAY=local_host:0.0 ; export DISPLAY
C shell:
% setenv DISPLAY local_host:0.0
In this example, local_host is the host name or IP address of the system that you want to use to display the Installer (your workstation or PC).
This step may not be necessary
Enter the following commands to start the Installer, where patchset_directory is the directory where you unzipped the patch set software:
% cd patchset_directory/Disk1
% ./runInstaller
Or use file manager goto the path and double click the runinstaller file
On the Welcome screen, click Next.
On the Specify File Locations screen, click Browse next to the Path field in the Source section.
Select the products.xml file from the stage directory where you unpacked the patch set files, then click Next. For example:
patchset_directory/Disk1/stage/products.xml
In the Name field in the Destination section, select the name of the Oracle home that you want to update from the drop down list, then click Next.
Click Next when the Selected Nodes screen appears.
Note:
The Selected Nodes screen lists the existing Oracle9i RAC release 2 (9.2) nodes. The first node in the list is the node from where Oracle9i RAC release 2 (9.2) was installed. You must install the patch set software from this node. If this is not the node where you are running the Installer, exit the Installer and install the patch set software from the first node in the list of nodes.
On the Summary screen, click Install.
This screen lists all of the patches available for installation.
Takes long time at 77 %
When prompted, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to a RAC installation, then run the root.sh script on each node of the cluster.$ su -
Password:
Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
You have new mail.
Sourcing //.profile-EIS.....
oracle@icai1 # /oracle/oracleapp/product/9.2.0.1.0/root.sh
Running Oracle9 root.sh script...
The following environment variables are set as:
ORACLE_HOME= /oracle/oracleapp/product/9.2.0.1.0
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
oracle@icai1 # telnet 10.0.0.2
Trying 10.0.0.2...
Connected to 10.0.0.2.
Escape character is '^]'.
SunOS 5.8
login: root
Password:
Last login: Sun Oct 9 14:05:41 from 10.0.0.14
Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
You have new mail.
Sourcing //.profile-EIS.....
root@icai2 # /oracle/oracleapp/product/9.2.0.1.0/root.sh
Running Oracle9 root.sh script...
The following environment variables are set as:
ORACLE_HOME= /oracle/oracleapp/product/9.2.0.1.0
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
root@icai2 #
On the End of Installation screen, click Exit, then click Yes to exit from the Installer.
Post-installation Tasks
Review the information in this section before using the upgraded software. This section lists required and optional post-installation tasks, depending on the installation type and the products that you want to use.
Required Post-installation Tasks
Check Tablespace Sizes and Set Parameter Values
Review the following sections before upgrading a database.
Check SYSTEM Tablespace Size
If JServer is part of the installation ensure that there is at least 10 MB of free space allocated to the SYSTEM tablespace.
Check XDB Tablespace Size
For RAC installations, ensure that there is at least 50 MB of free space allocated to the XDB tablespace.
TABLESPACE_NAME MB
CWMLITE 170
DRSYS 85
EXAMPLE 354
INDX 1141
ODM 231
RACCONFIG 635
SYSTEM 1705
TEMPSCHEMA 2282
TOOLS 10
UNDOTBS 1 2865
UNDOTBS 2 2888
USERS 0
XDB 475
21 rows selected.
Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters
Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters as follows:
Start the database:
SQL> STARTUP
If necessary, enter the following command to determine whether the system uses an initialization parameter file (initsid.ora) or a server parameter file (spfiledbname.ora):
SQL> SHOW PARAMETER PFILE;
This command displays the name and location of the server parameter file or the initialization parameter file.
Determine the current values of these parameters:
SQL> SHOW PARAMETER SHARED_POOL_SIZE
SQL> SHOW PARAMETER JAVA_POOL_SIZE
If the system is using a server parameter file:
If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
If the system uses an initialization parameter file, if necessary change the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora).
Shut down the database:
SQL> SHUTDOWN
Upgrade the Database
After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home:
Log in as the Oracle software owner (typically oracle).
Start the Global Services Daemon (GSD) on each node of the cluster as follows:
$ gsdctl start
Start the Oracle Net listener as follows:
$ lsnrctl start
start the listener on each node of the cluster.
Start the database as follows, where db_name is the database name:
$ srvctl start database -d db_name
Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
Set the CLUSTER_DATABASE initialization parameter to FALSE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;
Note:
If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameter to FALSE in the initialization parameter file (initsid.ora).
Exit SQL*Plus and shut down the database:
SQL> EXIT
$ srvctl stop database -d db_name
Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
Enter the following SQL*Plus commands:
SQL> STARTUP MIGRATE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catpatch.sql
SQL> SPOOL OFF
Review the patch.log file for errors and inspect the list of components that is displayed at the end of catpatch.sql script.
This list provides the version and status of each SERVER component in the database.
If necessary, rerun the catpatch.sql script after correcting any problems.
Restart the database:
SQL> SHUTDOWN
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
Set the CLUSTER_DATABASE initialization parameter to TRUE:
SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;
Note:
If the system uses an initialization parameter file, change the value of the CLUSTER_DATABASE initialization parameters to TRUE in the initialization parameter file (initsid.ora).
Restart the database:
SQL> SHUTDOWN
SQL> STARTUP
No comments:
Post a Comment