Upgrade Best Practices [message #545534] |
Thu, 01 March 2012 01:39 |
|
nicky_nicky
Messages: 2 Registered: March 2012
|
Junior Member |
|
|
I am planning to upgrade my application from 11i to R12
Database : 10.2.0.4 to 11.2.0.3
Application : 11.5.10.2 to 12.1.3
I need to complete the upgrade with in 48 hrs. Can you please suggest me with best practices to achieve this..
|
|
|
Re: Upgrade Best Practices [message #545540 is a reply to message #545534] |
Thu, 01 March 2012 02:41 |
John Watson
Messages: 8962 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
This is a huge upgrade. The technology stack is very different, but that is the easy part. It is the changes to data structures and the way the modules work and interact that take the time. We have done it with less than 48 hours down time, but it isn't easy. You must budget development time: minimum two months, possibly six. It depends on how complex your environment is, how good your implementation team is, and how your staff react to change. You need commitment from all the users, and from management.
Probably the first step is to determine how to use R12. It has much enhanced functionality. There will be many alerts, workflows, concurrent jobs, reports, and so on that you've developed that are no longer needed. You need to decide what new facilities to enable, what older ones to discard, and what needs to be migrated.
You have to do this upgrade: 11.5.10 installations are becoming almost impossible to maintain. But it isn't easy. Your choice of implementation consultants is critical. Good luck.
|
|
|
|
|
Re: Upgrade Best Practices [message #546507 is a reply to message #545763] |
Wed, 07 March 2012 04:16 |
|
SvenJensen
Messages: 1 Registered: March 2012 Location: Hamburg, Germany
|
Junior Member |
|
|
48hrs are a quite short time.
Did you gone through
Oracle® Applications Upgrade Guide Release 11i to 12.1.1
Oracle E-Business Suite Release 12.1.3 Readme [ID 1080973.1]
In addition this blog have some good points to you should know --> blogs.oracle.com/UPGRADE
and if you have the chance to attend one of Mike's Workshops, Do it!
You should do thorough testing before you could fix a schedule in that time. As John said your hardware has to be able the do so.
You have to go through some test upgrade cycles to have all error, breaks eg worked out, and have fixes and work around for all of them. If there is even one you did not know how to fix it soon, your time will flow away as none.
If ever possible I would opt to do this in two steps.
1st upgrade the database so you are able to be sure all your external interfaces and customizations are working well with 11gR1. This seems to be the part with less errors but just to be sure now errors evolving here could not harm. There are some Notes in MOS to get this done
Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade [ID 761570.1]
This one is a very good source, I would opt for PATH C to go, with using tho option of spliiting it in two parts
Database Initialization Parameters for Oracle Applications Release 12 [ID 396009.1]
Interoperability Notes EBS R12 with Database 11gR2 [ID 1058763.1]
After you are sure that every thing will work fine on RDBMS 11.2.0.3 you could gone on for production upgrade to R12.1.3
In the meantime you should go on for test upgrades of the EBS to work out all the things which could happening there.
And as Jason already told you. You strictly have to got 11.5.10 --> 12.1.1 -> 12.1.3
It is because of R12.1.3 is a patch only go into R12.1.1
And as last comment
Pleas read this very very thorough
Oracle® Applications Upgrade Guide Release 11i to 12.1.1.
And what Ive told about is only the dba thema.
As John said your developers, Key-Users, End-Users, managers. besides the technical upgrade they have to adopt all the new and different things coming with R12.1.3.
Lot of companies are going to get help by consultants to show how to work with R12 as they do not have the resources to do it all for them alone. But if the project gets well stuffed, enought time and so on it could be done in-house.
Regards
Sven
|
|
|
|
|
|
|