1 person found this helpful
If you have conducted all of your testing on 22.214.171.124, then that is the version you should target for production also. Performing a production upgrade that is different than all of your other upgrades is not recommended
For a production database, it is a must to first test any changes which will be applied on it, so it is not recommended to go directly to 126.96.36.199.
For any technical query or upgrade path, you may refer to below article -
837570.1 - Complete Checklist for Manual Upgrades to 11gR2
If you are going for upgrade, then first you have to choose how do u want to upgrade
1. using dbua
2. using catupgrd script
But in both situations, i would recommend you to first run the preugrade tool to check the prerequisites
In my opinion, either:
- You have an upgrade to 188.8.131.52, which is tested (?) and working. On those test-environments, you can ADD an upgrade from 184.108.40.206 to 220.127.116.11.
But, to know that this one works, you need to have enough time after doing this upgrade and before you start anything on production.
And, the idea is to NOT mix both upgrades, since a combined upgrade is what you've never tested (see below)
- Don't change the 18.104.22.168 upgrade at all, and patch production to 22.214.171.124
- Clone all non-production environments (from production) back to 10g, and run an 126.96.36.199 upgrade on all and each, and allow AT LEAST the same time for testing and debugging on non-production, as you have let the 188.8.131.52 testing being done already.
Other options are dangerous (untested)