Connect to the Oracle Exadata Database Service on Cloud@Customer Service
Learn how to connect to an Oracle Exadata Database Service on Cloud@Customer system using SSH, and how to connect to an Exadata Cloud@Customer database using Oracle Net Services (SQL*Net).
- Connecting to a Virtual Machine with SSH
You can connect to the virtual machines in an Oracle Exadata Database Service on Cloud@Customer system by using a Secure Shell (SSH) connection. - Connecting to a Database with Oracle Net Services
You can connect to the virtual machines in an Oracle Exadata Database Service on Cloud@Customer system using Oracle Net Services.
Parent topic: How-to Guides
Connecting to a Virtual Machine with SSH
You can connect to the virtual machines in an Oracle Exadata Database Service on Cloud@Customer system by using a Secure Shell (SSH) connection.
Most Unix-style systems (including Linux, Oracle Solaris, and macOS) include an SSH client. For Microsoft Windows systems, you can download a free SSH client called PuTTY from the following site: "http://www.putty.org".
- Prerequisites for Connecting to an Oracle Exadata Database Service on Cloud@Customer System
To access a virtual machine in an Oracle Exadata Database Service on Cloud@Customer system using SSH, be prepared to provide the host name or IP address of the virtual machine. - Connecting to a Virtual Machine from a Microsoft Windows System Using PuTTY
Learn to access a virtual machine from a Microsoft Windows system using PuTTY. - Connecting from a Unix-Style System
To access a virtual machine on an Oracle Oracle Exadata Database Service on Cloud@Customer system from a Unix-style system using SSH, use this procedure. - Accessing a Database After You Connect to the Virtual Machine
After you connect to a virtual machine, you can use the following series of commands to identify a database and connect to it.
Related Topics
Prerequisites for Connecting to an Oracle Exadata Database Service on Cloud@Customer System
To access a virtual machine in an Oracle Exadata Database Service on Cloud@Customer system using SSH, be prepared to provide the host name or IP address of the virtual machine.
- An SSH private key file that corresponds to a public key that is registered in the system.
When you create a VM cluster on your Oracle Exadata Database Service on Cloud@Customer system, you must specify the public key portion of one or more SSH key pairs. You can also register extra keys separately after you create the VM cluster.
Note
The public keys are stored in theauthorized_keys
file at~/.ssh/authorized_keys
. Separateauthorized_keys
files are located under the home directories of the operating system users. By default, only theopc
user account has an authorized_keys entry and is able to log in remotely. Do not remove or alter the automatically generated entry inauthorized_keys
for theopc
user. - The host name or IP address for the virtual machine that you
want to access.
See, Using the Console to Check the Status of a VM Cluster Virtual Machine.
Parent topic: Connecting to a Virtual Machine with SSH
Connecting to a Virtual Machine from a Microsoft Windows System Using PuTTY
Learn to access a virtual machine from a Microsoft Windows system using PuTTY.
Before you begin
-
The IP address of the virtual machine
-
The SSH private key file that matches the public key associated with the deployment. This private key file must be in the PuTTY
.ppk
format. If the private key file was originally created on the Linux platform, you can use the PuTTYgen program to convert it to the.ppk
format.
To connect to a virtual machine using the PuTTY program on Windows:
Parent topic: Connecting to a Virtual Machine with SSH
Connecting from a Unix-Style System
To access a virtual machine on an Oracle Oracle Exadata Database Service on Cloud@Customer system from a Unix-style system using SSH, use this procedure.
Parent topic: Connecting to a Virtual Machine with SSH
Accessing a Database After You Connect to the Virtual Machine
After you connect to a virtual machine, you can use the following series of commands to identify a database and connect to it.
Parent topic: Connecting to a Virtual Machine with SSH
Connecting to a Database with Oracle Net Services
You can connect to the virtual machines in an Oracle Exadata Database Service on Cloud@Customer system using Oracle Net Services.
- Using Oracle Net Services to Connect to a Database
Oracle Database Oracle Exadata Database Service on Cloud@Customer supports remote database access by using Oracle Net Services. - Prerequisites for Connecting to a Database with Oracle Net Services
Review the prerequisites to connect to an Oracle Database instance on Oracle Oracle Exadata Database Service on Cloud@Customer using Oracle Net Services. - Connecting to a Database Using SCAN
To create an Oracle Net Services connection by using the SCAN listeners, you can choose between two approaches. - Connecting to a Database Using a Node Listener
To connect to an Oracle Database instance on Oracle Exadata Database Service on Cloud@Customer with a connect descriptor that bypasses the SCAN listeners, use this procedure to route your connection directly to a node listener.
Using Oracle Net Services to Connect to a Database
Oracle Database Oracle Exadata Database Service on Cloud@Customer supports remote database access by using Oracle Net Services.
Because Oracle Exadata Database Service on Cloud@Customer uses Oracle Grid Infrastructure, you can make Oracle Net Services connections by using Single Client Access Name (SCAN) connections. SCAN is a feature that provides a consistent mechanism for clients to access the Oracle Database instances running in a cluster.
By default, the SCAN is associated with three virtual IP addresses (VIPs). Each SCAN VIP is also associated with a SCAN listener that provides a connection endpoint for Oracle Database connections using Oracle Net Services. To maximize availability, Oracle Grid Infrastructure distributes the SCAN VIPs and SCAN listeners across the available cluster nodes. In addition, if there is a node shutdown or failure, then the SCAN VIPs and SCAN listeners are automatically migrated to a surviving node. By using SCAN connections, you enhance the ability of Oracle Database clients to have a reliable set of connection endpoints that can service all of the databases running in the cluster.
The SCAN listeners are in addition to the Oracle Net Listeners that run on every node in the cluster, which are also known as the node listeners. When an Oracle Net Services connection comes through a SCAN connection, the SCAN listener routes the connection to one of the node listeners, and plays no further part in the connection. A combination of factors, including listener availability, database instance placement, and workload distribution, determines which node listener receives each connection.
This documentation provides basic requirements for connecting to your Oracle Exadata Database Service on Cloud@Customer databases by using Oracle Net Services.
Parent topic: Connecting to a Database with Oracle Net Services
Prerequisites for Connecting to a Database with Oracle Net Services
Review the prerequisites to connect to an Oracle Database instance on Oracle Oracle Exadata Database Service on Cloud@Customer using Oracle Net Services.
- The IP addresses for your SCAN VIPs, or the hostname or IP address for a virtual machine that hosts the database that you want to access.
- The database identifier: Either the database system identifier (SID), or a service name.
Parent topic: Connecting to a Database with Oracle Net Services
Connecting to a Database Using SCAN
To create an Oracle Net Services connection by using the SCAN listeners, you can choose between two approaches.
- Connecting to a Database Using a Connect Descriptor that References All of the SCAN VIPs
You can set up a connect descriptor for Oracle Exadata Database Service on Cloud@Customer System using multiple SCAN listeners. - Connecting to a Database Use a Connect Descriptor that References a Custom SCAN Name
You can set up a connect descriptor for Oracle Exadata Database Service on Cloud@Customer System using a custom SCAN name.
Parent topic: Connecting to a Database with Oracle Net Services
Connecting to a Database Using a Connect Descriptor that References All of the SCAN VIPs
You can set up a connect descriptor for Oracle Exadata Database Service on Cloud@Customer System using multiple SCAN listeners.
This approach requires you to supply all of the single client access name (SCAN) virtual IP (VIP) addresses, and enables Oracle Net Services to connect to an available SCAN listener.
Parent topic: Connecting to a Database Using SCAN
Connecting to a Database Use a Connect Descriptor that References a Custom SCAN Name
You can set up a connect descriptor for Oracle Exadata Database Service on Cloud@Customer System using a custom SCAN name.
Using this approach, you define a custom single client access name (SCAN) name in your domain name server (DNS), which resolves to the three SCAN virtual IP addresses (VIPs).
Parent topic: Connecting to a Database Using SCAN
Connecting to a Database Using a Node Listener
To connect to an Oracle Database instance on Oracle Exadata Database Service on Cloud@Customer with a connect descriptor that bypasses the SCAN listeners, use this procedure to route your connection directly to a node listener.
By using this method, you give up the high-availability and load-balancing provided by SCAN. However, this method may be desirable if you want to direct connections to a specific node or network interface. For example, you might want to ensure that connections from a program that performs bulk data loading use the backup network.
Using this approach, you direct your connection using the hostname or IP address of the node.
Example 5-1 Defining a Net Service Alias That Directly References the Node
alias-name = (DESCRIPTION=
(CONNECT_TIMEOUT=timeout)
(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=node)(PORT=1521)))
(CONNECT_DATA=(sid-or-service-entry)))
Where:
alias-name
is the name you use to identify the alias.
timeout
specifies a timeout period (in seconds), which enables you to
terminate a connection attempt without having to wait for a TCP
timeout. The (CONNECT_TIMEOUT=timeout
) parameter is
optional.
node
is the
hostname or IP address for the virtual machine that you want to
use.
sid-or-service-entry
identifies the
database SID or service name using one of the following formats:
SID=sid-name
. For example,SID=S12C1
.SERVICE_NAME=service-name
. For example,SERVICE_NAME=PDB1.example.oraclecloudatcust.com
.
node:1521/sid-or-service-entry
exa1node01.example.com:1521/S12C1
exa1node01.example.com:1521/PDB1.example.oraclecloudatcust.com
Parent topic: Connecting to a Database with Oracle Net Services