SQLcl

Using Oracle SQLcl with Oracle Database Exadata Express Cloud Service

Connecting with Oracle SQLcl

Oracle SQL Developer Command-Line (SQLcl) can connect to Oracle Database Exadata Express Cloud Service. Security is enforced by using an Oracle Wallet, which can be downloaded from the database service. Steps to do this and run SQLcl are shown below.

Prerequisites:

  • SQLcl is a Java application and requires a Java Runtime Engine (JRE) version 8 or higher (download)
  • The Oracle Wallet requires Java Cryptography Extension (JCE) Unlimited Strength support, which is provided automatically using JRE 8 update 161 and higher. 
Java Runtime Engine (JRE)


Ensure your machine has Java installed and available. You can test this in a terminal like:

c:\\sqlcll\bin>java -version
java version "1.8.0_161"
Java(TM) SE Runtime Environment (build 1.8.0_161)

If you do not get a version of 1.8 or higher back, confirm you have Java installed and in your PATH. Otherwise download the appropriate JRE for your Operating System and platform and install it.

Using Older Versions of Java 8

If you are running a JRE older than 8 update 161, download the Java Cryptography Extension and extract the two jar files to the JRE directory as documented in the README.txt. If this pre-requisite is not satisfied, SQLcl will detect it and prompt you to add the required files to your Java installation.

 

1. Download SQLcl

  • Obtain SQLcl by downloading the ZIP archive:

  • Unzip the packages into the desired application directory, for example /home/user/sqlcl or C:\sqlcl

  • On Windows, append C:\sqlcl\bin to the PATH variable in the "System variables" section of the Environment Variables pane. On Windows 8 this can be accessed by navigating to Control Panel>System>Advanced System Settings>Environment Variables

2. Enable Oracle Network Connectivity and Download the Client Wallet

  • In the Exadata Express console Enable SQL*Net access.

  • Download the Oracle Wallet that will allow access to Exadata Express.

  • Unzip the client wallet client_credentials.zip file and move the contents to a directory. For example move the files to /home/user/sqlcl/bin or C:\sqlcl\bin.

    Store the Oracle Wallets and JKS files (*.sso, *.p12, *.jks) securely so that only users who are authorized to connect to the Exadata Express service have access to them. By default, Oracle recommends granting permissions only to the owner of the files.

     

3. Run SQLcl and Configure the Wallet

  • Start SQLcl without a connection using the /nolog flag and configure the wallet like:

    sql /nolog
    SQL>set cloudconfig wallet.zip -- where wallet.zip is the name of the wallet zip file, include the directory location if necessary
    Using TEMP directory: C:\Users\User\AppData\Local\Temp\oracle_cloud_config108293874592847976/keystore.jks
  • Connect to your service using your username and password and the service name 'dbaccess' like:
    SQL>connect pdb_admin/Welcome1!@dbaccess
    SQL>Connected.

Related Technologies

Other Developer Resources