Skip to main content

Apply patches on 9.2.0.1.0 to upgrade 9.2.0.7.0

Apply patches on 9.2.0.1.0 to upgrade 9.2.0.7.0

The Oracle 9.2.0.7 patchset is available from Oracle's Metalink Web site. To register for Metalink, you will need a valid Support Identifier (CSI). CSI numbers are unique support identifiers given to each customer with a current support contract. When you download the patchset from Metalink, it will be accompanied by a detailed, step-by-step guide for how to apply the patchset.
The basic steps for applying the Oracle 9.2.0.7.0 patchset are:
§               Download the patch from Metalink.
§               Unzip it on the database server.
§               Shut down all databases using the Oracle9i home.
§               Apply the patchset to the Oracle binaries.
§               Start up all databases using the Oracle9i home and run required SQL scripts within each database.
Patch set release 9.2.0.7 includes all fixes in patch set 9.2.0.7 and earlier as well as new fixes for patch set 9.2.0.7. This you can apply this patch set to any earlier release 9.2 installations. You do not have to install intermediate patch sets.
Patch sets contain generic fixes that apply to all platforms. Patch sets may also include additional platform-specific patches.
Note: Oracle provides both 32-bit and 64-bit versions of Oracle9i for Windows. Currently, the 32-bit version of the patch set must only be installed on the 32-bit version of the database. The 64-bit version of the patch set must only be installed on the 64-bit version of the database.

Users applying this patch set must use Oracle Universal Installer release 10.1.0.4 (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.4 is also installed when you install this patch set.
There are two documents oracle 9i release 2 patchset. Both of these documents are included with the patchset.
1.      Oracle9i Patch Set Notes, Release 2 (9.2.0.7) Patch Set 6 for Microsoft Windows (32-bit)
2.      Oracle9i List of Bugs Fixed, Release 2 (9.2.0.7) Patch Set 6
This document provides:
§         System requirements and information about how to install or reinstall the patch set
§         A list of all bugs fixed to date that are specific to Oracle9i release 2 for Microsoft Windows (32-bit)
§         A list of known issues relating to Oracle9i release 2 for Microsoft Windows (32-bit)
The following are the system requirements for this patch set:
System Architecture: Intel Pentium and AMD processors
Operating System:
§         Windows Server 2003
§         Windows 2000 (Service Pack 2 or higher)
§         Windows XP Professional
Note: Windows 98 and Windows NT are no longer supported.
Oracle9i release 2 (9.2.0.1.0) or later


For more details about pre-installation and post-installation task do not forget to read the README for 4163445 - Release 2 (9.2.0.7) Patch Set 6 for Microsoft Windows (32-Bit).

Upgrading Oracle database from 9.2.0.1.0 to 9.2.0.7.0 on Windows server 32 bit.
Step1: Backup your database for precaution.
Step2: check your current database name and version.
SQL>Select database_name from v$database;
Sadhan.world
SQL> select * from v$version;
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
PL/SQL Release 9.2.0.1.0 - Production
CORE     9.2.0.1.0  Production
TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
NLSRTL Version 9.2.0.1.0 - Production


Step 3: Login to you’re MY ORACLE SUPPORT 
https://support.oracle.com/CSP/ui/flash.html
and Click on PATCHES & UPDATES for downloading your patch for windows 32 bit.
In PATCHES & UPDATES enter Patch Number 4163445.


Step 4: Search and Download this patch on the disk drive and its associated Read me too.
p4163445_92070_WINNT.zip and unzip it somewhere else (For Example: D:\patch) outside actual ORACLE_HOME.




Note: You must Read the Associated Read and Patchset notes before applying actual process.
Step 5: Shutdown your database
SQL>shutdown immediate;
Step 6: Stop all the services and Listener.
You can do it either from the command prompt (C:\oracle1\net strop, C:\oracle1\lsnrctl stop) and type services.msc on RUN and Stop it by right click on the required services.
OracleServiceyourSADHAN
OracleOraHome92TNSListener
OracleOraHome92Agent
OracleOraHome92ManagementServer (asks for credentials - use sysman/oem_temp)
OracleOraHome92HTTPServer





Step 7: Launch your patch setup.
From your drive location where patch downloaded Clicking on the Setup.exe (D:\patch\Disk1\Setup.exe). Before upgrading the database you must check Tablespace size and set parameter values if required.
This start the OUI  (Newer Version of OUI). The Welcome screen will appear. Then Click NEXT.

Enter the OraHome92 into the name field and this will update the path to your ORACLE_HOME. Then Click NEXT. If any services are still running you will see this message:

Stop the services (if any) and Retry.

Click "Install" and wait for End of installation.

Step 8: After installation of patch set you must perform the following task:
i. Start all the services and listener
Use the same concept shown on the above screenshot just by clicking on start
ii.  Upgrade your dictionary.
Run SQL*Plus as SYS, Restart the database and run the upgrade script. It will take approx. 30 Min.
SQL> SHUTDOWN ABORT;
SQL> STARTUP;
SQL> SHUTDOWN IMMEDIATE;
SQL> STARTUP MIGRATE
SQL> spool d:\patch.log
SQL>@D:\Oracle\ora92\rdbms\admin\catpatch.sql
SQL> SPOOL off;
This script provides a direct upgrade path from this release (9.2.0.1.0) to the new release (9.2.0.7.0). Review patch.log for any errors (if any)
Note: OR you can run the catupgrd.sql script from ORACLE_HOME/rdbms/admin path. For that you have to start your database using STARTUP UPGRADE.
iii.  Restart your database for change to take effect:
SQL> SHUTDOWN;
SQL> STARTUP;
iv.  Compile Invalid Objects & Verify Database version.
Run the utlrp.sql script to recompile all invalid PL/SQL packages.
SQL> @ D:\Oracle\ora92\rdbms\admin\utlrp.sql 
SQL>Select database_name from v$database;
Sadhan.world
SQL> select * from v$version;
Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
PL/SQL Release 9.2.0.7.0 - Production
CORE     9.2.0.7.0  Production
TNS for 32-bit Windows: Version 9.2.0.7.0 - Production
NLSRTL Version 9.2.0.7.0 – Production


If you find to get the details which patchset your database, then simply query with the DBA_registry.
SQL>Select comp_id, comp_name, version, modified from dba_registry;
If you applied all of the above post installation task then finally you will get the result of above query as:
COMP_NAME                           STATUS      VERSION
----------------------------------- ----------- ----------
Oracle9i Catalog Views              VALID       9.2.0.7.0
Oracle9i Packages and Types         VALID       9.2.0.7.0
Oracle Workspace Manager            VALID       9.2.0.1.0
JServer JAVA Virtual Machine        VALID       9.2.0.7.0
Oracle XDK for Java                 VALID       9.2.0.9.0
Oracle9i Java Packages              VALID       9.2.0.7.0
Oracle interMedia                   VALID       9.2.0.7.0
Spatial                             VALID       9.2.0.7.0
Oracle Text                         VALID       9.2.0.7.0
Oracle XML Database                 VALID       9.2.0.7.0
Oracle Ultra Search                 VALID       9.2.0.7.0
Oracle Data Mining                  VALID       9.2.0.7.0
OLAP Analytic Workspace             UPGRADED    9.2.0.7.0
Oracle OLAP API                     UPGRADED    9.2.0.7.0
OLAP Catalog                        VALID       9.2.0.7.0

In fact upgrading is not difficult and is nothing more than following a series of stepsmentioned in README documentation. 
I hope it will help you all.......


Comments

Popular posts from this blog

Tablespace Management using Toad

You can view all of your tablespace information using toad tablespace screen from Database –> Administer –> Tablespaces Here each table describes different detailed information across all the tablespaces in database. If you open this screen from the toad DBA module then you are also able to see the “space history” and “IO history” tab along with Files, Free space, object, Fragmentation. With these tab you are able to able perform space monitoring and planning steps. These tab permits you check graphically space and IO usage over time. Through this way DBA are also able to estimate ‘Object size’ based on this estimation. From the below “alter tablespace” tab you can §          Modify the tablespace and datafile size. §          Add new datafile to the tablespace.

Import Excel Data into Oracle using Oracle form Button

Import Excel Data into Oracle using Oracle form Button 1. Create a button on the form with the name "IMPORT_EXCEL" and write a pl/sql on "WHEN BUTTON PRESSED" trigger. BEGIN IF :System.Cursor_Block<>'GL_DAILY_COMPOUND_HEADER' THEN   Go_Item('GL_DAILY_COMPOUND_HEADER.V_DATE'); END IF; IF :System.Mode = 'NORMAL' AND :System.Record_Status IN ('NEW','INSERT') THEN   IMPORT_EXCEL_PROC;   ---Form procedure ELSE  MESSAGE('Import allowed only for new entry!!!');  MESSAGE('Import allowed only for new entry!!!'); END IF; END; 2. Now write the procedure "IMPORT_EXCEL_PROC" into the program unit. Don't forget to create required table and folder for procedure IMPORT_EXCEL_PROC PROCEDURE IMPORT_EXCEL_PROC IS application    OLE2.Obj_Type; workbooks      OLE2.Obj_Type; workbook       OLE2.Obj_Type; worksheets      OLE2.Obj_Type; worksheet       OLE2.Obj_Type; ce...

Changing National Character Set AL16UTF16 to UTF8

Changing National Character Set AL16UTF16 to UTF8 The national character set is used for data that is stored in table columns of the types NCHAR, NVARCHAR2, and NCLOB.  In contrast, the database character set is used for data stored in table columns of the types CHAR, VARCHAR2 and CLOB. Like the database character set, the national character set is defined when the database is initially created and can usually no longer be changed, at least not easily or without involving quite a lot of work (export, recreate database, import). Except when creating the database, where the national character set is defined explicitly, it can change implicitly even when upgrading the database from Oracle8i to Oracle9i (or Oracle10g). You require SYSDBA authorization to change the national character set. Changing the national character set means changing an Oracle Dictionary entry, but no data is changed.  $sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> Select property_...