TIp of the week: Got IE 11 for EBS?


As many organizations gearing up for Internet explorer 11, where do Oracle stand on certifying it for Oracle E-Business Suite?

Look no further than Steven Chan’s latest post here

Alternatively access the URL below

https://blogs.oracle.com/stevenChan/entry/ie11_ebs?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+OracleE-BusinessSuiteTechnology+%28Oracle+E-Business+Suite+Technology%29

In short, its not yet certified :)

 

Revisiting Magical Ingredient EBR in Oracle E-Business Suite R12.2.2


As Oracle EBS R12.2 just become a GA, an interesting metaphor is reducing downtime for planned software maintenance. As enough said on ADOP here http://oracletechnologistblog.wordpress.com/2012/06/20/oracle-ebs-r12-2-online-patching-via-adop/

http://oracletechnologistblog.wordpress.com/2012/01/17/r12-2-key-features/ and elsewhere, there is less information on the revolutionary 11gR2 database feature Edition-Based Redefinition, which is essential to ADOP.

If you are an Oracle E-Business Suite customer, multi-tier patching is inevitable. EBS R12.2’s ADOP is certainly a revolutionary feature that comprehensively provides minimal definable downtime.  Complexity in R12.2’s ADOP feature resides in the database. Magical ingredient here is Edition-Based Redefinition (EBR) feature within the database.

Lets briefly dig into the recent evolution of minimizing downtime features in Oracle database and more. Over the years, Oracle database team has developed several key capabilities such as online index rebuild, non-blocking nature of ALTER TABLE DDLs, eliminating object invalidations due to logical changes, that continue to reduce downtime along with costly endeavors such as schema clones and log-based replication, still you are left with noticeable downtimes. That changes with EBR, which provides three features such as edition, edition view and crossedition trigger that helps online application patching and upgrades. Lets take a look at these three features in detail.

Edition: Edition’s principal objective is to provide isolation mechanism and is considered as a non-schema object type.  It permits same object to occur multiple times in same database yet maintain unalike or different editions. Furthermore, all the database objects fall under two types of editions such as editionable and non-editionable types.

whats editionable object type:  Code type objects such as PL/SQL, views, types, synonyms, triggers and editioning views supports edition. Nonetheless, it prevents changes in one edition of the object to impact other editions of same object. Especially in ADOP where the instance has to maintain multiple copies of the code objects, edition feature come in handy to accomplish the online patching capability.

Whats non-editionable object type: So what about storage objects? Will that provide any editioning? Short answer is no. Here are the details. Storage objects such as tables, indexes, materialized views and also sequences do not support editioning and are categorized as non-editionable types.

Editioning View:

In edition world, there is a potential to have multiple editioned table data. With editioning view capabilities, it’s truly possible. Editioning view allows several versions of table’s data by logical representations, where a physical table cannot be editioned. In other words, a table can store data related to multiple editions but its the editioning view that provides the accurate subsection of data from underlying table.

On a side note, Oracle highly recommends that in preparation for R12.2, its vital to not to have any of your customizations refer to base tables directly as EBS data model now provides a cover layer via editioning views. It is extremely important that you refer the cover layer to access EBS data model instead of physical layer to prevent any integrity issues. The reason behind this requirement is to prevent any code accessing outdated columns in physical layer. In R12.2 world, Oracle strongly recommends that all code should access the data model only via apps synonym as it internally points to editioning view. Nonetheless, editioning views allow triggers to be defined on them along with hint reference.

Crossedition Trigger

Oracle 11gR2introduced a special kind of editionable object type trigger called crossedition trigger. Lets assume the patch process need to change the structure of an OLTP table. ADOP to work properly a mechanism that can keep up the pace with changes that user makes to the pre-patch state of the data yet transform the data into postpatch state. Pre-patch will continue to see the running edition of the table while the post-patch would see the new structure. This is possible due to crossedition trigger that uses advanced synchronization mechanism to ensure the values of the pre-patch transactional data is in sync with what could be post-patch transactional data inspite of structural changes to the table.

Within crossedition trigger, Oracle introduced two types of triggers that are forward corssedition trigger and reverse crossedition trigger.

Simply put, forward Crossedition trigger is instrumental for bringing the pre-patch column values to the post-patch values and reverse Crossedition trigger exactly does the contrary.

EBR re-definition lifecycle in ADOP process would have similar pattern

  • Virgin state of the database will have only one edition, prepatch
  • During the patching process, the database will have two editions called prepatch and its child edition called postpatch.
  • When you have successfully executed the ‘cutover’ stage of the ADOP cycle which is at the stage where you no longer need prepatch edition, it will be retired and postpatch will now become parent edition and thus will have one edition.

Reference:

http://www.oracle.com/technetwork/database/features/availability/edition-based-redefinition-1-133045.pdf

http://docs.oracle.com/cd/E11882_01/appdev.112/e10471/adfns_editions.htm

http://www.oracle.com/webfolder/technetwork/tutorials/obe/ebs/ebs121/atg/OnlinePatching.pdf

MOS: Example of Edition-Based Redefinition using Cross-Edition Triggers [ID 845667.1]

Oracle E-Business Suite Release 12.2 Information Center – Implement (Doc ID 1583153.1)

Using the Online Patching Readiness Report in Oracle E-Business Suite Release 12.2 (Doc ID 1531121.1)

Its official. Oracle Releases E-Business Suite R12.2


Long wait is finally over. Oracle just released E-Business Suite R12.2 (General Release). This release signifies  Online Patching and Enhancements Across Integrated Suite of Business Applications. For further details please refer to the official press release below.

http://www.oracle.com/us/corporate/press/2016931?rssid=rss_ocom_pr

Useful R12.2 links

http://oracletechnologistblog.wordpress.com/2012/01/17/r12-2-key-features/

http://oracletechnologistblog.wordpress.com/2012/06/20/oracle-ebs-r12-2-online-patching-via-adop/

 

 

 

 

Useful notes
Oracle E-Business Suite Release 12.2 Information Center – Implement (Doc ID 1583153.1)

Using the Online Patching Readiness Report in Oracle E-Business Suite Release 12.2 (Doc ID 1531121.1)

Using the Online Patching Readiness Report in Oracle E-Business Suite Release 12.2 (Doc ID 1531121.1)

Attending Oracle Open World? What to expect?


Well its that time of the year and that type of blog post. Its imperative to get pumped up on Oracle Open World 2013.  So where would be the focus? Like last year, propaganda on Cloud is inevitable and that has created even more buzz with Oracle’s strategic partnership with Salesforce.com.  Big data & Analytics, 12c Database with Oracle’s Mobile strategy are few more that can generate ample curiosity among attendees.  So how about Engineered Systems? Of course. Especially when Oracle’s mid-market penetration strategies allow to come up with ¼ rack size for ES, which in turn triggers attractive entry points. Don’t know why I think about BMW’s 1-series here ;) If you work directly with any of your Oracle accounts team members, they will highly ‘recommend or encourage’ you to attend ES sessions.

By the way, how many of you thought Oracle and Microsoft never get along. Well you might be right for several years and now that phenomenon has changed. “Microsoft and Oracle: Partners in the enterprise cloud”.  That’s one of the key note topics from Brad Anderson, Corporate Vice President,Microsoft. Yet another reason for OOW’s Cloud mantra.

Anyways, here are few tracks that you can get a glimpse on. Honestly, I find quite a few sessions that elicit significant interest in me.

Oracle database

https://oracleus.activeevents.com/2013/connect/focusOnDoc.do?focusID=23520

Oracle EBS Tools & Technology

https://oracleus.activeevents.com/2013/connect/focusOnDoc.do?focusID=22573

Oracle Mobile

https://oracleus.activeevents.com/2013/connect/focusOnDoc.do?focusID=23570

Oracle EBS Management

https://oracleus.activeevents.com/2013/connect/focusOnDoc.do?focusID=23512

Fusion Apps

https://oracleus.activeevents.com/2013/connect/focusOnDoc.do?focusID=23534

Business Analytics

https://oracleus.activeevents.com/2013/connect/focusOnDoc.do?focusID=22725

Useful links

http://www.oracle.com/openworld/index.html

Schedule Builder

https://oracleus.activeevents.com/2013/connect/dashboard.ww

High level Agenda

http://www.oracle.com/openworld/agenda/index.html

 

How to reset Weblogic password in Fusion Middleware Environment


As weblogic being core to Oracle’s Fusion Middleware product suite, we tend to get into embarrassing situations such as losing weblogic password :)

If it happens to you, below post should help you to reset the password.

NOTE: Take a backup of entire domain completely before making any changes.

1.- Take the back of the LDAP folder of the admin server as well as managed server (you may rename those folders) and then delete the actual LDAP folder (found at <Domain_Home>\servers\<MyServer>\data\ldap).

2. Make sure WebLogic instance is down.

3. Set your environment variables using setDomainEnv.cmd

4. cd to security directory in your instance.
(eg: $WL_HOME/user_projects/domains/base_domain/security)

5. Run:
java weblogic.security.utils.AdminAccount admin_user admin_pass .

Remember to change “admin_user” and “admin_pass” to your required username and password.
Also, don’t forget the period “.” at the end of the above command, it is required.

6. After running the command, the file “DefaultAuthenticatorInit.ldift” will get updated.

7. Delete the following file from “ldap” folder:

cd WL_HOME/user_projects/domains/base_domain/servers/AdminServer/data/ldap
rm DefaultAuthenticatormyrealmInit.initialized

8. Go to folder DOMAIN_HOME/servers/AdminServer/security

9. Edit the boot.properties file and change the password to the value already used on step 5. Do this for all the servers in the domain.

10. Start Weblogic Server (Weblogic Server will encrypt the password for you)

Oracle E-Business Suite – Tip of the week


Tip of the week:

As simplified Chinese is becoming one of the widely used languages in Oracle E-Business Suite environments, a few notable issues are inevitable. Below issue is one to notice.

Problem: Running standard reports in EBS application (not specific to any product) in Chinese, returns inverse ? “COMPANY ¿¿: 48 ¿ 48”

Solution:

  1. Set profile option “NATIVE CLIENT ENCODING” to UTF8 or AL32UTF8.
  2. Restarted the services after the profile change.
  3. Retest the issue.

Useful MOS notes:

The correct NLS_LANG setting in Unix Environments (Doc ID 264157.1)

Recommended Set Up for Client/Server Products with Oracle E-Business Suite 11i & R12 [ID 277535.1]

Effective MLS management using Lightweight MLS in Oracle E-Business Suite


Getting started

In 12.1.3, Oracle came up with Lightweight Multi-Language Support (MLS) feature to help environments to reduce significant overhead such as extended downtime in applying language patches, saving substantial amount of disk space associated to NLS patching. In other words, when using Lightweight MLS, you are not required to apply the time and resource consuming NLS patches.

Even though you cannot have both full and lightweight MLS for the same language, you can still have your environment fully patched with NLS languages co-exist with lightweight languages. Thus enabling hybrid language environment. Moreover, you can migrate any of your Lightweight MLS languages to full MLS using NLS patching at any given time. Additionally, 12.1.3 supports 34 languages.

Consider the spirit of Lightweight MLS as the “UI is in English, while the setup or customer data are shown in the relevant language”.

Nonetheless, Lightweight MLS do have its own limitations. Since you will be using English user interface and if your users prefer NLS translated forms and reports, LMLS may not be for you.

With lightweight MLS, Oracle provides a capability to enter and maintain multiple language data using English user interface, yet delivers the ability to display data in appropriate language. Users can use so called ‘globe’ icon in forms to enter the needed language data showed in below screenshot.

Steps

  1. If you are implementing a new language, from System Administration ->Oracle Applications Manager ->License Manager, click on Languages under license, select the needed Language name and submit.
  2. From adadmin, under Maintain Applications Database Entities menu (option 4), run Maintain multi-lingual tables (option 3).
  3. It’s highly recommended that you run the message synchronization script $FND_TOP/patch/115/sql/AFMSGSYNC.sql. Input the language code that you enabled in step 1.
  4. Once done, restart the applications services via adstrtal.sh.

Behind the scenes

The R12.1.3 Multilingual Support (MLS) table architecture needs the multilingual tables to fully populate for all active languages. By running maintain multi-lingual tables option ensures that every row in the base table has an analogous row in the MLS table. This is applicable for all the active languages.

When you run the AFMSGSYNC.sql script, it first asks for the language that you enabled. It then reads FND_NEW_MESSAGES table to see if language data exists. If not, it synchronizes the language data in FND_NEW_MESSAGES table with the base language data in message directory. Additionally, lightweight MLS stores the translation data in the %_TL tables.

 PS: If you already have few languages installed with NLS and prefer to convert those to lightweight MLS, all you need to perform is follow steps 3 and 4.

Follow

Get every new post delivered to your Inbox.

Join 25 other followers

%d bloggers like this: