Edition-Based Redefinition (EBR): How this is related to R12.2 Online Patching.   9 comments

EBR a new feature in 11gR2 Database which plays vital role in R12.2 Online Patching

Edition-Based Redefinition enables you to upgrade an application’s database objects while the application is in use, thus minimizing or eliminating down time. This is accomplished by changing (redefining) database objects in a private environment known as an edition.

Only when all changes have been made and tested then it  make the new version of the application objects available to users.

Editioned Database Objects
• All code type objects support editioning
• The Database automatically manages multiple copies of these objects during patching


As shown above, Patch and Run Edition of Application File system sees different Projection of the table.

Code in RUN edition will treat description as 30 Characters whereas Code in Patch edition will see the new expanded 80 Characters.

A new edition is created as a child of an existing edition. The changes are made in the child edition, while the parent edition remains available for use. Changes to data (such as when a patch is applied) are made by writing only to new columns or new tables not seen by the old edition.

EBR allows an application’s database objects to be changed without interrupting the application’s availability. For example, an Oracle E-Business Suite patch can be applied while users are logged in and active. This is accomplished by making the changes in the privacy of a new edition.
Key objects used by EBR include:
• Editioning views expose a different projection of a changed table to each edition, allowing each to see only its own columns.
• Cross-edition triggers propagate data changes made by the old edition into the columns of the new edition, which subsequently replaces the old edition.

Creating a copy of the database part of the running system has been accomplished by taking advantage of the Oracle Database 11g R2 Edition-Based Redefinition (EBR) feature. This allows an application to efficiently store multiple copies of its application definition in the same database, and thereby enables online upgrade of the database tier.

The term edition refers to the isolation mechanism that allows pre-upgrade and post-upgrade schemas to co-exist. The simplest way to think of an edition is as a separate (isolated) copy of all database code objects that are changed by a patch.

The three types of database edition are:
• Run: Online users connect to this edition, which is always the default database edition. The run edition will always exist.
• Patch: Patching tools connect to this edition. A child of the run edition, the patch edition exists only while a patching cycle is in progress.
• Old: When a patch edition is promoted to be the run edition, the previous run edition is now regarded as an old edition. There may be zero or more old editions at a given time. They are discarded when full cleanup  is performed. You cannot connect to an old edition.


9 responses to “Edition-Based Redefinition (EBR): How this is related to R12.2 Online Patching.

Subscribe to comments with RSS.

  1. I have difficulty purging prior editions that clutter up my system: we deploy new code every 2 weeks, hence a new edition every time:

    ORA$BASE –> v37 –> v38 for example.

    I actualized all objects from ORA$BASE to v37, and for v38, same thing, actualized all v37 into v38

    then i tried this:

    DROP EDITION v37 cascade;

    and no luck.. got this:
    SQL Error: ORA-38810: Implementation restriction: cannot drop edition that has a parent and a child

    Any words of wisdom?

  2. Hi! Someone in my Myspace group shared this website with us so I came to look it over.
    I’m definitely enjoying the information. I’m book-marking and will be tweeting this to my followers!
    Wonderful blog and amazing design.

  3. Hi there exceptional website! Does running a blog such as this require
    a lot of work? I have absolutely no knowledge of computer programming but I had been hoping to start my own
    blog soon. Anyhow, should you have any recommendations or techniques for new blog
    owners please share. I know this is off topic but I
    simply had to ask. Kudos!

  4. My brother recommended I would possibly like this blog.
    He used to be totally right. This put up actually made my
    day. You cann’t believe just how much time I haad spent for this info!


  5. Everyone loves it whenever people come together and share views.
    Great blog, keep it up!

  6. Hi All,
    We are upgrade R12.2.4
    we faced some of the custom objects(Tables) doesn’t have Edition based info.
    Could you please let me know is there any issues or how to fix.

    Issues as well in MV (Materialized views).

    Please mail me if any answers -omshivanagesh@gmail.com

    Thanks and Regards,
    Nageshwar Reddy Porla.

  7. Thanks a lot for response.

    we are upgrading from R12.1.3 to R12.2.4 .
    Some of the custom tables and views are not created Edition info .

    Note : Custom schema are already registered in APPLICATION LEVEL LIKE CUSTOM TOPS.

    Could you please give me some inputs why it is not created Edition information for that objects.

    Like Materialized views as well Custom tables .

    Please call -571-442-3443 need to discuss more on this ..or please let me know your contact details.

    Thanks and Regards,
    Nageshwar Reddy

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: