Discussions
Categories
- 381.9K All Categories
- 2.1K Data
- 207 Big Data Appliance
- 1.9K Data Science
- 447.5K Databases
- 220.8K General Database Discussions
- 3.7K Java and JavaScript in the Database
- 24 Multilingual Engine
- 516 MySQL Community Space
- 464 NoSQL Database
- 7.8K Oracle Database Express Edition (XE)
- 2.9K ORDS, SODA & JSON in the Database
- 473 SQLcl
- 3.9K SQL Developer Data Modeler
- 186K SQL & PL/SQL
- 20.9K SQL Developer
- 292.7K Development
- 7 Developer Projects
- 125 Programming Languages
- 289.5K Development Tools
- 95 DevOps
- 3K QA/Testing
- 645.5K Java
- 23 Java Learning Subscription
- 36.9K Database Connectivity
- 150 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.8K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 16 Java Essentials
- 143 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 197 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 243 LiveLabs
- 35 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.8K Other Languages
- 2.3K Chinese
- 166 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 225 Portuguese
Each schema on separate listener
Hello,
Is it posible to have each schema on separate listener so each schema will be accessed from different port?
Please let me know if it is possible.
Thanks!
Answers
-
Catinredboots wrote: Hello,Is it posible to have each schema on separate listener so each schema will be accessed from different port?Please let me know if it is possible. Thanks!
Yes, it is possible to have multiple listeners running on a single DB Server.
It is also possible to poke yourself in the eye with a sharp pencil.
It is equally foolish to do either possible action.
Do you realize & understand that you can shutdown any Oracle listener & that there will be ZERO impact to existing connected Oracle sessions?
Oracle listener is only active to service the initial connection requests coming from remote client.
If you have a stable application that use Connection Pooling, no listener is really need after the Connection Pool has been initially established.
How do you limit a listener to connecting to a single schema?
What is the advantage of having a dedicated listener for each schema?
-
Is it posible to have each schema on separate listener so each schema will be accessed from different port?
No - listeners are used to connect to databases - not schemas.
-
Catinredboots wrote: Hello,Is it posible to have each schema on separate listener so each schema will be accessed from different port?Please let me know if it is possible. Thanks!
To be honest, you have a very strange requirement.
In order to help you better, please explain what issue you have.
-
Not required , strange requirement.
-
Catinredboots wrote:Is it posible to have each schema on separate listener so each schema will be accessed from different port?Please let me know if it is possible.
Not possible.
And a clear indication that you are entirely unfamiliar with Oracle client-server architecture, and concepts. You should explain instead what you think the requirement or issue is, instead of asking how a broken and flawed solution can be crafted.
-
Catinredboots wrote: Hello,Is it posible to have each schema on separate listener so each schema will be accessed from different port?Please let me know if it is possible. Thanks!
As others have said, it is not possible, and not necessary.
And as other's have asked, why do you think you'd want to?
============================================================================
Please stay after school and write the following sentence 100 times:
One single listener, using the default name of LISTENER and the default port of 1521, is quite capable of -- indeed, WAS DESIGNED TO -- service multiple databases of multiple versions running from multiple homes. Multiple listeners simply adds complications, and for no gain whatsoever.
============================================================================
-
Application team would like to have different application server connect to a different port number per schema, it is for some kind of testing.
Thanks everyone for you explanation, it looks like it is not possible and I will tell them know that they will need a separate database for each one.
-
Catinredboots wrote:Application team would like to have different application server connect to a different port number per schema, it is for some kind of testing. Thanks everyone for you explanation, it looks like it is not possible and I will tell them know that they will need a separate database for each one.
Application team would benefit from some serious (re)training!
Why not just have different schemas for testing isolation?
-
Catinredboots wrote:Application team would like to have different application server connect to a different port number per schema, it is for some kind of testing. Thanks everyone for you explanation, it looks like it is not possible and I will tell them know that they will need a separate database for each one.
yes it is possible but does not have sense.
-
Catinredboots wrote:Application team would like to have different application server connect to a different port number per schema, it is for some kind of testing. Thanks everyone for you explanation, it looks like it is not possible and I will tell them know that they will need a separate database for each one.
No problem with that. Configure your listener to listen on as many ports as necessary.
