9i 10g manual upgrade

We can upgrade the version as 7. Manual Upgradation : A manual upgrade consists of running SQL scripts and utilities from a command line to upgrade a database to the new Oracle Database 10g release. While a manual upgrade gives us finer control over the upgrade process, it is more susceptible to error if any of the upgrade or pre-upgrade steps are either not followed or are performed out of order. Below are the steps. Install Oracle 10g software : For Upgradation , Invoke the. The above scripts checks a number of areas to make sure the instance is suitable for upgrade including.

The issues indicated by this script should be resolved before a manual upgrade is attempted. Once we have resolved the above warning , then re-run the above script once more to cross-check.

Check for the timestamp with timezone Datatype : The time zone files that are supplied with Oracle Database 10g have been updated from version 1 to version 2 to reflect changes in transition rules for some time zone regions. If the utltzuv2.

After the upgrade, we must update the tables to ensure that the data is stored based on the new rules. Adding and Deleting Cluster Nodes. OLSNodes Command. Oracle Clusterware Summary commands. Proper steps to remove a node from a cluster. RACcheck Command. Removing a Node from an Scan Single Client Access Name commands. VIP Commands. Block recovery.

Recovering Oracle Plan. Restoring a Database to an Alternate Server. RMAN Configurations. RMAN Parameters. Step by step to create Standby Database. Upgrade 9i to 10g. Colored Prompt. Cut - Extract from file. File Search. With Napply itself by providing patch location and specific patch id you can apply only one patch from a collection of extracted patch. For more information check the opatch util NApply —help. It will give you clear picture. What kind of errors usually resolved from them?

Critical Patch Update CPU was the original quarterly patches that were released by oracle to target the specific security fixes in various products.

PSU contain fixes for bugs that contain wrong results, Data Corruption etc but it doe not contain fixes for bugs that that may result in: Dictionary changes, Major Algorithm changes, Architectural changes, Optimizer plan changes. Regular patchset: Please do not confuse between regular patchests and patch set updates PSU. The importance of PSU is minimizing once a regular patchset is released for a given version. So if you have not decided or applied any of the patches then, I will suggest you to go to use PSU patches.

For more details refer: Oracle Products [ID It seems to be theoretically more consecutive approach and can cause less trouble than PSU as it has less code changing in it. Thus any one who is concerned only with security fixes and not functionality fixes, CPU may be good approach. PSU references at 5 th place in the oracle version number which makes it easier to track such as e.

Note: You can find the details from the above query if you already executed the catbundle. Will Patch Application affect System Performance? Sometimes applying certain patch could affect Application performance of SQL statements.

Thus it is recommended to collect a set of performance statistics that can serve as a baseline before we make any major changes like applying a patch to the system. Can you stop applying a patch after applying it to a few nodes? What are the possible issues? Yes, it is possible to stop applying a patch after applying it to a few nodes. There is a prompt that allows you to stop applying the patch. But, Oracle recommends that you do not do this because you cannot apply another patch until the process is restarted and all the nodes are patched or the partially applied patch is rolled back.

When I apply a patchset or an interim patch in RAC, the patch is not propagated to some of my nodes. What do I do in that case? In a RAC environment, the inventory contains a list of nodes associated with an Oracle home. It is important that during the application of a patchset or an interim patch, the inventory is correctly populated with the list of nodes.

If the inventory is not correctly populated with values, the patch is propagated only to some of the nodes in the cluster.

OUI allows you to update the inventory. What do I do? Caution: It is not advisable to apply the patches directly into the production server. The ideal solution is to apply or test the patches in test server before being moved into the production system. Here in this article you will find all those things briefly with an example.

For more details please study the oracle documentation. PSE, one-off or interim patch: This is usually a single fix for single problem. Interim patches are bug fixes given to the customers in critical need and are not cumulative, regressed or versioned. It is applied via opatch. You can use opatch lsinventory command to see which one-off patch are installed on your system.

MRL patch : This type of patch is created by putting several fixes into a single patch. It is also applied using opatch. It is usually applied to upgrade oracle version. For Example if you want to upgrade oracle version from 9. OPatch is a Java-based utility that runs on all supported operating systems and requires installation of the Oracle Universal Installer. A patchset contains a large number of merged patches, is thoroughly tested, changes the version of the product it is applied to, can sometimes introduce new functionality, and should be applied when suitable.

Patchset are usually applied through OUI-based product specific installers. Steps and Process when you need to apply patches:. First, determine the patch you have to apply, if you are applying a patchset e. These are applied in different ways. When you download the patchset, it will be accompanied by a detailed, step-by-step guide for how to apply the patchset.

Step 1: Contact Oracle Support. If Oracle Support is not able to resolve the issue, they may ask to see if you have any patches already installed on your system. To determine this information, you should run the opatch lsinventory command or opatch checkInstalledOneOffs command. It list only the interim patch applied on oracle binaries. You can list patch applied on database with the help of below query in 10g R2.

Upon determining that you are in need of a new patch and it has not already been installed on your system, you should do the above steps: Getting Patches:. Once you obtain the patch, determine the Oracle home directory to which you are going to apply the patch.

This file contains important information and instructions that must be followed prior to applying your patch. After you determine the Oracle home to which you need to apply the patch, you should apply the patch with the opatch apply command. In most cases, after you apply the patch the instructions in the README file will tell you to run the opatch start command to re-start your servers. After the patching is complete and your servers are restarted, you should check your product software to verify that the issue has been resolved.

If for some reason the result is not satisfactory, you can use the opatch rollback command to remove the patch from the Oracle home. Opatch is an interim utility for applying Database interim patches which will fix the bug in the release. For making use of the opatch utility you have to download the opatch recent version and apply as follow: Opatch is very useful for applying the database patches to fix various bugs and it is essential to have the latest version.

We can use winscp or ftp for copying this patch from MOS to windows and than windows to linux Box. Patch sets 3.

Critical patch updates. Patchset updates 5.