How to manage DB Control 11.x for RAC Database with emca (文档 ID 578011.1)

How to manage DB Control 11.x for RAC Database with emca (文档 ID 578011.1)

In this Document

 Purpose Scope Details Difference between the DB Control for RAC 10.1.x.x and the DB Control for RAC 10.2.x.x or 11.x Environment: RAC Database 11.1.0.7 with 3 instances running on a Cluster with 3 nodes Configure DB Control for a RAC database running 3 instances on a 3 RAC cluster node Reconfigure DB Control to have 2 dbconsole started and running to manage a RAC database running 3 instances on a 3 RAC cluster node Remove an instance from DB Control monitoring Add an instance to DB Control monitoring Drop the DB Control keeping the repository DB Control deconfiguration removing the repository References

---

APPLIES TO:

Enterprise Manager for Oracle Database - Version 11.2.0.1 to 11.2.0.4 [Release 11.2]
Information in this document applies to any platform.

PURPOSE

This bulletin will clarify the way to set up/configure/deconfigure DB Control 11.x for RAC database 11..x.
Examples of emca commands will be illustrated and the directory structure will be explained as well.

This bulletin is not intended to replace Oracle Documentation but to illustrate it.

For a complete overview of emca, please refer to the following documentation available at OTN:

Oracle Database Release 11.1.x

Oracle Database Utilities
11g Release 1 (11.1) - Part Number B28319-02
http://download.oracle.com/docs/cd/B28359_01/server.111/b28319/toc.htm
Topic: Using EMCA With Oracle Real Application Clusters

Oracle Database Release 11.2.x

Oracle Database Administrator's Guide
11g Release 2 (11.2) - Part Number E17120-06
Topic: Using Using EMCA With Oracle RAC

SCOPE

• This article is intended for DBAs using DB Control to manage RAC databases 11.x
• Before reading this article, the user must have a good understanding of RAC 11.x databases installation, configuration and functionalities
• This article is intended to illustrate the main emca commands to setup/configure DB Control for RAC datadase 11.x: installation/configuration/setup and usage of RAC database 11.x is beyond the scope of this article.
  Please refer to the RAC documentation available on OTN for any RAC related topic.
  http://www.oracle.com/pls/db111/homepage (Oracle Database Release 11.1.x)
  http://www.oracle.com/pls/db112/homepage (Oracle Database Release 11.2.x)

DETAILS

Difference between the DB Control for RAC 10.1.x.x and the DB Control for RAC 10.2.x.x or 11.x

As a reminder, DB Control 10.x.x.x includes 3 components:
- the dbconsole Management Service
- the dbconsole Management Agent
- the dbconsole Management Repository

In 10.1.x.x, when a DB Control was deployed on a RAC cluster with n nodes, a dbconsole was started on each node of the cluster. Each agent on each node reported to each dbconsole management service on the same node.

Beginning 10.2.x.x, to improve performance and reduce the workload on the RAC database/instances,when a DB Control is first deployed on a RAC cluster with n nodes, a dbconsole is started only on the node from which the DB Control is deployed. Each agent on each node reports to that same unique dbconsole management service.
It is however possible to later reconfigure the DB Control to have more than one dbconsole started and to have agents reporting to several dbconsole.

Environment: RAC Database 11.1.0.7 with 3 instances running on a Cluster with 3 nodes

For the purpose of this article, we will illustrate DB Control on the following configuration:
Cluster RAC 11.1.0.7 on linux x86-64 with OEL 5.0

Cluster crs with 3 nodes:
- node1.mycompany.com
- node2.mycompany.com
- node3.mycompany.com

RAC Database 10.1.0.7 EM111 using ASM with 3 instances:
- EM1111 running on node1.mycompany.com
- EM1112 running on node2.mycompany.com
- EM1113 running on node3.mycompany.com

The RAC database has been created manually without using dbca, therefore emca has not been run and there is no DB Control repository created in the RAC database.

The RAC database is not the hosting database for a Grid Control repository

This can be checked running the following SQL statement connected as a DBA user to the database:

SQL> select username from DBA_USERS where username = 'SYSMAN';

If the SQL Statement returns 'SYSMAN', it means that there is already a DB Control repository or a Grid Control repository present in the database.
A DB Control repository is created with objects in SYSAUX tablespace.

• A Grid Control repository is created with objects in MGMT_TABLESPACE and MGMT_ECM_DEPOT_TS.

To distinguish a Grid Control repository and a DB Control repository, you need to execute the following query connected through Sql*Plus as SYSMAN to the database:

SQL> column component_name format a30 
SQL> column component_mode format a30 
SQL> column version format a10
SQL> select component_name, version, component_mode 
  2  from mgmt_versions 
  3* where component_name ='CORE';

The value of the column COMPONENT_MODE is CENTRAL for a Grid Control repository.

COMPONENT_NAME VERSION COMPONENT_MODE 
------------------------------ ----------     ------------------------------ 
CORE                            10.2.0.4.0  CENTRAL

The value of the column COMPONENT_MODE is SYSAUX for a DB Control repository. 

COMPONENT_NAME        VERSION COMPONENT_MODE 
------------------------------ ----------    ------------------------------ 
CORE                                    10.2.0.4.0   SYSAUX 


If a Grid Control repository or a DB Control repository already exists and if you want to drop the existing repository because you are sure that this repository is decommissioned, you can use the following process:

To drop a DB Control repository or a to drop a Grid Control repository:
Note: This can be done from any node of the cluster, connected to whichever instance you prefer.

1. cd to RDBMS ORACLE_HOME/sysman/admin/emdrep/bin (for a DB Control Repository)
   or
   cd to the OMS ORACLE_HOME/sysman/admin/emdrep/bin (for a Grid Control Repository)
2. Issue the following command* repository_host is the machine name where the Management Repository database is located
   
   $ ./RepManager repository_host repository_port repository_SID
   -sys_password password_for_sys_account -action drop
   
   * repository_port is the Management Repository database listener port address, usually 1521 or 1526
   * repository_SID is the Management Repository database system identifier
   * password_for_sys_account is the password of the SYS user for the database. For example, change_on_install.
   * -action drop indicates that you want to drop the Management Repository.
   
   Note: Dropping a Grid Control or DB Control repository quiesces and unquiesces the database. 
   Note2: Manual steps from note 278100.1 can be also used to drop the repository objects.

Configure DB Control for a RAC database running 3 instances on a 3 RAC cluster node

Connect to node1.mycompany.com and set the environment for the RDBMS RAC database ORACLE_HOME
ORACLE_HOME and ORACLE_SID must be set
ORACLE_HOME and ORACLE_HOME/bin are set in the environment variable $PATH

Run emca in interactive mode:

$ emca -config dbcontrol db -repos create -cluster

Enter the following information:

• Cluster Name
  To find out the value of your CLUSTER_NAME from CRS (OCR), do the following from the CRS_HOME:
  
  $ cd $CRS_HOME/bin
  $ ./cemutlo -n
• Database unique name
  If you're not sure of the values for Database unique name and service name, execute the following statement connected as a DBA user to any instance of the RAC database: 
  
  SQL> show parameter db_unique_name
• Listener port
• SYS password
• DBSNMP password
• SYSMAN password
• ASM ORACLE_HOME (ASM_OH)
• ASM SID (ASM_SID)
• ASM ROLE (ASM_USER_ROLE)
• ASM USERNAME (ASM_USER_NAME)
• ASM PORT (ASM_PORT)

or

Run emca in silent mode:
It is also possible to run emca in silent mode, providing a response file with all the parameters needed:

$ emca -config dbcontrol db -repos create -cluster -silent -respfile /u01/app/oracle/admin/EM111/scripts/emca_configandrep.rsp

with content of file /u01/app/oracle/admin/EM111/scripts/emca_configandrep.rsp as follow: 
CLUSTER_NAME=mycrsname
DB_UNIQUE_NAME=EM111 
SERVICE_NAME=EM111 
SYS_PWD=oracle 
SYSMAN_PWD=oracle 
DBSNMP_PWD=oracle 
PORT=1521
ASM_OH=/u01/app/oracle/rdbms111
ASM_SID=+ASM1
ASM_PORT=1521
ASM_USER_ROLE=SYSDBA
ASM_USER_NAME=SYS
ASM_USER_PWD=oracle

This emca command will:

• Create the DB Control repository in the RAC database
• Configure the DB Control on the local node and deploy the DB Control on all nodes of the cluster
• Start the DB Control on the local node (dbconsole and agent)
• Start all the agents on all the other nodes of the cluster

The resulting sub-directories of the RDBMS ORACLE_HOME will be the same on each node of the cluster:

$ORACLE_HOME/node1_EM111
$ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node1_EM111
$ORACLE_HOME/node2_EM111
$ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node2_EM111
$ORACLE_HOME/node3_EM111
$ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node3_EM111

On the cluster node node1.mycompany.com, the "active" sub-directories will be
$ORACLE_HOME/node1_EM111
$ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node1_EM111

On the cluster node node2.mycompany.com, the "active" sub-directories will be
$ORACLE_HOME/node2_EM111
$ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node2_EM111

On the cluster node node3.mycompany.com, the "active" sub-directories will be
$ORACLE_HOME/node3_EM111
$ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node3_EM111

The other directories are just "witnesses" of the current DB Control configuration on the cluster.

Note: If you deploy another DB Control for another RAC database on the same cluster, 
          you will have as well on each node of the cluster a new set of directories created under the
          RDBMS ORACLE_HOME.
          The format of the sub-directories is always shorthostnamei_dbuniquename.
          The active sub-directories on node i is always shorthostanmei_dbuniquename.

To check the configuration files, log files, targets.xml, contents of upload or recv directories
You must look only into the "active" directory.
This means that to check the file emd.properties of the agent on node1, you must login to node1 and look into $ORACLE_HOME/node1.mycompany.com_EM1111/sysman/config.
If you want to check the targets.xml of the agent on node3, you must login to node3 and look into  $ORACLE_HOME/node3.mycompany.com_EM1113/sysman/emd

or

• Login to node3, set the environment variables
  - ORACLE_HOME
  - ORACLE_SID 
  - ORACLE_HOME and ORACLE_HOME/bin are set in the environment variable $PATH
• Run
  
  $ emctl config agent listtargets

Example of targets.xml file:

<Targets AGENT_SEED="231030912">
<Target TYPE="oracle_emd" NAME="node1.mycompany.com:3938"/>
<Target TYPE="host" NAME="node1.mycompany.com">
<CompositeMembership>
<MemberOf TYPE="cluster" NAME="mycrsname" ASSOCIATION="cluster_member"/>
</CompositeMembership>
</Target>
<Target TYPE="cluster" NAME="mycrsname">
<Property NAME="OracleHome" VALUE="/u01/app/oracle/product/11.1.0/crs"/>
</Target>
<Target TYPE="oracle_database" NAME="EM111_EM1111">
<Property NAME="MachineName" VALUE="node1vip.mycompany.com"/>
<Property NAME="Port" VALUE="1521"/>
<Property NAME="SID" VALUE="EM1111"/>
<Property NAME="OracleHome" VALUE="/u01/app/oracle/product/11.1.0/db"/>
<Property NAME="UserName" VALUE="8454cd093bd33db3" ENCRYPTED="TRUE"/>
<Property NAME="password" VALUE="b9ae96b172e0d873" ENCRYPTED="TRUE"/>
<CompositeMembership>
<MemberOf TYPE="rac_database" NAME="EM111" ASSOCIATION="cluster_member"/>
</CompositeMembership>
</Target>
<Target TYPE="rac_database" NAME="EM111">
<Property NAME="MachineName" VALUE="node1vip.mycompany.com"/>
<Property NAME="Port" VALUE="1521"/>
<Property NAME="SID" VALUE="EM1111"/>
<Property NAME="OracleHome" VALUE="/u01/app/oracle/product/11.1.0/db"/>
<Property NAME="UserName" VALUE="8454cd093bd33db3" ENCRYPTED="TRUE"/>
<Property NAME="password" VALUE="b9ae96b172e0d873" ENCRYPTED="TRUE"/>
<Property NAME="ClusterName" VALUE="mycrsname"/>
<Property NAME="ServiceName" VALUE="EM111"/>
</Target>
<Target TYPE="oracle_listener" NAME="LISTENER_node1.mycompany.com_node1.mycompany.com">
<Property NAME="Machine" VALUE="node1vip.mycompany.com"/>
<Property NAME="LsnrName" VALUE="LISTENER_node1.mycompany.com"/>
<Property NAME="Port" VALUE="1521"/>
<Property NAME="ListenerOraDir" VALUE="/u01/app/oracle/product/11.1.0/db/network/admin"/>
<Property NAME="OracleHome" VALUE="/u01/app/oracle/product/11.1.0/db"/>
</Target>
<Target TYPE="osm_instance" NAME="+ASM1_node1.mycompany.com">
<Property NAME="SID" VALUE="+ASM1"/>
<Property NAME="MachineName" VALUE="node1vip.mycompany.com"/>
<Property NAME="OracleHome" VALUE="/u01/app/oracle/product/11.1.0/db"/>
<Property NAME="UserName" VALUE="SYS"/>
<Property NAME="password" VALUE="b9ae96b172e0d873" ENCRYPTED="TRUE"/>
<Property NAME="Role" VALUE="SYSDBA"/>
<Property NAME="Port" VALUE="1521"/>
</Target>
</Targets>

To check the DB Control configuration on the cluster:

$ emca -displayConfig dbcontrol -cluster 

INFO: 

**************** Current Configuration **************** 

INSTANCE NODE DBCONTROL_UPLOAD_HOST 
---------- ---------- --------------------- 
EM1111 node1 node1.mycompany.com 
EM1112 node2 node1.mycompany.com 
EM1113 node3 node1.mycompany.com 

 This table shows that:

• the db control is running on node1.mycompany.com (DBCONTROL_UPLOAD_HOST)
• there are 3 instances monitored EM1111, EM1112 and EM1113 on nodes node1, node2 and node3 respectively.
• the agents on nodes node1, node2 and node3 are all reporting to the dbconsole running on node node1.mycompany.com, because emca was run from node1.mycompany.com. If emca had been run from node2.mycompany.com, all agents would have reported to node2.mycompany.com

To check the emca log files:

As displayed to the standard output, emca log files are created in $ORACLE_BASE/cfgtoollogs/emca/EM112.
The log files are only created on the local node (the node from which emca has been run).
The log file for DBControl configuration/setup and deployment is emca_<timestamp>.log
The log file for DB Control repository creation is emca_repos_create_<timestamp>.log

For more information on emca log files, please refer to:
Note 330689.1 How To Trace/Debug the EMCA Tool in 10g and 11g

Login to DB Control

At the end of the deployment, emca gives the URL to login to the dbconsole.
This URL is also available in the dbconsole log file.
This URL is also available in the file $ORACLE_HOME/install/readme.txt
The Console ports and Agent ports can be checked in the file $ORACLE_HOME/install/portlist.ini

Reconfigure DB Control to have 2 dbconsole started and running to manage a RAC database running 3 instances on a 3 RAC cluster node

This does not really make sense for a 3 nodes RAC cluster, but it is possible to have several dbconsole running instead of one, and agents configured to report to different dbconsole.

For example we want to have a dbconsole running on node1 and node2 with agents on node1 reporting to the dbconsole on node1 and agent on node2 and node3 reporting to the dbconsole on node2.

This emca command can be run from any node in the cluster.

According to the documentation and the prompt help we would then run:

$ emca -reconfig dbcontrol -cluster -EM_NODE node2 -EM_SID_LIST EM1112,EM1113 

or

$ emca -reconfig dbcontrol -cluster 
Enter the following information: 
Database unique name: EM111 
Database Control node name (optional): node2 
Agent SID list [comma separated] (optional): EM1112,EM1113

or

$ emca -reconfig dbcontrol -cluster -silent -respfile /u01/app/oracle/admin/EM111/scripts/emca_node2_23.rsp

With content of emca_node2_23.rsp as follows:
DB_UNIQUE_NAME=EM111 
EM_NODE=node2 
EM_SID_LIST=EM1112,EM1113

$emca -displayConfig dbcontrol -cluster 

INFO: 

**************** Current Configuration **************** 

INSTANCE NODE DBCONTROL_UPLOAD_HOST 
---------- ---------- --------------------- 
EM1111 node1 node1.mycompany.com 
EM1112 node2 node2.mycompany.com 
EM1113 node3 node2.mycompany.com

 

IMPORTANT:

1. Starting with 11.2, SCAN listener configuration is mandatory when configuring Database Control in an Oracle RAC environment
    Please check the Document 1188736.1 - How to Setup SCAN Listener and Client for TAF and Load Balancing
2. Starting with 11.2 EMCA, the reconfig command uses the parameter -EM_NODE_LIST instead of -EM_SID_LIST
    Example:
    $ emca -reconfig dbcontrol -cluster -EM_NODE <node1> -EM_NODE_LIST <node1,node2,nodeN>

 

 

Remove an instance from DB Control monitoring

If you plan to remove an instance from the RAC database, you must first remove the instance from the DB Control monitoring.
You can also remove an instance from the DB Control monitoring simply because you are not interested to monitor this particular instance.
Removing an instance from the DB Control monitoring does not remove the instance from the RAC database.

This command can be run from any node in the cluster, except from the node from where runs the instance for which we want to stop the monitoring.
Please refer to:
Note 394445.1 - emca -deleteInst db fails with Database Instance unavailable

For example if we want to stop monitoring the instance on node2, we can run the following command either from node1 or from node3:

$ emca -deleteInst db 
Enter the following information: 
Node name: node2 
Database unique name: EM111 
Database SID: EM1112

The command will:
- update the repository to remove all rows related to the instance
- remove all sub-directories related to the DB Control on the node specified in node name (node2 here)
  - here the following sub-directories will be removed on node2
    $ORACLE_HOME/node1_EM111
    $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node1_EM111
    $ORACLE_HOME/node2_EM111
    $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node2_EM111
    $ORACLE_HOME/node3_EM111
    $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node3_EM111
- remove all sub-directories related to the instance EM1112 on all the other nodes of the cluster
  - here the following sub-directories will be removed on node1 and node3
    $ORACLE_HOME/node2_EM111
    $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node2_EM111
- reconfigure the agents which were reporting to the dbconsole removed if needed. This is what happened in our example:

• here we stopped monitoring the instance EM1112, which dropped the dbconsole on node2
•  however the agent on node3 was reporting to this dbconsole; emca has also reconfigured the agent on node3 to upload to the dbconsole on node1. 
  
  $emca -displayConfig dbcontrol -cluster 
  
  INFO: 
  
  **************** Current Configuration **************** 
  
  INSTANCE NODE DBCONTROL_UPLOAD_HOST 
  ---------- ---------- --------------------- 
  EM1111 node1 node1.mycompany.com 
  EM1113 node3 node1.mycompany.com

Log files
The log files are only created on the local node (the node from which emca has been run).
emca log files for an instance operation (delete instance) are logged in:
RDBMS $ORACLE_BASE/cfgtoollogs/emca/EM111/EM1112
A new sub-directory is created, if it does not exists, to log emca operations at instance level, named with the SID on which the operation was performed.

Add an instance to DB Control monitoring

If you have added an instance to the RAC database and if you plan to monitor it with the DB Control, you must add the instance to the DB Control monitoring:

$ emca -addInst db 
Enter the following information: 
Node name: node2 
Database unique name: EM111 
Database SID: EM1112

This emca command will:
- update the repository to add all rows related to the instance
- add all sub-directories related to DB Control on the node specified in node name (node2 here)
- here the following sub-directories will be created on node2
  $ORACLE_HOME/node1_EM111
  $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node1_EM111
  $ORACLE_HOME/node2_EM111
  $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node2_EM111
  $ORACLE_HOME/node3_EM111
  $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node3_EM111
- all sub-directories related to the instance EM1112 on all the nodes of the cluster
- here the following sub-directories will be added on node1 and node3
  $ORACLE_HOME/node2_EM111
  $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node2_EM111

$ emca -displayConfig dbcontrol -cluster 

INFO: 

**************** Current Configuration **************** 

INSTANCE NODE DBCONTROL_UPLOAD_HOST 
---------- ---------- --------------------- 
EM1111 node1 node1.mycompany.com 
EM1112 node2 node1.mycompany.com 
EM1113 node3 node1.mycompany.com

Log files
The log files are only created on the local node (the node from which emca has been run).
emca log files for an instance operation (add instance) are logged in:
RDBMS $ORACLE_BASE/cfgtoollogs/emca/EM111/EM1112
A new sub-directory is created, if it does not exist, to log emca operations at instance level, named with the SID on which the operation was performed.

Drop the DB Control keeping the repository

This commands is used to drop the Dbconsole configuration files ONLY (the Dbconsole Repository objects are not removed).

$ emca -deconfig dbcontrol db -cluster 
Enter the following information: 
- Database unique name

This emca command does the following:
- stop the DB Control (dbconsole, agent) on all nodes of the cluster
- remove all DB Control related directories on all nodes of the cluster
  $ORACLE_HOME/node1_EM111
  $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node1_EM111
  $ORACLE_HOME/node2_EM111
  $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node2_EM111
  $ORACLE_HOME/node3_EM111
  $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node3_EM111

The repository has not been dropped.
You can then if needed recreate the DBControl without recreating the repository.

DB Control deconfiguration removing the repository

This commands is used to drop the Dbconsole configuration files AND the Dbconsole Repository objects.

$ emca -deconfig dbcontrol db -repos drop -cluster 
Enter the following information: 
Database unique name: EM111 
Listener port number: 1521 
Password for SYS user: 
Password for SYSMAN user:

This emca command does the following:
- stop the DB Control (dbconsole, agent) on all nodes of the cluster
- remove all DB Control related directories on all nodes of the cluster   
   $ORACLE_HOME/node1_EM111
   $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node1_EM111
   $ORACLE_HOME/node2_EM1112
   $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node2_EM111
   $ORACLE_HOME/node3_EM111
   $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_node3_EM111
- drop the repository
  The command (one line) launched by emca to drop the repository once the DB Control is dropped
   is: 
   /oracle/app/oracle/product/10.2.0/db/sysman/admin/emdrep/bin/RepManager -connect (DESCRIPTION=
  ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1vip)
  (PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=ukp79142vip)(PORT=1521))
  (ADDRESS=(PROTOCOL=TCP)(HOST=node3vip)(PORT=1521))(LOAD_BALANCE=yes))
  (CONNECT_DATA=(SERVICE_NAME=EM111)))
  -repos_user SYSMAN -action drop -verbose 
  -output_file /oracle/app/oracle/cfgtoollogs/emca/EM111/emca_repos_drop_2006-10-13_01-03-03-PM.log

Log files
The log files are only created on the local node (the node from which emca has been run).
The log file for DBControl configuration/setup and deployment is emca_timestamp.log
The log file for DB Control repository drop is emca_repos_drop_timestamp.log

REFERENCES

NOTE:278100.1 - How To Drop, Create And Recreate the Database Control (DB Control) Release 10g and 11g
NOTE:330689.1 - How to Trace / Debug the EMCA Tool in 10g and 11g
NOTE:394445.1 - Problem: emca -deleteInst db fails with Database Instance unavailable
NOTE:395162.1 - How to manage DB Control 10.2 for RAC Database with emca
NOTE:1188736.1 - How to Setup SCAN Listener and Client for TAF and Load Balancing [Video]
NOTE:1092753.1 - How To Configure Scan Listeners With A TCPS Port?
NOTE:1448841.1 - Step by Step Guide: How to Configure SSL / TCPS on ORACLE 11.2 RAC with SCAN