Five Errors Customers Make When Upgrading E-Business Suite 12 [5]

This is the fifth in a series of articles about common technical myths or misunderstandings about the E-Business Suite. Previous articles have covered installations, cloning, patching, and migrations. This article discusses upgrading. The final article will cover general maintenance.

Each article is absolutely not definitive and I’d be interested in comments from readers who think there are other misconceptions about the day to day maintenance and upgrade of a typical E-Business Suite environment.


COMMON ERROR #1: Believing that DBUA does not work for Apps databases. 

ORACLE’S RECOMMENDATION: Many DBAs still like to perform database upgrades manually instead of using Oracle-provided scripts as they feel it gives them more control of the upgrade process. For the rest of us, DBUA is an excellent tool that greatly simplifies the upgrade process and which should reduce your upgrade time. E-Business Suite database upgrade documentation now assumes (but does not mandate) that you will use DBUA and documentation will be written accordingly. Raise a Service Request if you believe you have an issue where DBUA fails and the manual process is required instead.


COMMON ERROR #2: Assuming that only one test upgrade is needed before the production upgrade. 

ORACLE’S RECOMMENDATION: Oracle advise a minimum of three completely successful tests of any upgrade or maintenance downtime before your production upgrade. 


COMMON ERROR #3: Using generic documentation instead of the E-Business Suite versions. 

ORACLE’S RECOMMENDATION: As an example, if you need to upgrade your database do not just refer to the standard database upgrade manuals. The E-Business Suite Development Team have created documentation specifically for upgrading the E-Business Suite technology stack to supplement generic documentation. Follow these supplemental documents. They are well written, thoroughly tested and will make your upgrade a success.


COMMON ERROR #4: Skipping new products included in Release Update Packs (RUPs) because there are no plans to use that product. 

ORACLE’S RECOMMENDATION: When instructed to add new products to your database as part of a RUP you must always add those products. These products will later be patched and updated by this or later RUPs and if the products are not present then the patches will fail. 


COMMON ERROR #5: Manually copying files between different E-Business Suite environments. 

ORACLE’S RECOMMENDATION: New or replacement files should only be introduced to your system by patching, scheduled upgrades or other documented methods. Manually copying files between systems can cause mismatches between files in the APPL_TOP and their corresponding entries in database AD tables. This could cause patching issues later. 

 

Related Articles

posted @ 2012-08-16 14:18  dbblog  阅读(156)  评论(0)  编辑  收藏  举报