Integrating Connection Manager (CMAN) into a RAC+SCAN Environment (Doc ID 1556300.1)

Last updated on MAY 20, 2015

Applies to:

Oracle Net Services - Version 11.1.0.7 to 11.2.0.3 [Release 11.1 to 11.2]
Information in this document applies to any platform.

Goal

CRS is not "CMAN aware", nor is CMAN "CRS aware".  While the two products currently exist independently and function independently, they can be integrated into your infrastructure - with caveats.  For example, client applications can take advantage of all of the features of CMAN; however, CRS cannot detect a CMAN outage.  

Because RAC is independant of CMAN, there are no configuration changes that need to be made on the server.  Parameters such as LOCAL_LISTENER and REMOTE_LISTENER will remain untouched.  The only tasks required is to configure CMAN and alter the client's tnsnames.ora file.

Configuring CMAN and any rules will not be covered in this note. The Oracle Net Administrator's Guide covers this topic.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms