Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Oracle Edition Based Redefinition (EBR) feature of 11g

755737Feb 8 2011 — edited Feb 15 2011
We are researching the use of Oracle EBR features of 11g database in our company to reduce downtimes. I have read some article and white papers on Oracle EBR and also tried out this technology on a test database. I feel that Oracle EBR is a very interesting and provides some nice feature but I have a few questions that I would like some clarification on. I'd appreciate it if anyone has input on these.

We deploy custom code every month and generally take the Oracle Database and App Servers down during the patch process. If we were to use Oracle EBR, my understanding is that we would still need a short downtime to disconnect existing sessions and switch the database to the new edition as the default. The main reason for this is as follows:

- If we do not disconnect existing sessions, then different sessions could be using different editions of the code which would cause confusion with troubleshooting issues. Ideally we would want the new edition code to be running for all sessions at a given instance.

- Some of our users have Oracle Forms applications open that connect to the database (some Forms are always left open ex: on the mfg shop floor) . If we do not have a downtime, then the existing Forms session could potentially never see the new edition code

- We have several web applications that connect to the database via a connection pool on the App Server. In order for these applications to access the new code, we would need to bounce the App Server also.

Given this scenario, would you agree that a downtime would be needed?

The time it takes for us to apply view/package changes during a typical patch application is just a few minutes so we are wondering if it is even worth the effort to implement Oracle EBR to save a few minutes of downtime (assuming we have to take a downtime anyway). Most of our patch application time is spent on compiling/generating Forms/Reports which has to be done in a downtime anyway since Oracle EBR is relevant only to database object changes.

I am curious to know how other customers are using Oracle EBR in real life situations particularly in scenarios where they have applications developed using Oracle Forms or Web Apps using a connection pool. Are there any case studies out there? Is this something that is more useful for huge upgrades where hundreds of database objects are changed as opposed to routine application changes? Is there a way to force an existing session to switch to a new edition without requiring a database downtime?
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 15 2011
Added on Feb 8 2011
5 comments
835 views