Force Connections to a Specific Database Service When two Identical Services are Registered to CMAN
(Doc ID 1455068.1)
Last updated on MARCH 31, 2022
Applies to:
Oracle Net Services - Version 10.2.0.4 to 12.2.0.1 [Release 10.2 to 12.2]Information in this document applies to any platform.
Goal
The TNS Poison issue can apply to a CMAN listener as well as a normal TNS listener. In the case of CMAN, there is no need for complex SSL setups or complex remote_listener settings. All that is required of CMAN, to not be a victim of the TNS Poison issue, is to create a rule(s) in the CMAN.ORA file that will tell CMAN to only send connection requests to a specific destination and/or a specific service name.
The problem can be defined using the example:
Node 1 is registering a database service to Connection Manager (CMAN) called "prod"
Node 2 is also registering a database service to Connection Manager (CMAN) called "prod"
"CMCTL> show services" would report Service "prod" has 2 instance(s).
This note will describe the steps needed to configure CMAN to force all client connections to Node 1. This configuration will cause clients using CMAN to ignore Node 2.
Pre-requisite (1): CMAN version 10.x, 11.x, or 12.x must be installed and operational
Additional information can be found in the Oracle Database Net Services Administrator's Guide in the Chapter covering "Configuring Oracle Connection Manager"
Pre-requisite (2): A database services should be registered with CMAN using the REMOTE_LISTENER parameter (although older SOURCE_ROUTE configuration will work as well).
Additional information can be found in the Oracle Database Net Services Administrator's Guide in the Chapter covering "Configuring Oracle Connection Manager"
and more specifically under the section: "Configuring the Oracle Database Server for Oracle Connection Manager"
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |