I need to Upgrade my 10GB oracle database from 126.96.36.199.0 to 188.8.131.52 or the latest one ! best options and procedures most welcome
Just follow the same steps documented in this Oracle white paper.
The upgrade doc lists the requirements for upgrades:
Current Release Upgrade Path
184.108.40.206 (or earlier)
Direct upgrade is not supported. Upgrade to an intermediate Oracle Database release before you can upgrade to the new Oracle Database 11g release, as follows:
- 220.127.116.11 (or earlier) -> 18.104.22.168 -> 10.2.0.4 -> 11.2
When upgrading to an intermediate Oracle Database release, follow the instructions in the intermediate release's documentation. Then, upgrade the intermediate release database to the new Oracle Database 11g release using the instructions in Chapter 3, "Upgrading to the New Release of Oracle Database".
Direct upgrade to the new Oracle Database 11g release is supported from 22.214.171.124 or higher, 10.1.0.5 or higher, 10.2.0.2 or higher, and 126.96.36.199 or higher. Note that Oracle
Your shortest path is to upgrade to 188.8.131.52 so you can then upgrade directly to 11g.
If you have tablespaces that are Dictionary Managed, or Locally Managed that were converted from Dictionary Managed, you may be better off using export/import, depending on how much time you have. 10G isn't really very much, unless of course you don't have that much space (of course, the export is likely to be much smaller). Are you moving to a different machine?
Moved to the Database Upgrade forum. What metric measures "best" ?
Check the links on the Upgrade site (the 11gR2 section) - Oracle Database Upgrade
Moving machines and versions like this is a good time to look for deferred housekeeping. You have to test anyways, so you might watch for basic things like pctfree and over allocated segments. If most of your data is historical, you might consider lowering pctfree for the import, then setting it to what it should be after. A possible downside is if there is implicit data distribution that gets undone by this reorganization of the data. Combined with optimizer changes and hardware and configuration changes, there could be some amount of work figuring out why a few queries go awry. Hard to predict whether that will be more work than just the version change, but you can't know anything without testing anyways. What's important to users perception should control where you spend effort, an argument could be made to just import it all as is, test with a representative load, and see what goes wrong. You may find that simply working through the sql plan management is good enough, see the oracle optimizer blog. https://blogs.oracle.com/optimizer/tags/sql_plan_management