Download and Extract the Installation Software
Shut Down Oracle Databases
Shut down any existing Oracle database instances with normal or immediate priority
Stop All Processes
Stop all listener and other processes running in the Oracle home directory where you want to install the patch set. (In case any processes are running during oracle patch installation, oracle raises which processes are running) BACK UP THE SYSTEM Oracle recommends that you create a backup of the Oracle9i installation before you install the patch set. (Complete Oracle Home directory).
Installing the Patch Set Interactively
Click the setup.exe file in download patches.
Name field in the Destination section, select the name of the Oracle home that you want to update from the drop down list and then click next.
Click the Install button.
Upgrade the Instances from Previous Version to Current Version
Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameter
Start the services
connect sys/sys@patch as sysdba
Startup the database
Now ensure the database version
Don’t use the v$version version, its only show the component upgraded, not a database
SQL>SELECT COMP_ID, COMP_NAME, VERSION, STATUS, FROM DBA_REGISTRY;
Determine the current value of parameter
SQL> SHOW PARAMETER SHARED_POOL_SIZE
SQL> SHOW PARAMETER JAVA_POOL_SIZE
Change the size of the following parameter (instance running in spfile)
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE=’150M’ SCOPE=spfile;
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE=’150M’ SCOPE=spfile;
Shut down the database
Upgrade the Database
Start the listener.
LSNRCTL> start listener
Connect sys/sys@patch as sysdba
Startup the database
SQL> Startup Migrate
Run the catpatch.sql script
SQL> SPOOL patch. Log
SQL> SPOOL off
Note: 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.
Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. (Optional but recommended)
After Upgraded the Database if you are using the Oracle Recovery Manager Catalog
RMAN catalog username/password@alias
RMAN> UPGRADE CATALOG;
While trying to install Oracle 9.2 on Suse Linux 10.1 64 bit, but it got hanged after 17% installation, it was showing a message
To overcome this problem, the value for LD_ASSUME_KERNEL should be
RHAS 2.1 2.2.5
RHEL3, RHEL4, OEL4 any value from 2.4.1 to 2.4.19
SLES8, SLES9 2.4.21
RHEL5, OEL5, SLES10 Should not be set
- Testing the Media Management API
- PROC-26: Error while accessing the physical storage ASM error AMDU-00204: AMDU-00201:
- Oracle Database 12c installation steps
- Auto start of Golden Gate after DB server reboots
- Relocating SCAN VIP from one node to another node
- amdu – ASM Metadata Dump Utility
- Backup and Restore of ASM Metadata in Oracle 11gR2 (md_backup and md_restore)
- Deleting an OCR in 11gR2
- Adding an OCR on a separate Diskgroup 11gR2
- ORA-27154: post/wait create failed ORA-27300: OS system dependent operation:semget failed with status: 28
- Oracle DBA Training
- RMAN Backup Architecture (Diagram)