Home » RDBMS Server » Server Administration » Upgradation from 8.1.7.4 to 9.2.0.8
| Upgradation from 8.1.7.4 to 9.2.0.8 [message #220562] |
Wed, 21 February 2007 05:06  |
Suresh B
Messages: 10
Registered: October 2003
|
Junior Member |
|
|
Hellow!
As per the requirements, one of our database has to be upgraded from 8.1.7.4 to 9.2.0.8
OS : Sun Solaris
Source : oracle8.1.7.4
Destination : 9.2.0.8
Could anyone help me out on below activities.
1. Earlier I have installed the 9.2.0 base and upgraded upto 9.2.0.4. I want to know,is there any direct patch for 9.2.0.8 from the base version of 9.2.0.
If not pls provide me the procedure that how to build a 9.2.0.8 environment on Solaris5.8
2. The upgrade procedure from 8.1.7.4 to 9.2.0.8
Kindly provide the required docs at the earliest.
Regards,
Suresh.
|
|
|
|
|
|
| Re: Upgradation from 8.1.7.4 to 9.2.0.8 [message #220579 is a reply to message #220571] |
Wed, 21 February 2007 05:30  |
Suresh B
Messages: 10
Registered: October 2003
|
Junior Member |
|
|
Hi Mahesh,
Thanks for the response.
I have this document already and if you can provide the environment build document for oracle9.2.0.8 that would really help me. I need the info about the installation of Oracle9.2.0.8 on Solaris.
Thanks,
Suresh.
|
|
|
|
|
|
|
|
| Re: Upgradation from 8.1.7.4 to 9.2.0.8 [message #220589 is a reply to message #220581] |
Wed, 21 February 2007 05:43 |
sshpocp
Messages: 9
Registered: January 2007
Location: India
|
Junior Member |
|
|
Hi,
Below is the Readme contents of 9.2.0.8 patchset
================================================================
5.6 Download and Extract the Installation Software
To download and extract the patch set installation software:
Download and extract the patch set p4547809_9208_solaris64.zip installation archive to a directory that is not the Oracle home directory or under the Oracle home directory. For example, Oracle_patch.
Enter the following commands to unzip and extract the installation files:
$ unzip p4547809_9208_solaris64.zip
5.7 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 system identifier of the database that you want to upgrade.
5.8 Shut Down Oracle Databases
Shut down any existing Oracle database instances with normal or immediate priority. On Oracle RAC systems, shut down all instances on each node.
5.9 Stop All Processes
Stop all listener and other processes running in the Oracle home directory where you want to install the patch set.
5.10 Back Up the System
Oracle recommends that you create a backup of the Oracle9i installation before you install the patch set.
6 Installation Tasks
You can install the patch set either interactively or noninteractively. See one of the following sections for information about how to complete the installation:
To install the patch set interactively, see the "Installing the Patch Set Interactively" section.
To install the patch set noninteractively, see the "Installing the Patch Set Noninteractively" section.
Note:
You must use Oracle Universal Installer release 10.1.0.5 or later to install this patch set.
6.1 Installing the Patch Set Interactively
Note:
If you attempt to install this patch set in an Oracle home directory that does not contain an Oracle9i installation, Oracle Universal 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.8.0
The Oracle Universal Installer does not allow the installation to proceed. Click OK, then click Cancel to end the installation.
The following procedure describes how to install the patch set interactively:
Log in as the Oracle software owner (typically oracle).
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 Oracle Universal Installer, for example, your workstation or PC.
Enter following commands to start Oracle Universal Installer, where patchset_directory is the directory you unpacked the patch set software:
$ patchset_directory/Disk1
$ ./runInstaller
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.
If you are installing the patch set on an Oracle RAC cluster, 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 Oracle Universal Installer, exit Oracle Universal 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.
When prompted, run the $ORACLE_HOME/root.sh script as the root user. If you are applying the patch set to an Oracle RAC installation, then run the root.sh script on each node of the cluster.
On the End of Installation screen, click Exit, then click Yes to exit from Oracle Universal Installer
7.2.1 Check Tablespace Sizes and Set Parameter Values
Review the following sections before upgrading a database.
7.2.1.1 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.
7.2.1.2 Check XDB Tablespace Size
For Oracle RAC installations, ensure that there is at least 50 MB of free space allocated to the XDB tablespace.
7.2.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters
Users who have JVM (Java enabled) or JVM and XDB installed on their 9.2.0.1 databases should make sure that the init.ora parameters SHARED_POOL_SIZE and JAVA_POOL_SIZE are each 150 MB or more before running the catpatch.sql upgrade script. Failure to do so could result in an unrecoverable memory failure while running of the script. Please note that JVM and XML DB was shipped as part of the default 9.2.0.1 seed database, and will be present unless the user explicitly installed a 9.2.0.1 instance without them.
Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters as follows:
Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus /nolog
SQL> CONNECT SYS/SYS_password AS SYSDBA
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
7.2.2 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).
For Oracle RAC installations, 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
Note:
For Oracle RAC installations, start the listener on each node of the cluster.
For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:
$ sqlplus /nolog
SQL> CONNECT SYS/SYS_password AS SYSDBA
For Oracle RAC installations:
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 SYS/SYS_password 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 SYS/SYS_password 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
For Oracle RAC installations:
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> EXIT
$ srvctl start database -d db_name
If you are using the Oracle Recovery Manager catalog, enter the following command:
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
If Oracle Internet Directory release 9.2.0 is installed in the Oracle home, run the following shell script:
Note:
Make sure that the database and database listener are running, and all parameters for the oidpatchca.sh script are specified before running the script.
$ORACLE_HOME/bin/oidpatchca.sh
-connect Connect_String
-lsnrport Listener_Port
-systempwd SYSTEM_Password
-odspwd ODS_Password
-sudn Super-User_DN
-supwd Super-User_Password
-dippwd Password_to_register_DIP_Server
In the preceding example, Password_to_register_DIP_Server must conform to the password policy in the Oracle Internet Directory server.
Note:
If you are using the Oracle OLAP option, then you must run catpatch.sql and utlrp.sql on any additional instance created from your main 9.2.0.8 database. Your catpatch log should show the status of the three OLAP components as follows:
OLAP Analytic Workspace UPGRADED 9.2.0.8.0
Oracle OLAP API UPGRADED 9.2.0.8.0
OLAP Catalog VALID 9.2.0.8.0
================================================================
Regards,
Sabdar Syed.
|
|
|
|
|
|
|
|
|
|
|
|
Goto Forum:
Current Time: Mon Dec 02 15:44:09 CST 2024
|
] 
Blog
Search
Help
Members
Register
Login
Home
