Hi,
The ebs_patch entry in init.ora is for the Online Patching feature in 12.2
which internally makes use of edition based redefinition.
It's perfectly OK to have the following in ebs_patch in the init.ora for
multiple databases on the same server. This is because only application
internal patching code will ever use this and it knows to connect to the
right database. We have this done in our non production cluster where
databases are consolidated while applications are not.
Hope this helps.
Thanks, J
On 29 November 2016 at 01:19, Maris Elsins <elmaris@xxxxxxxxx> wrote:
Hi,
I think the most simple approach would be having separate listeners for
each database.
regards,
---
Maris Elsins
@MarisElsins <https://twitter.com/MarisElsins>
www.facebook.com/maris.elsins
On Mon, Nov 28, 2016 at 9:42 PM, Beckstrom Jeffrey <JBECKSTROM@xxxxxxxxx>
wrote:
We run with multiple R12.1 non-production databases on one server. We
wish to do the same in R12.2 of EBS. Found note 1472560.1
<https://support.oracle.com/epmos/faces/DocumentDisplay?parent=SrDetailText&sourceId=3-13729275901&id=1472560.1>
which states have to add ebs_patch entry to services_name parameter of
init.ora. Note 1662741.1
<https://support.oracle.com/epmos/faces/DocumentDisplay?parent=SrDetailText&sourceId=3-13729275901&id=1662741.1>
states can continue to have multiple databases on one server. Therefore,
confused about this ebs_patch entry in init.ora if same entry exists for
multiple databases on the server and same oracle home. Our web tiers will
be on separate servers, only the database tier is consolidated. I don't
understand how I can have multiple databases with the same service name.
Can someone shed some light on this.
Jeffrey Beckstrom
Lead Database Administrator
Information Technology Department
Greater Cleveland Regional Transit Authority
1240 W. 6th Street
Cleveland, Ohio 44113
