Oracle Database - Personal Edition - Version 10.1.0.5 and later Oracle Database - Standard Edition - Version 10.1.0.5 and later Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later Oracle Database Cloud Exadata Service - Version N/A and later Oracle Database Backup Service - Version N/A and later. Oracle VM VirtualBox on 32-bit and 64-bit PCs. This download is licensed as freeware for the Windows (32-bit and 64-bit) operating system on a laptop or desktop PC from computer utilities without restrictions. VirtualBox 6.1.0 is available to all software users as a free download for Windows 10 PCs but also without a hitch on Windows 7.
SQL*Plus Instant Client is a standalone product with all the functionality of SQL*Plus command-line. It connects to existing remote Oracle databases, but does not include its own database. It is easy to install and uses significantly less disk space than the full Oracle Database Client installation required to use SQL*Plus command-line.
SQLPro supports many database types including MySQL (and MariaDB), Postgres/PostgreSQL, Redshift, Microsoft SQL Server (2005 and above), Oracle (8i and above), SQLite and SnowflakeDB. Best at the basics. Table creation, custom queries, auto-complete and syntax highlighting are just some of the features you can expect. Updating or designing a table? Oracle ADO.NET Entity Framework supports features of Entity Framework 6.0; Oracle Entity Framework data providers now require Entity Framework 6.0. Database Support. Oracle 19c; Oracle 18c; Oracle 12c R1, R2 (12.1, 12.2) Oracle 11g R1, R2 (11.1, 11.2) Oracle 10g R1, R2 (10.1, 10.2) Oracle 9i R1, R2 (9.0.1, 9.2) Programming Support.
SQL*Plus Instant Client is available on platforms that support the OCI Instant Client. See the Oracle Call Interface Programmer's Guide for more information on the OCI Instant Client.
To install SQL*Plus Instant Client, you need two packages:
SQL*Plus Instant Client package.
Either the Basic OCI Instant Client package, or the lightweight OCI Instant Client package.
Choosing the SQL*Plus Instant Client to Install
SQL*Plus Instant Client can be installed in two ways:
Download the packages from the Oracle Technology Network (OTN).
Copy the same files that are in the packages from an Oracle Database 11g Client Administrator installation.
Both the SQL*Plus and OCI packages must be from the same Oracle Database version, for example, 11.1.0.6.
Basic Instant Client
SQL*Plus Instant Client using the Basic OCI package works with any NLS_LANG setting supported by the Oracle Database. It supports all character sets and language settings available in the Oracle Database.
Lightweight Instant Client
SQL*Plus Instant Client using the lightweight OCI package displays error messages in English only and supports only specific character sets. It is significantly smaller than SQL*Plus Instant Client using the Basic OCI package.
Valid values for NLS_LANG parameters with the lightweight Instant Client are:
language can be any valid language supported by the Oracle Database, however, error messages are only reported in English.
territory can be any valid territory supported by the Oracle Database.
charset is one of the following character sets:
US7ASCII
WE8DEC
WE8MSWIN1252
WE8ISO8859P1
UTF8
AL16UTF16
AL32UTF8
For example:
See the Oracle Database Globalization Support Guide, and NLS_LANG Environment Variable for more information about NLS settings.
Lightweight SQL*Plus Instant Client Error with Unsupported Character Set
Attempting to start SQL*Plus Instant Client with an unsupported character set will fail with the following error:
Installing SQL*Plus Instant Client by Downloading from OTN
The OTN downloads for Linux are RPM packages. The OTN downloads for UNIX and Windows are zip files.
The SQL*Plus Instant Client package should never be installed on an ORACLE_HOME.
Installing SQL*Plus Instant Client from Linux RPM Packages
Download the RPM packages containing the SQL*Plus Instant Client package, and the OCI package from the OTN Instant Client page at
http://www.oracle.com/technology/tech/oci/instantclient/instantclient.html. Both packages must be from the same version such as 11.1.0.6.Use rpm -i for the initial install of the RPM packages, or rpm -u to upgrade to a newer version of the packages.
Configure SQL*Plus Instant Client. See Configuring SQL*Plus Instant Client.
Installing SQL*Plus Instant Client from the UNIX or Windows Zip Files
Download the zip files containing the SQL*Plus Instant Client package, and the OCI package from the OTN Instant Client page at
http://www.oracle.com/technology/tech/oci/instantclient/instantclient.html. Both packages must be from the same version such as 11.1.0.6.Create a new directory, for example, /home/instantclient11_1 on UNIX or c:instantclient11_1 on Windows.
Unzip the two packages into the new directory.
Configure SQL*Plus Instant Client. See Configuring SQL*Plus Instant Client.
List of Files Required for SQL*Plus Instant Client
Tables E-1, E-2 and E-3 list the required files from each of the SQL*Plus and OCI packages. The files from only one of the OCI packages are required. Other files installed that are not listed here can be ignored, or can be removed to save disk space.
Table D-1 Instant Client Files in the SQL*Plus Package
| Linux and UNIX | Windows | Description |
|---|---|---|
sqlplus | sqlplus.exe | SQL*Plus executable |
libsqlplus.so | not applicable | SQL*Plus library |
libsqlplusic.so | orasqlplusic11.dll | SQL*Plus data shared library |
Table D-2 Instant Client Files in the Basic OCI Package
| Linux and UNIX | Windows | Description |
|---|---|---|
libclntsh.so.11.1 | oci.dll | Client code library |
libociei.so | oraociei11.dll | OCI Instant Client data shared library |
libnnz11.so | orannzsbb11.dll | Security library |
Table D-3 Instant Client Files in the Lightweight OCI Package
| Linux and UNIX | Windows | Description |
|---|---|---|
libclntsh.so.11.1 | oci.dll | Client code library |
libociicus.so | oraociicus11.dll | OCI Instant Client data shared library (English only) |
libnnz11.so | orannzsbb11.dll | Security library |
Installing SQL*Plus Instant Client from the 11g Client Release Media
Run the installer on the Oracle Database 11g Client Release media and choose the Administrator option.
Create a new directory, for example, /home/instantclient11_1 on UNIX and Linux, or c:instantclient11_1 on Windows.
Copy the SQL*Plus Instant Client and the OCI Instant Client files to the new directory. All files must be copied from the same ORACLE_HOME.
See Installing SQL*Plus Instant Client on UNIX or Linux or Installing SQL*Plus Instant Client on Windows for a list of the files to copy.
Configure SQL*Plus Instant Client. See Configuring SQL*Plus Instant Client.
Installing SQL*Plus Instant Client on UNIX or Linux
To install SQL*Plus Instant Client using the Basic OCI package on UNIX and Linux, copy the following files:
To install SQL*Plus Instant Client using the lightweight OCI package on UNIX and Linux, copy the following files:
Installing SQL*Plus Instant Client on Windows
To install SQL*Plus Instant Client using the Basic OCI package on Windows, copy the following files:
To install SQL*Plus Instant Client using the lightweight OCI package on Windows, copy the following files:
Configuring SQL*Plus Instant Client
The SQL*Plus Instant Client executable should only be used with the matching version of the OCI Instant Client.
Note that no ORACLE_HOME or ORACLE_SID environment variables need to be set.
Configuring SQL*Plus Instant Client on Linux (from RPMs)
The RPMs downloaded from OTN install into Oracle specific sub-directories in the /usr file system. The sub-directory structure enables multiple versions of Instant Client to be available.
Add the name of the directory containing the Instant Client libraries to LD_LIBRARY_PATH. Remove any other Oracle directories.
For example, to set LD_LIBRARY_PATH on Solaris in the Bourne or Korn shells:
Make sure the sqlplus executable installed from the RPM is the first found in your PATH. To test, enter which sqlplus which should return /usr/bin/sqlplus. If not, remove any other Oracle directories from PATH, or put /usr/bin before other SQL*Plus executables in PATH, or use an absolute or relative path to start SQL*Plus.
For example, to set PATH in the bash shell:
If you install multiple versions of SQL*Plus, you may need to change the symbolic link /usr/bin/sqlplus to the version of SQL*Plus matching the libraries in LD_LIBRARY_PATH. For 11.1.0.6, /usr/bin/sqlplus is a symbolic link to the SQL*Plus binary at /usr/lib/oracle/11.1.0.6/client/bin/sqlplus.
Set Oracle globalization variables required for your locale. A default locale will be assumed if no variables are set. See the Oracle Database Globalization Support Guide for more information.
For example:
Configuring SQL*Plus Instant Client on Linux (from Client Media or Zip File) and UNIX
Add the name of the directory containing the Instant Client files to the appropriate shared library path LD_LIBRARY_PATH, LIBPATH or SHLIB_PATH. Remove any other Oracle directories.
For example on Solaris in the Bourne or Korn shells:
Add the directory containing the Instant Client files to the PATH environment variable. If it is not set, then an absolute or relative path must be used to start SQL*Plus. Remove any other Oracle directories from PATH. For example:
Set Oracle globalization variables required for your locale. A default locale will be assumed if no variables are set. See the Oracle Database Globalization Support Guide for more information.
For example:
Configuring SQL*Plus Instant Client on Windows
The environment may be configured using SET commands in a Windows command prompt or made permanent by setting Environment Variables in System Properties.
For example, to set environment variables in Windows 2000 using System Properties, open System from the Control Panel, click the Advanced tab and then click Environment Variables.
Add the directory containing the Instant Client files to the PATH system environment variable. Remove any other Oracle directories from PATH.
For example, add c:instantclient11_1 to the beginning of PATH.
Set Oracle globalization variables required for your locale. A default locale will be assumed if no variables are set. See the Oracle Database Globalization Support Guide for more information. For example, to set NLS_LANG for a Japanese environment, create a user environment variable NLS_LANG set to JAPANESE_JAPAN.JA16EUC.
If you have installed the lightweight Instant Client, see Lightweight Instant Client for information about supported NLS_LANG settings.
Connecting to a Database with SQL*Plus Instant Client
SQL*Plus Instant Client is always 'remote' from any database server. To connect to a database you must specify the database using an Oracle Net connection identifier.
An example using an Easy Connection identifier to connect to the HR schema in the MYDB database running on mymachine is:
Alternatively you can use a Net Service Name:
Net Service Names can be stored in a number of places, including LDAP. The use of LDAP is recommended to take advantage of the new features of Oracle Database 11g. See the Oracle Database Net Services Reference for more information.
If you want to use Net Service Names configured in a local Oracle Net tnsnames.ora file, then set the environment variable TNS_ADMIN to the directory containing the tnsnames.ora file. For example, on UNIX, if your tnsnames.ora file is in /home/user1 and it defines the Net Service Name MYDB2:
If TNS_ADMIN is not set, then an operating system dependent set of directories is examined to find tnsnames.ora. This search path includes looking in the directory specified by the ORACLE_HOME environment variable for network/admin/tnsnames.ora. This is the only reason to set the ORACLE_HOME environment variable for SQL*Plus Instant Client. If ORACLE_HOME is set when running Instant Client applications, it must be set to a directory that exists.
This example assumes the ORACLE_HOME environment variable is set, and the $ORACLE_HOME/network/admin/tnsnames.ora or ORACLE_HOMEnetworkadmintnsnames.ora file defines the Net Service Name MYDB3:
Sqlpro For Oracle 1 0 64
The TWO_TASK (on UNIX) or LOCAL (on Windows) environment variable can be set to a connection identifier. This removes the need to explicitly enter the connection identifier whenever a connection is made in SQL*Plus or SQL*Plus Instant Client. This UNIX example connects to the database known as MYDB4:
On Windows, TNS_ADMIN and LOCAL may be set in the System Properties. See Configuring SQL*Plus Instant Client on Windows.
AS SYSDBA or AS SYSOPER Connections with SQL*Plus Instant Client
To connect AS SYSDBA or AS SYSOPER to perform DBA tasks, you need to set up an Oracle password file on the database server using the database's orapwd utility. Once this is configured, your SQL*Plus Instant Client connection string might look something like:
Sqlpro For Oracle 1 0 6 Months
See the Oracle Database Administrator's Guide for information on Oracle password files.
Uninstalling Instant Client
The SQL*Plus Instant Client package can be removed separately from the OCI Instant Client. After uninstalling the SQL*Plus Instant Client package, the remaining OCI Instant Client libraries enable custom written OCI programs or third party database utilities to connect to a database.
Uninstalling SQL*Plus Instant Client
For installations on Linux from RPM packages, use rpm -e only on the SQL*Plus Instant Client package
or
For installations on UNIX and Windows, and installations on Linux from the Client Release media, manually remove the following SQL*Plus specific files:
Table D-4 Instant Client Files in the SQL*Plus Package
UNIX Windows Description sqlplus
sqlplus.exe
SQL*Plus executable
libsqlplus.so
not applicable
SQL*Plus library
libsqlplusic.so
orasqlplusic11.dll
SQL*Plus data shared library
Reset environment variables and remove tnsnames.ora if necessary.
Uninstalling the Complete Instant Client
For installations on Linux from RPM packages, use rpm -qa to find the SQL*Plus Instant Client and Basic OCI package names and run rpm -e to remove them
or
For installations on UNIX and Windows, and installations on Linux from the Client Release media, manually delete the directory containing the SQL*Plus executable and Oracle libraries.
See Installing SQL*Plus Instant Client from the 11g Client Release Media for a list of the files you copied to the directory.
Reset environment variables such as PATH, SQLPATH, LD_LIBRARY_PATH and TNS_ADMIN.
Remove tnsnames.ora if necessary.
Features
Sqlpro For Oracle 1 0 60
Easily installed from PyPI.
Support for Python 3.5 and higher. Older versions of cx_Oracle may be used with previous Python releases.
Support for Oracle Client 11.2, 12, 18 and 19. Oracle's standard cross-version interoperability, allows easy upgrades and connectivity to different Oracle Database versions.
Connect to Oracle Database 9.2, 10, 11, 12, 18 or 19 (depending on the Oracle Client version used). Adobe audition cc 2019 12 1 0 182.
SQL and PL/SQL Execution. The underlying Oracle Client libraries have significant optimizations including compressed fetch, pre-fetching, client and server result set caching, and statement caching with auto-tuning.
Full use of Oracle Network Service infrastructure, including encrypted network traffic and security features.
Extensive Oracle data type support, including large object support (CLOB and BLOB).
Direct binding to SQL objects. One great use case is binding Python objects to Oracle Spatial SDO objects.
SODA (Simple Oracle Document Access)
Array operations for efficient INSERT and UPDATEs.
Array row counts and batch error handling for array operations.
Fetching of large result sets.
REF CURSOR support.
Support for scrollable cursors. Go back and forth through your query results.
Fetch PL/SQL Implicit Results. Easily return query results from PL/SQL.
Row Prefetching. Efficient use of the network.
Client Result Caching. Improve performance of frequently executed look-up statements.
Support for Advanced Queuing. Use database notifications to build micro-service applications.
Continuous Query Notification (CQN). Get notified when data changes.
Support for Edition Based Redefinition. Easily switch applications to use updated PL/SQL logic.
Support for setting application context during the creation of a connection, making application metadata more accessible to the database, including in LOGON triggers.
End-to-end monitoring and tracing.
Transaction Management.
Session Pooling, with tagging and session state fix-up callback.
Database Resident Connection Pooling (DRCP).
Privileged Connections.
External Authentication.
Database startup and shutdown.
Sharded Databases.
Oracle Database High Availability Features, such as FAN notifications and Transaction Guard support.
DB API specification exclusions: The time data type is not supported by Oracle and is therefore not implemented. The method cursor.nextset() is not implemented either as the DB API specification assumes an implementation of cursors that does not fit well with Oracle's implementation of cursors and implicit results. See the method cursor.getimplicitresults() for more information.
