Private Source Limitations - SCAN

Oracle Analytics Cloud can't access private data sources on an Oracle Database that uses a Single Client Access Name (SCAN) with the TCP/IP with SSL protocol (TCPS). If you want to use TCPS to access an Oracle Database that uses a SCAN, use one of the following methods to set up the connection in Oracle Analytics Cloud:

• Configure the data source connection using the Advanced Connection String option and connect directly to the Oracle Database nodes, instead of SCAN.

  For example:

  (DESCRIPTION=(ENABLE=BROKEN)
   (ADDRESS_LIST=(LOAD_BALANCE=on)(FAILOVER=ON)
     (ADDRESS=(PROTOCOL=tcps)(HOST=<DB Node 1 FQDN Host Name>)(PORT=2484))
     (ADDRESS=(PROTOCOL=tcps)(HOST=<DB Node 2 FQDN Host Name>)(PORT=2484)))
   (CONNECT_DATA=
     (SERVICE_NAME=<DB Service Name>))
     (SECURITY=(SSL_SERVER_CERT_DN="CN=<DB Server Certificate DN>")))

  Where the distinguished name (DN) might look something like: (SECURITY=(SSL_SERVER_CERT_DN="CN=host-example-scan.mysubnet.exadatainfrastr.oraclevcn.com"))

  The way you configure this connection string depends how many database hosts are active at the same time:

  • If more than one database host is active at the same time, set (LOAD_BALANCE=on) in the connection string above.

  • If only one database host is active at a time, set (LOAD_BALANCE=off) in the connection string. To optimize performance, include the ADDRESS of the active database host first in the ADDRESS_LIST.

    To find out which database host is active at any given time, refer to the documentation for your database. For example, for Oracle Database you can use V$INSTANCE.

• Configure an Oracle Connection Manager in front of SCAN and then configure a data source connection in Oracle Analytics Cloud that connects to the Oracle Connection Manager endpoint.