Oracle 9.2.0.3.0 patch set for windows - questions

Question

Hi!
I have for that some questions. I have oracle 9.2.0.1.0 on a windows 2003 server running with one local database - no real apllication cluster.
I don't understand which instructions I have to make for oracle upgrade?
Must I also make the 3. instruction? Connect to databse prior and drop?
Must I also make the post install action for my database?
(startup migrate ...)
what means at post install actions the following:
'execute these post install actions only if you have one or more databases associated to the upgraded $oracle_homee.
My database path is e:\oracle\oradata\database my oracle path is e:\oracle\ora92 have I in my case make the post install actions?
Thanks for help!
1. When applying this patchset on Windows NT, XP or Windows 2000, you must log onto the system as a user with Administrative privileges
(e.g. as a user which is a member of the local Administrators group).
2. Unzip the downloaded patch set file into a new directory.
3. Drop the xmlconcat function by running the following commands:
drop public synonym xmlconcat;
drop function xmlconcat;
4. Shut down any existing Oracle Server instances in the ORACLE_HOME to be patched with normal or immediate priority. i.e.: Shutdown all instances (cleanly). Stop the database services, and stop all listener, agent and other Oracle processes running in or against the ORACLE_HOME to be installed into.
5. Perform the following pre-install steps for Real Application Clusters (RAC) enviroments only:
IN ADDITION TO STOPPING ALL ORACLE SERVICES IN THE ORACLE_HOME TO BE UPGRADED:
If you are running in a RAC enviroment, stop the following Windows service(s)/devices(s) using the Net Stop command:
Stop the Windows service named "OracleGSDService"
Stop the Windows service named "OracleCMService9i".
Stop the Windows device named "OraFenceService" (This Device does NOT show up as a Service in the Control Panel).
For Example:
C:\>net stop OracleGSDService
C:\>net stop OracleCMService9i
C:\>net stop OraFenceService
Once the above steps have been performed on all the nodes of the cluster, you should then be able to upgrade the OSD components to the 9.2.0.3 versions. This can be accomplished by...
xcopy all the files in the \Disk1\preinstall_rac\osd\*.* directory to the directory in which the OSD components were originally installed on all nodes(typically %SystemRoot%\system32\osd9i).
Note: You may also be able to look in HKEY_LOCAL_MACHINE\Software\Oracle\OSD9i registry key to determine the directory in which the original OSD components were installed. Now the OSD components can be restarted on all the nodes in the cluster.
C:\>net start OraFenceService
C:\>net start OracleCMService9i
C:\>net start OracleGSDService
After all of the above steps have been completed on all the nodes of the cluster, you are now ready to proceed with the Oracle 9.2.0.3.0 patchset installation.
6. Start the installer:
If the current Installer version is less than 2.2.0.18.0 then download the Installer 2.2.0.18.0 from Oracle Metalink where it can be accessed with the bug number 2878462 and choosing the MS Windows NT/2000 Server platform, then run the setup.exe 2.2.0.18.0 from the C:\Program Files\Oracle\oui\install directory .
7. You may install the Patch Set through either an interactive or a silent installation.
To perform an interactive installation using the Oracle Universal Installer graphical interface:
1. Start the installer from the newly installed OUI 2.2.0.18.0 by running the version of setup.exe located at C:\Program Files\Oracle\oui\install and verify
that the version of the OUI GUI is 2.2.0.18.0 before proceeding.
2. Follow the steps given below within the installer:
1. On the Welcome screen, click the Next button. This will display the File Locations screen.
2. Click the Browse button for the Source... entry field and navigate to the stage directory where you unpacked
the Patch Set tar file.
3. Select the products.jar file. Click the Next button
The products file will be read and the installer will load the product definitions.
The products to be loaded will be displayed (verify ORACLE_HOME setting for this first).
4. Verify the products listed and then click on the Install button.
5. Once the installation has completed successfully, it will display End of Installation. Click on Exit and confirm
to exit the installer.
To perform a silent installation requiring no user intervention:
1. Copy the response file template provided in the response directory where you unpacked the Patch
Set tar file.
2. Edit the values for all fields labeled as "<Value Required>" according to the comments and examples
in the template.
3. From the unzipped patchset installation area, start the installer by running the setup executable passing
as the last argument the full path of the response file template you have edited locally with your own
value of ORACLE_HOME and FROM_LOCATION:
setup.exe -silent -responseFile <full_path_to_your_response_file>
Post Install Actions
Execute these "Post Install Actions" only if you have one or more databases associated to the upgraded $ORACLE_HOME.
Important Notes
1: Java VM and XML DB Requirements
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 during 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.
2: SYSTEM table space
If you have JServer installed in the database, you should check to be sure there is at least 10M of free space in the SYSTEM table space before running these actions.
3: Installing on Cluster Databases
If you are applying this patch set to a cluster database, then set the CLUSTER_DATABASE initialization parameter to false. After the post-install actions are completed, you must set this initialization parameter back to true.
To complete the installation of this patch set, you need to start up each database associated with the upgraded $ORACLE_HOME, start the database listener (e.g., lsnrctl start), login using SQL*Plus (e.g., sqlplus "/ as sysdba"), and run the following commands/scripts in order from $ORACLE_HOME within a MIGRATE session. If you are using the OLAP option, make sure that the database listener is up.
startup migrate
spool patch.log
@rdbms/admin/catpatch.sql
spool off
Review the patch.log file for errors and re-run the catpatch script after correcting any problems
shutdown
startup
This step is optional - it will recompile all invalid PL/SQL packages now rather than when accessed for the first time - you can also use utlrcmp.sql to parallelize this in multiprocessor machines:
@rdbms/admin/utlrp.sql
Execute the following if you use Oracle OLAP option:
alter user olapsys identified by <password> account unlock
connect olapsys/<password>
@cwmlite/admin/cwm2awmd.sql
exit
Execute the following script only if you have version 9.2.0.1.0 of Oracle Internet Directory installed in your ORACLE_HOME. Make sure that the database and database listener are running and that all parameters are specified prior to running the script:
$ORACLE_HOME/bin/oidpatchca.bat
-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>
Where:
connect - Database connect string
lsnrport - Database Listener port
systempwd - Password of the database 'SYSTEM' user
odspwd - Password of the database 'ODS' user
sudn - Super-user DN
supwd - Super-user Password
dippwd - New password to register Directory Integration Server. This password must conform to the password policy in the OID server
Execute the following steps only is you are using the RMAN catalog.:
rman catalog <user/passwd@alias>
upgrade catalog;
upgrade catalog;

Answer 1

I don't understand which instructions I have to make for oracle upgrade?
-- You have to follow all the instructions mentioned
(Just check for few if's for Cluster enabled, OID and OLAP databases. Perform these steps only if they apply)
Must I also make the 3. instruction? Connect to databse prior and drop?
-- Yes you should do
Must I also make the post install action for my database?
(startup migrate ...)
-- Yes. Do run catpatch.sql .
what means at post install actions the following:
'execute these post install actions only if you have one or more databases associated to the upgraded $oracle_homee.
-- In this step make sure you do step 1
1: Java VM and XML DB Requirements
Otherwise catpatch.sql will fail.
Do 2 and 3 only if applicable
Chandar
My database path is e:\oracle\oradata\database my oracle path is e:\oracle\ora92 have I in my case make the post install actions?