Maris is technically right, but allowing connections from the public
internet is almost certainly a terrible idea. What is the business case
here (if you can share of course)? You might wish to have 2 listeners on
different ports so that you can do maintenance via the corporate listener,
but its hard to see this as a good enough justification for me.
On Thu, Mar 22, 2018 at 10:15 AM, Maris Elsins <elmaris@xxxxxxxxx> wrote:
Hi,
I don't really understand why you need to have 2 listeners.
I would set up one listener for that, similar to this:
LISTENER=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=tcp)(HOST=internal_ip_address)(PORT=1521))
(ADDRESS=(PROTOCOL=tcp)(HOST=external_ip_address)(PORT=1521))))
---
Maris Elsins
@MarisElsins <https://twitter.com/MarisElsins>
www.facebook.com/maris.elsins
On Thu, Mar 22, 2018 at 12:09 PM, Sam K <dbinsight@xxxxxxxxx> wrote:
Hi All,
We have an oracle database in AWS EC2( no rac) running with a single
listener configured
we want to attach a second NIC card to the instance and configure a
second listener to accept requests from the pubic internet only
so we will essentially have two listeners for the same DB (11g) - one
for internal private use (corporate network) configured
the other listener we want to configure it to allow public access , allow
it to accept incoming connection from the internet only
This listener configured on the new NIC will be configured thru firewall
and accept traffic from public internet.
Is it possible to have such a configuration
Or is it better to have a remote listener configuration for the external
access only and local listener for the internal traffic
Looking for tips/ guidance from the group
--
Regards
Sam K
