user1420455 wrote:So why don't "they" want 11g R2. If you are starting from scratch, why would "they" even consider a release that is already terminal in its life cycle? Before you can address their concerns, you need to know what their concerns are in the first place. Neither you nor we can give answers without knowing what the questions are.
Yeah but here is the issue , My company simply dont want to go for 11g R2 . I have to be sure tht I have good advantages or features then I can go for 11g R2. So can you suggest me some.
ji li wrote:They started deviating from their own rules the moment the App Server people were allowed to choose a number. And it's getting worse now that WebLogic Server is in the mix - WLS for 11g is 10.3.x.
Funny though how Oracle deviated from their own rules when they released the different versions of OMS using the forth digit for the actual release version.
Remember that "in theory" (and I regress), the patchset releases are only error correction code and (should) not introduce any new features. Of course, we all know they do, but they are undocumented and not readily available to use.Again, there is the theory, and the exception : if I'm not wrong the Real Application testing has been introduced (well, backported from 11g) in 10.2.0.4... and is very well documented (sorry, I'm not able to reach the documentation hosted by Oracle doc website to show it).
damorgan wrote:I maybe miss something here.
I must confess a bit of surprise at the advice you have received so far given the sparsity of information you provided.
1. Is this for new development or for upgrading an existing application?What are the answers make it in favor of 11gR1 or 11gR2 ? Would it mean 11gR2 is less capable on some of these features you're pointing out ?
2. What type of usage? OLTP? DSS? DW?
3. What features do you use? RAC? Partitioning?
Decisions such as the one you are asking about are best made from a position of having all of the relevant facts: You didn't tell us anything about what you plan to do with it or even the go-live timeframe.Ok, you certainly right by asking questions, but eventually your posistion is not very different than the ones suggested above, going for 11gR2.
From a pure database standpoint there are not a lot of things in 11gR2 that most people can use immediately. But, certainly, by moving to 11gR2 now you make for a clearer path moving forward. My favorite 11gR2 features are Edition Based Redefinition and Hybrid Columnar Compression. The issue with the later being that you must buy an Exadata. Something I would like to do if I had room for one on my lab. <g>