SQLcl is a command-line interface used to enter SQL commands. SQLcl connects to an Oracle database.
You can use SQLcl version 4.2 or later with Autonomous Data Warehouse. Download SQLcl from oracle.com.
SQLcl can connect to the Autonomous Data Warehouse using either an Oracle Call Interface (OCI) or a JDBC thin connection.
If you use Oracle Call Interface (OCI), prepare for OCI, ODBC and JDBC OCI Connections. See Prepare for Oracle Call Interface (OCI), ODBC, and JDBC OCI Connections.
If you use JDBC Thin, prepare for JDBC Thin Connections. See Prepare for JDBC Thin Connections.
SQLcl with Oracle Call Interface
To connect using Oracle Call Interface, use the
–oci option, supply the database user
name, a password, and the database service name provided in the
tnsnames.ora file. For example:
sql -oci SQLcl: Release 18.4 Production on Wed Apr 03 15:28:40 2019 Copyright (c) 1982, 2019, Oracle. All rights reserved. Username? (''?) sales_dwh@adwc1_low Password? (**********?) ************** Last Successful login time: Wed Apr 03 2019 15:29:19 -07:00 Connected to: Oracle Database 18c Enterprise Edition Release 18.104.22.168.0 - Production Version 22.214.171.124.0 SQL>
When connecting using Oracle Call Interface, the Oracle Wallet is transparent to SQLcl.
SQLcl with a JDBC Thin Connection
To connect using a JDBC Thin connection, first configure the SQLcl cloud configuration and then connect to the Autonomous Data Warehouse database.
- Start SQLcl with the /nolog option.
- Configure the SQLcl session to use your Oracle Wallet:
SQL> set cloudconfig directory/client_credentials.zip Wallet Password: **********
- Connect to the Autonomous Data Warehouse database:
SQL> connect username@servicename password
sql /nolog SQLcl: Release 18.4 Production on Thu Jan 24 11:29:41 2019 Copyright (c) 1982, 2019, Oracle. All rights reserved.
SQL> set cloudconfig /home/adwc/wallet_ADWC1.zip Wallet Password: ********** SQL> connect admin@adwc1_medium
Note:If you are connecting to an Autonomous Data Warehouse database using Microsoft Active Directory credentials, then connect using an Active Directory user name in the form of "AD_domain\AD_username" (double quotes must be included), and Active Directory user password. See Use Microsoft Active Directory with Autonomous Database for more information.
For more information, on the connection types specified in
tnsnames.ora, see Managing Concurrency and Priorities on Autonomous Data Warehouse.
For information on SQLcl, see Oracle SQLcl.