Monday, May 10, 2010

Collaborate 10 OAUG Upgrade SIG Meeting by Barbara Matthews

The OAUG Upgrade SIG hosted a meeting at Collaborate 10 to discuss upgrade issues from E-Business Suite Release 11i to Release 12.

The Panel

- John Stouffer, Independent Consultant, Past Chair of the Upgrade SIG, Moderator
- Lester Gutierrez, Oracle EBS Performance Group, works on upgrades and reducing downtime
- Udayn Parvate, EBS Release Management Team, works on building and packaging the E-Business Suite software. Udayn performs installation and upgrade activities, defines and enforces standards for packaging and delivery with development teams. He works to get upgrade issues resolved so E-Business Suite customers' experience is as smooth as possible.
- Sandra Vucinic, Vlad Group, Inc., Chair of the Upgrade SIG
- Floyd Teter, Jet Propulsion Labs, functional guy on the panel
- Steven Chan, Director, Applications Technology Integration, Oracle Corporation
- Michael Rulf, Executive Director - Product Development, AT&T Hosting and Application Services (H&AS)

The Questions and Answers

We are going to upgrade from Release 11.0.3 to Release 12. We are currently running on Sun Solaris and will switch to a Linux Intel environment. Our architecture team is wondering how to do performance load simulation so we know how much hardware we need to buy to run the upgraded E-Business Suite environment. Our database is 700 gigabytes, and we have 2500 users.

- First, you need to get a sense of how many concurrent users you have, and what those users are doing. While you may have a total of 2500 users, those users probably aren't all logged on at the same time, and they likely aren't submitting data and hitting commit at the same time. The limits will not be software, but will be hardware limitations based on the degree of throughput, and read and write operations per second. The architecture team needs to understand the product mix (modules), the read/write workload, and the concurrent manager workload, and then bring in the hardware vendor to help build out a test environment. You can also use load simulation software like Mercury Interactive. Oracle has a Test Starter Kit (see for E-Business Suite Release 12.1.1 that can be helpful, but you need to choose carefully when you put together your test environment.

- As you purchase your hardware, make sure you are positioned to be scalable, so you have room to grow if you need to. You might find, for example, that when you do the first close on the new system, you need to add more hardware to deal with the extra load. If you can move to parallel concurrent processing, you can add another node easily. Given the size of your environment, you should research and understand the options available for using load balancing and shared appl tiers (see Parallel Concurrent Processing Failover and Load Balancing of E-Business Suite Release 11i and Release 12 by Mike Swing at TruTek).

- As far as hardware is concerned, we are starting to see where the Intel world is supporting more processor cores, and the hardware is hot pluggable. Be careful not to skimp on the chassis, but populate it with the number of processors you want. We're about to see a big jump in the industry from 4 core to 8 core. You should try to pick a hardware solution that allows you to make that move if you need to. Note that there's a tradeoff to buying more processing power than you need - if you overload your processor, your software fees will go up, so you have to strike a balance.

We upgraded to release 12.0.4 and saw a 25-30% increase in database size. Is there a similar increase with the 12.0.4 to 12.1.2 upgrade?

TCA, SLA, and E-Business Tax added a lot to the database size, but you've already bit the bullet on those modules, so no, you shouldn't see a significant increase.

We are currently running Release Is there a recommended upgrade path?

You should upgrade to RDBMS Version 11gR2 and then Release 12.1.1, and then apply the 12.1.2 RUP. We've "borrowed" a wonderful diagram from Steven Chan's blog of what your E-Business Suite Upgrade Roadmap is:

Is there a plan to offer a gui screen for the Mobile Supply Chain module? Currently it uses a telnet session.

It is a high priority with the User Experience team, but we aren't sure when it will be released. The Release 11.5.10 gui version, according to someone in the audience, was too slow, so it wasn't adopted by many users.

Do people typically upgrade or reimplement?

Upgrading is less expensive, and much better supported by Oracle. Because of the nature of reimplementations, the path isn't as clear because we all have different reasons for doing it. It is much more difficult to determine what post upgrade patches to apply, and how to do validation testing. Reimplementation customers will have to blaze their own trail.

Is bifurcation still recommended?

For Release 12, the new term is Upgrade by Request. Upgrade by Request allows you to upgrade part of your data during the upgrade, and then upgrade the rest of your data after your upgrade completes. Modules that can use Upgrade by Request include Financials and Procurement, projects, Supply Chain Management, and CRM. You can read more about Upgrade by Request in Appendix G of the Release 12 Upgrade Manual.

Are there any recommendations for preparing for a Release upgrade to Release 12.1.2?

- See Sandra Vucinic's presentation, Get Ready for EBS Release 12.1! Tasks to Complete Now to Ease R12.1 Upgrade Process. Here's a list of tasks from her presentation:

- Upgrade database to 11gR1 or 11gR2
- Convert tablespaces to OATM model
- Evaluate impact of R12.1 on customizations and extensions
- Introduce BI (XML) Publisher and JDeveloper
- Introduce Web ADI and Report Manager
- Archive and purge EBS 11i data
- Convert from JInitiator to Native Sun JRE - _21 is recommended
- Integrate Discoverer Server Release 10g with EBS 11i - use Discoverer 11g if possible as Discoverer 10g is desupported at the end of 2010
- Configure Oracle iAS Release 10g for external apps (SSO, OID, Portal) and integrate with EBS 11i
- Position for high availability and scalability
- Evaluate and complete platform change based on ROI

- RDBMS 11gR2 is a major architectural change in the nature of the cluster software. DBAs need time to understand the fairly steep learning curve. The many new features may help justify doing the database upgrade separately from the E-Business Suite upgrade so DBAs can come up to speed on the technology.

- In terms of testing, have you catalogued all of your customizations? How are you going to train your user community? What tool will you use to develop training guides?

- Read the 11gR2 Upgrade Companion, and be sure to stay current throughout your upgrade on new patches. There's already a RDBMS Version patch which fixes a lot of issues.

A user related his story of upgrading from Release to Release 12.1.2. During the upgrade the patch stuck on a program, they waited a day, and got a pre-upgrade patch that needed to be applied before starting the upgrade. He noted how frustrating this was, and asked if there is any My Oracle Support note that tells all performance and serious functional issues in the upgrade.

The official My Oracle Support documents are the Release 12 Upgrade Guide, the Release Notes, and the NLS Release Notes. When Oracle encounters issues, they update the Release Notes. They may also release additional patches, including Critical Update Patches (CUP), which include a consolidation of fixes. Users must actively monitor My Oracle Support for additional patches and alerts while upgrading. Another option is to look at the Release 12 Forum, a very active, live, real time forum. Often solutions can be found there before logging a problem in My Oracle Support. Check out the forum at:

How close are we to desupport on Release

Premier Support ends at the end of November, 2010. The extra cost for Extended Support is waived until November, 2011. Extended Support ends in November 2013. Premier support is what you have today, and includes certifications with Oracle products and other products. If a new MS Windows client is released, with Premium Support, Oracle will certify to that. Extended Support, however, will not include third party certifications, so if a new service pack for Windows 7 is released after November, 2010, Oracle is not bound to certify to that service pack. Odds are, they'll give it a try, but they are not likely to produce new patches. The emphasis at Oracle once Extended Support kicks in for Release will be on Release 12.

This point is very important - E-Business Suite customers use a variety of other products besides the E-Business Suite on their computers. Once Extended Support starts, customers may find themselves needing to upgrade because of some other product that they use, but unable to do so because of certification issues with Windows or JRE or other products.

When you move to R12, JInitiator is not certified and won't work on Windows 7 or Vista. You will need to migrate to the native SUN JRE client. Don't have to worry about java conflicts between applications.

I am new to an organization that uses grants, contracts, and projects. In the past, these were considered outliers that kept us from going to the latest release. Will these modules impact our ability to go to Release 12?

Panel members pointed to several companies using those modules who are upgrading, and said they have not hit any big issues.

An audience member said that she had put together a plan for her company based on what she has heard at the conference and wanted to make sure they were heading in the right direction. They are running RDBMS Version with Release, they are already on JRE, they have Discoverer and ADI/GL already implemented with the web, and are moving to RDBMS 11g using OATM with a 2 node shared $APPL_TOP and the latest Release 12 (currently 12.1.2). Is that where her company should be heading?

The panel agreed, her approach is correct.

What features of RDBMS Version 11gR2 would be useful to the E-Business Suite Applications?

You can save a baseline of your production RDBMS 10g performance, and 11gR2 will tell you that your current execution plan is fine, or that you need to run a different plan. You won't lose any performance by going to 11g. This feature is built into 11g. If you run into a performance problem, you can fall back to the 10g plan to get immediate relief while working with Oracle Support to get a more permanent fix.


All in all, it was a fun meeting with lots of questions and interesting answers. As one might expect, the OAUG Upgrade SIG strongly urges you, if you haven't done so already, to get ready to upgrade to Release 12. There are exciting features in RDBMS 11gR2 that will benefit the E-Business Suite Applications even if you don't upgrade to Release 12. The path to upgrading is well-laid out and tested, and the software is now very stable. If you have questions about the upgrade, feel free to contact the OAUG Upgrade SIG. Just drop a note to barb at oncalldba dot com

Collaborate 10 OAUG Database SIG Meeting by Barbara Matthews

The OAUG Database SIG held a lively meeting at Collaborate 10 in Las Vegas. Steven Chan, Senior Director in Oracle's Applications Technology Group, spoke at length about the nuances of Oracle's Lifetime Support policy. You can (and should!) read the details about Lifetime Support at

Understanding just what is included with Extended Support and Sustaining Support, and at what price, is important for customers to understand. You can also sign up for My Oracle Support notifications to receive automatic emails when the LSDs (Lifetime Support Documents) change.

Steven explained that E-Business Suite Release 11.5.10 Premier Support lasts six years from November 2004. That means that at the end of November, 2010 - that's right, this year - Premium Support ends. To stay supported on Release 11.5.10 after that, you'll have to pay a premium on support costs to run in "Extended Support". Steven strongly recommended not running in production in Extended Support unless you really need to. He described Extended Support as a dangerous place to be.

And here's where the nuances come in. With Extended Support, you can still log a P1 problem - but there's no guarantee that the resolution will come quickly - it might take months. Even within Premium Support, Oracle supports only the current and previous database releases for 12 months after the current database has been released. That's a subtle point that could cause big issues for customers - if you are running RDBMS, you're supported for only 1 year now that 11gR2 is available. If you are running RDBMS, thinking you are supported based on what you read on the support page, you aren't - that support stopped in February, 2009. These policies override the E-Business Suite support agreements.

One technical issue brought up at the meeting concerned Sun JRE. Sun JRE is required on Windows desktops for users to access the Applications. Up until JRE 1.6.0_17, the software worked fine. However, Sun introduced changes that broke session management and ordering with JRE 1.6.0_18. The recommendation at the meeting was that if you were still on JRE 1.6.0_17, you should not apply versions 18, 19 or 20, because they all have significant issues for E-Business Suite users. With automatic updates on PCs, you can imagine the issues that this might cause. Also, certain customers, particularly government customers, are required to stay current, so those customers had no choice but to upgrade to the latest version of JRE, even though it had these two major bugs.

Now add one more point - JRE 1.6.0_20 was released to correct a significant security issue that occurred between JRE 1.6.0_17 and JRE 1.6.0_20, which means that if you're on JRE 1.6.0_17, you're ok, but if you are on JRE 1.6.0_18 or JRE 1.6.0_19, you need JRE 1.6.0_21. For military organizations that are required to stay within a certain number of releases of the most current, they may have no choice but to upgrade. Steven commented that while this issue was going on, there really was no reassuring place for an E-Business Suite administrator to be right now.

Mark Farnham suggested that if you're a non-DOD compliant organization with pretty good campus-wide security, and you're a low enough target value, then you can wait for JRE 1.6.0_21, which is expected shortly. The PCI (credit card) industry has a similar issue to military organizations. They have to apply all vendor security patches within 30 days of their release. The good news, according to Mark, is that the really mercenary hackers aren't interested in most organizations.

The recommendation, therefore, is that as soon as a release becomes available that doesn't have the functionality issues, all E-Business Suite users should seriously consider moving to that release. You can read more about this issue on Steven Chan's blog at:

Another issue with versions comes with third party vendors. If third party vendors don't stay current on JRE versions, then users may find themselves working with releases that have bugs or security issues. Agile and Siebel were two examples of vendors with this issue. Steven said that the only thing customers can do in this case is apply pressure on the third party vendors. The advantage of staying current with JRE, for example, is that each new release brings new memory management capabilities, better security, and bug fixes, so, with the exception of the temporary issues with JRE 1.6.0_18 - 1.6.0_20, staying current is the way to go.

Yet another example of the need to understand the nuances of Oracle support agreements lies with the 9i Application Server used with Release 11i and the 10g Application Server used with Release 12 applications. The double edge to that sword is that Application Server 10g has its own application lifecycle, and the Application Server 10g obsolescence life cycle overrides the E-Business Suite life cycle.

One of the questions from the group was what Oracle is doing to make this situation better. Steven said that Oracle is testing better and more, taking more time to test and running more tests. Now that Sun is integrated with Oracle, there's a better chance of working better together. The Oracle team now gets early shipments of Application 10g Patchset 3, and similarly will get early builds of JRE releases at some point.

One very strong point that Steven highlighted is that Oracle can only go so far in their testing. He strongly recommended that if you are testing a combination of software that isn't documented by Oracle, then it is your job to test heavily, as there are too many possible combinations for Oracle to test.

Randy Giefer, from Solution Beacon, asked if Sun Java might merge into Oracle's CPU cycle. Steven said that while this was a nice idea, he wasn't sure it would ever happen, as we can't really afford to wait for up to 3 months for new changes. He also said that the JRE crowd marches to a different beat because of military requirements.

Also covered in this meeting was the need to stay current with Oracle's quarterly CPUs (Critical Patch Updates). Oracle has improved their CPU process by making the CPUs cumulative as of January 2010 for the Applications users. Where in the past, if you wanted to patch current you would have had to apply each CPU, now when you apply the latest CPU - currently the April 2010 CPU - you're set and don't need to apply any others until the next cumulative quarterly CPU comes out in July 2010.

One additional recommendation discussed was the need to periodically review your company's Master License Agreement. Customers need to be aware that the Oracle Account Manager can't authorize anything that flies contrary to the Master License Agreement. An example - implementing custom objects can eliminate a customer's ability to run using a runtime license. One subtlety, however, is that if Oracle directions say that you have to create an object (there are instructions, for example, that tell you to create custom indices for some of your GL objects), then you are ok and are not violating your E-Business Suite license.

Customers have run into similar issues with partitioning. If you are a licensed EBS customer and Oracle introduces a new product requirement, they can't force you to buy a new license. This caveat is driven by mandatory upgrades of the E-Business Suite that would otherwise have forced you to upgrade the technology. On a new license, for example, customers have to buy the partitioning option when licensing the database, because the E-Business Suite uses partitioning. Customers that upgrade, however, don't have to buy the partitioning software as long as they don't partition any data themselves.

Steven mentioned one area with exciting upcoming changes - for those customers who have considered Active Data Guard to create a mirror of an E-Business Suite database for hardware or software failure, it would be really valuable to be able to use that database for reporting. Currently, the database simply sits, unused, unless a failure occurs.

For Active Data Guard to work, you would have to break the mirror to query against the database, but Steven said that Oracle is working on a series of patches that would allow you to run reads against the real-time copy of the database. This functionality will be included with Version 11gR2, and there may be a port for 11gR1. The one catch is that not all reports will work in this environment. Steven asked that if anyone had E-Business Suite reports (provided by Oracle, not custom reports written by customers!) that they would especially like to be able to run on Active Data Guard, that they should send Steven a note with a list of those reports so that he could ensure that they were tested.

That said, we leave you with two pieces of valuable information - first, Steven's blog,, and second, his email, steven dot chan at oracle dot com.

An Inquiring Mind Wants to Know (More About Reimplementing vs Upgrading) by Barbara Matthews

At the end of the Reimplement vs. Upgrade Panel at Collaborate 10, someone asked the panel ”Do third party products that claim to fix the issues that might make you decide to reimplement actually work?” The issues include changing the chart of accounts, calendar, and organization structures, or consolidating multiple instances to a single global instance with a shared service center.

The question went unanswered, because no one on the panel had firsthand experience. Since Floyd Teter said “Reimplementing is like getting a root canal without anesthetic in the lobby of the IRS while you're waiting for the audit,” and others on the panel agreed, I decided to do a little digging around. If you can avoid reimplementing the full E-Business Suite and migrating your 11i data, based on everything that was said by the panel, then it would be worthwhile to do so.

So I searched for a software vendor and came across eprentise. I started with Skip Straus , an ex-Oracle Consulting Practice Manager and now an eprentise salesman, and asked him lots of questions. Then I read a paper that he wrote called Why Reimplement? I really wanted to attend the eprentise presentations at Collaborate on global instance consolidation and upgrade vs. reimplement, but that didn't work out. I spoke to Skip again over the phone, asked more questions, and finished up by looking at the eprentise website.

I also asked around to see if my consulting colleagues had any opinions.

The biggest concern raised by consultants was whether Oracle would support a customer that used eprentise transformation software to change Oracle EBS’s "implementation-time configurations." According to Skip, Oracle does not support third party tools, nor does it support the conversion scripts that you would write yourself to extract and transform the data. The assorted eprentise solutions change the data content or format (such as numeric to alpha), but not the database structure. The result is consistent and correct. He said that eprentise has lots of customers who have made the move, and they haven't had any customer report that Oracle wouldn't support them. The eprentise software changes and converts the data; the company supports the conversion and will address any issues. That does not violate any Oracle support agreement.

Also, if you're going to reimplement because your data is bad, your choice is to clean up your data anyway, or abandon it since it’s untrustworthy. If you are reimplementing because you want to change your chart of accounts, well, you'll still be changing your chart of accounts as part of the reimplementation. So it would seem like fixing the data over on your Release 11i side, making the changes to base setups in the E-Business Suite that are not easily changed, would be a good way to go. I also like the idea of changing your data first, and upgrading second, rather than trying to do both at the same time as part of a reimplementation.

Migrating all your data manually seems like a painful way to go rather than using Oracle's well-tested upgrade path. I understand the panelists who said it would take a lot more time and money to reimplement and migrate your data.

I'll leave you with these questions:

1) If you've used a third party vendor's software to avoid reimplementing, whose product did you use?
2) Did it work?
3) Were the tools easy to use?
4) Would you recommend this path to others?
5) Do you have any caveats?
6) Did you run into any issues with Oracle Support?

Drop me a line at, as I'd love to hear more about this.

Collaborate 10 Release 12 Reimplement vs. Upgrade Panel by Barbara Matthews

The Panel

Panel members included Sandra Vucinic, Vlad Group, Inc., John Stouffer, Independent Consultant, Floyd Teter, JPL, Stephen Horgan, Oracle Corporation, Kyle Harris, Oracle Corporation, Mike Swing, TruTek, and Alyssa Johnson, Solution Beacon.

The Questions and Answers

What are the main decision points for upgrading versus reimplementing?

- If you are thinking of changing your accounting structure, you may have to reimplement. Reimplementing can offer a good opportunity to make changes to the accounting setup manager, subledger accounting, and the chart of accounts, and implement additional ledgers. Other reasons that might drive a reimplementation include if there is significant bad data in the existing environment, if the customer has lost their customization history, or company wide consolidations, mergers and acquisitions.

- The biggest issue with reimplementing is money. When you upgrade, you can expect to spend 20-25% of your original implementation costs. Reimplementation costs go way up; close to the original implementation costs. Floyd Teter suggested that if you can squeeze by with an upgrade, do the upgrade. If something dramatic has changed with the way you model your business, then reimplement. Floyd said that reimplementing versus upgrading was strictly a cost/benefit tradeoff.

Do reimplementations take longer than upgrades?

- Floyd said that reimplementation is always going to take longer. He suggested tacking on 40% to the schedule in terms of effort, but it could be even more, depending on your implementation.

- If you haven't archived or purged your data in a very long time, and have a lot of historical data, how does that drive the implement versus upgrade decision? Can you update selected data?

- You should archive as much data as you can before your upgrade process starts.

- You can also bring over only the data you want, and use your Release 11i instance to reference historical data.

- You can use Oracle's Upgrade by Request process to pick and choose how much data to bring over. Oracle provides a lot of flexibility, but you have to time it and make sure it makes sense. With SLA there is a pre-upgrade patch that lets you control how much of the data you upgrade. If you have 10 million debits and credits, they will all get updated, but you can use Upgrade by Request to update some now and the rest later. You can upgrade the last fiscal year of your data, and it will ensure you have at least 6 months worth of data when you go live.

Are there any lessons learned from upgrading?

- The technological architecture changes, along with E-Business Tax, SLA and TCA caused a big increase in size with Release 12. TCA alone went from 30 tables to 300. You should expect to need an additional 20-25% of disk space for Release 12.

- With the original upgrade to Release 12, AP changed considerably and there were a number of functionality issues that came up. AP is in much better shape since Release 12.0.4, although 12.0.6, the most current release, is also the terminal release for 12.0.x. Performance has improved and there are less errors. Oracle has a proactive information center on My Oracle Support that has information about AP. In many cases, you can find solutions without even logging an SR. AP in Release 12.1.2 is as stable as the other subledger modules.

How does customization impact the decision to reimplement or upgrade?

The consensus was that customization impacts need to be dealt with for both reimplementing and upgrading, and that customizations shouldn't have more impact on one method over another. For both reimplementing and upgrading, customers should consider the following:

- No matter what you decide, those customizations are in your business now because they serve a purpose and are addressing business needs. From that point of view, you need to decide whether the business process gap is still there or not. You need to figure this out whether you plan to upgrade or reimplement. The good news is that sometimes customers have been able to eliminate customizations thanks to new features in Release 12.

- You should catalog your customizations. You should know why you put those customizations in and map it to Release 12 functionality to see which customizations you can retire, and then retire what you can. By doing this groundwork, your upgrade or reimplementation will be that much easier.

- Oracle Consulting offers in its Advanced Customer Services a CEMLI Catalog Service that provides an inventory of your CEMLIs (Configuration/Customization, Extension, Modification, Localization, and Integration). These are scripts, and don't appear to be generally available except through Oracle Consulting. But they sounded like they would be quite handy. You can read more about them at - They are available as part of a "free" Oracle Insight engagement.

The Gorilla in the Room: We're thinking about reimplementing next year. Should we do that or wait for the Fusion Applications?

These were the pearls of wisdom from our experts:

Sandra - Consider Release 12 as a milestone in your journey. It is stable. There are live customers on it. It is a known animal. Doing nothing leaves you with less options. R12 is your milestone to get to Fusion. A lot of great business functionality is available now. With desupport for Release 11i coming in December, 2010, you need to get to Release 12, rather than wait for Fusion.

Mike Swing - If you wait to upgrade to R12, you are putting your production system at risk of being forced to upgrade in a hurry to resolve an issue that can't be resolved in R11i.

Alyssa - Don't wait, you won't regret it.

Floyd - Reimplementing is like getting a root canal without anesthetic in the lobby of the IRS while you're waiting for the audit. Upgrading is always the better choice if you can.

Kyle Harris, from Oracle, pointed out that you may not have a path from Release 11i directly to Fusion. Floyd explained that there's no guarantee that Oracle will offer a direct path from Release 11.5.10 to Fusion 2 or 3. The current direct path offering is for Release to Fusion 1. So if you think you're going to sit on Release 11.5.10 and wait for a fully functional Fusion Application, don't. 80% of E-Business Suite Release 11.5.10 customers are probably not good candidates for Fusion Release 1. Fusion Release 1 will not include manufacturing, for example.

Stephen - Oracle Support will support the upgrade and not the reimplementation. Customers need to really make sure they can't upgrade before considering reimplementation. This point was made at other conference presentations as well - Oracle has limited resources for testing and must focus on what the vast majority of customers will be doing, which is upgrading. Reimplementation issues will vary by customer, depending on their situation, so Oracle Support will certainly try to help with issues, but the more thoroughly tested path will always be the upgrade path.

In the past, when we went from Release 10.7 to Release 11i, Oracle had good numbers on the expected downtime window given certain factors. What is a typical idea of what you can expect for the downtime window?

Mike Swing suggested that the upgrade from RDBMS Version to could take 8-12 hours, with the applications upgrade taking 12-15 hours, plus 1 day of testing; so about 3 days. To get that 3 day downtime window, the other panelists suggested you would need to consider the following:

- Test your hardware environment. In most cases you will bring in new servers. Do as much as you can ahead of time. Consider adding CPUs that you might not use moving forward. Can you lease additional CPUs for the upgrade period? Can you borrow CPUs from other hardware?

- Brainstorm ways to improve performance with your third party vendors and consultants.
Use Upgrade by Request to process the most necessary data during the upgrade, and then complete processing the rest of the data after go-live.

- Consider taking the database upgrade off the table. All new releases of the database have been certified. Mitigate the risk. While you do have to test twice if you do the database upgrade separately from the applications upgrade, the testing is different for the database upgrade, where performance considerations are the main issue, and the Applications upgrade testing for R12 is largely functionality testing.

- You won't know until you test it, then, after you test it, try to figure out how much time it will take and what you can do to reduce the time. There are lots of documents about how to reduce the downtime on My Oracle Support.


All in all, the consensus from the panel was that if you can avoid doing a reimplementation, you should, due to issues with cost, support, and time. For those customers who are waiting for Fusion, the panel concluded that if the functionality provided in Fusion Release 1 doesn't match your business needs, then you should move to Release 12 first, and wait for Fusion to catch up with your requirements in a future release.