Sql oracle free download - SQL Assistant for Oracle, SQL PathFinder for Oracle, Oracle SQL Handler, and many more programs. This video contains a total demonstration of how to connect to oracle 12c release 1 on Oracle linux server 6.4 64 bit from MAC OSX Mountain Lion 7.0 using SQ. Oracle SQL Developer is a free, integrated development environment that simplifies the development and management of Oracle Database in both traditional and Cloud deployments. SQL Developer offers complete end-to-end development of your PL/SQL applications, a worksheet for running queries and scripts, a DBA console for managing the database, a. MySQL Cluster CGE. MySQL Cluster is a real-time open source transactional database designed for fast, always-on access to data under high throughput conditions.
- Free Sql Plus
- Oracle Sql Plus Download Mac Iso
- Oracle Sql Plus Download Dba
- Sql Plus App Download
- Oracle Sql Plus Download Mac Installer
- Sql Plus Download Free
- Oracle Sql Plus Download Mac Download
This chapter explains how to configure your SQL*Plus command-line environment. It has the following topics:
2.1 SQL*Plus Environment Variables
These environment variables specify the location or path of files used by SQL*Plus. For other environment variables that influence the behavior of SQL*Plus, see the Oracle Database Administrator's Reference.
Table 2-1 Parameters or Environment Variables influencing SQL*Plus
Parameter or Variable | Description |
---|---|
LD_LIBRARY_PATH | Environment variable to specify the path used to search for libraries on UNIX and Linux. The environment variable may have a different name on some operating systems, such as DYLD_LIBRARY_PATH on Apple Mac OS, LIBPATH on IBM/AIX-5L, and SHLIB_PATH on HP-UX. Not applicable to Windows operating systems. Example |
LOCAL | Windows environment variable to specify a connection string. Performs the same function as TWO_TASK on UNIX. |
NLS_LANG | Environment variable to specify globalization behavior. Example |
ORACLE_HOME | Environment variable to specify where SQL*Plus is installed. It is also used by SQL*Plus to specify where message files are located. Examples: |
ORA_EDITION | Environment variable to specify the database edition to use. If you specify the edition with the CONNECT or SQLPLUS command option, edition=value, it is used instead of ORA_EDITION. If no edition is specified in either the CONNECT or SQLPLUS command option, or in ORA_EDITION, SQL*Plus connects to the default edition. When ORA_EDITION is set, a subsequent STARTUP command in the session results in an ORA-38802 error. To correct this, you must unset ORA_EDITION, then reconnect and shutdown the database, then start the database again. |
ORA_NLS10 | Environment variable to specify the locations of the NLS data and the user boot file in SQL*Plus 10.2. The default location is $ORACLE_HOME/nls/data. In a system with both Oracle9i and 10g, or a system under version upgrade, you should set ORA_NLS10 for Oracle 10g and set ORA_NLS33 for 9i. The default NLS location in 9i was $ORACLE_HOME/common/nls/admin/data. |
ORACLE_PATH | Environment variable to specify the location of SQL scripts. If SQL*Plus cannot find the file in ORACLE_PATH, or if ORACLE_PATH is not set, it searches for the file in the current working directory. Not applicable to Windows |
ORACLE_SID | Environment variable to specify the database instance, optional |
PATH | Environment variable to specify the path to search for executables, and DLLs in Windows. Typically includes ORACLE_HOME/bin |
SQLPATH | Environment variable or Windows registry entry to specify the location of SQL scripts. SQL*Plus searches for SQL scripts, including login.sql, in the directories specified by SQLPATH. SQLPATH is a colon-separated list of directories. There is no default value set in UNIX installations. In Windows, SQLPATH is defined in a registry entry during installation. For more information about the SQLPATH registry entry, see SQLPATH Registry Entry. |
TNS_ADMIN | Environment variable to specify the location of the tnsnames.ora file. If not specified, $ORACLE_HOME/network/admin is used Example |
TWO_TASK | UNIX environment variable to specify a connection string. Connections that do not specify a database will connect to the database specified in TWO_TASK. Example is the same as: |
2.1.1 SQLPATH Registry Entry
The SQLPATH registry entry specifies the location of SQL scripts. SQL*Plus searches for SQL scripts in the current directory and then in the directories specified by the SQLPATH registry entry, and in the subdirectories of SQLPATH directories.
The HKEY_LOCAL_MACHINESOFTWAREORACLEHOME0 registry subkey (or the HOMEn directory for the associated ORACLE_HOME) contains the SQLPATH registry entry. SQLPATH is created with a default value of ORACLE_HOMEDBS. You can specify any directories on any drive as valid values for SQLPATH.
When setting the SQLPATH registry entry, you can concatenate directories with a semicolon (;). For example:
c:oracleora12database;c:oracleora12dbs
See the Registry Editor's help system for instructions on how to edit the SQLPATH registry entry.
2.2 SQL*Plus Configuration
You can set up your SQL*Plus environment to use the same settings with each session.
There are two operating system files to do this:
- The Site Profile file, glogin.sql, for site wide settings.
- Additionally, the User Profile, login.sql, sets user specific settings.
The exact names of these files is system dependent.
Note:
The Site Profile and User Profile files are run after a successful Oracle Database connection from a
SQLPLUS
or CONNECT
command, or where /NOLOG
is specified.The Site Profile and User Profile files are not run when you switch to another PDB using ALTER SESSION SET CONTAINER
. Some privileged connections may generate errors if SET SERVEROUTPUT or SET APPINFO commands are put in the Site Profile or User Profile.
The following tables show the profile scripts, and some commands and settings that affect the Command-line user interface.
Table 2-2 Profile Scripts affecting SQL*Plus User Interface Settings
This script ... | is run in the Command-line... |
---|---|
Site Profile (glogin.sql) Can contain any content that can be included in a SQL*Plus script, such as system variable settings or other global settings the DBA wants to implement. | After successful Oracle Database connection from a SQLPLUS or CONNECT command. Where /NOLOG is specified. |
User Profile (login.sql) Can contain any content that can be included in a SQL*Plus script, but the settings are only applicable to the user's sessions. | Immediately after the Site Profile. |
Table 2-3 Commands in Profile scripts affecting SQL*Plus User Interface Settings
In a profile script, this command ... | affects the Command-line by ... |
---|---|
Also see the SQL*Plus Compatibility Matrix. | Setting the SQL*Plus compatibility mode to obtain the behavior the DBA wants for this site. |
SQLPLUS command COMPATIBILITY Option | As for SET SQLPLUSCOMPATIBILITY but set with the SQLPLUS command COMPATIBILITY option. |
SQLPLUS command RESTRICT Option | Starting SQL*Plus with the RESTRICT option set to 3 prevents the User Profile script from being read. |
2.2.1 Site Profile
A Site Profile script is created during installation. It is used by the database administrator to configure site-wide behavior for SQL*Plus Command-line connections. The Site Profile script installed during installation is an empty script.
The Site Profile script is generally named glogin.sql. SQL*Plus executes this script whenever a user starts a SQL*Plus session and successfully establishes the Oracle Database connection.
The Site Profile enables the DBA to set up site wide SQL*Plus environment defaults for all users of a particular SQL*Plus installation
Users cannot directly access the Site Profile.
2.2.1.1 Default Site Profile Script
The Site Profile script is $ORACLE_HOME/sqlplus/admin/glogin.sql in UNIX, and ORACLE_HOMEsqlplusadminglogin.sql in Windows. If a Site Profile already exists at this location, it is overwritten when you install SQL*Plus. If SQL*Plus is removed, the Site Profile script is deleted.
2.2.2 User Profile
For SQL*Plus command-line connections, SQL*Plus also supports a User Profile script. The User Profile is executed after the Site Profile and is intended to allow users to specifically customize their session. The User Profile script is generally named login.sql. SQL*Plus searches for the directories you specify with the ORACLE_PATH environment variable. SQL*Plus searches this colon-separated list of directories and their subdirectories in the order they are listed.
Note:
SQL*Plus will no longer search for login.sql in the current directory. Free Sql Plus
You can add any SQL commands, PL/SQL blocks, or SQL*Plus commands to your user profile. When you start SQL*Plus, it automatically searches for your user profile and runs the commands it contains.
2.2.2.1 Modifying Your LOGIN File
You can modify your LOGIN file just as you would any other script. The following sample User Profile script shows some modifications that you could include:
See Also:
- SET command for more information on these and other SET command variables you may wish to set in your SQL*Plus LOGIN file.
- About Using Predefined Variables for more information about predefined variables.
2.2.3 Storing and Restoring SQL*Plus System Variables
From the Command-line you can store the current SQL*Plus systemvariables in a script with the STORE command. If you alter any variables, this script can be run to restore the original values. This is useful if you want to reset system variables after running a report that alters them. You could also include the script in your User Profile script so that these system variables are set each time you start SQL*Plus.
To store the current setting of all system variables, enter
Enter a file name and file extension, or enter only the file name to use the default extension .SQL. You can use theSET SUF[FIX] {SQL | text} command to change the default file extension.
2.2.3.1 Restoring the System Variables
To restore the stored system variables, enter
If the file has the default extension (as specified by the SET SUF[FIX] {SQL | text} command), you do not need to add the period and extension to the file name.
You can also use the @ (at sign) or the @@ (double at sign) commands to run the script.
Now the value of any system variable can be changed:
The original values of system variables can then be restored from the script:
Example 2-1 Storing and Restoring SQL*Plus System Variables
To store the current values of the SQL*Plus system variables in a new script 'plusenv.sql':
2.2.4 About Installing Command-line Help
Command-line help is usually installed during Oracle Database installation. If not, the database administrator can create the SQL*Plus command-line help tables and populate them with SQL*Plus help data by running a supplied SQL script from SQL*Plus.
The database administrator can also remove the SQL*Plus command-line help tables by running a SQL script from SQL*Plus.
Before you can install or remove SQL*Plus help, ensure that:
- SQL*Plus is installed.
- The ORACLE_HOME environment variable is set.
- The SQL*Plus help script files exist:
- HLPBLD.SQL - to drop and create new help tables.
- HELPDROP.SQL - to drop existing help tables.
- HELPUS.SQL - to populate the help tables with the help data.
2.2.4.1 Running the hlpbld.sql Script to Install Command-line Help
Run the provided SQL script, HLPBLD.SQL, to load command-line help.
- Log in to SQL*Plus as the SYSTEM user with: You are prompted to enter the password you have defined for the SYSTEM user.
- In UNIX run the SQL script, HLPBLD.SQL, from SQL*Plus with: In Windows run the SQL script, HLPBLD.SQL, from SQL*Plus with:The HLPBLD.SQL script creates and loads the help tables.
2.2.4.2 Running the helpdrop.sql Script to Remove Command-line Help
Run the provided SQL script, HELPDROP.SQL, to remove the command-line help.
- Log in to SQL*Plus as the SYSTEM user with: You are prompted to enter the password you have defined for the SYSTEM user.
- In UNIX run the SQL script, HELPDROP.SQL, from SQL*Plus with: In Windows run the SQL script, HELPDROP.SQL, from SQL*Plus with:The HELPDROP.SQL script drops the help tables, and then disconnects.
2.2.5 About Configuring Oracle Net Services
If you plan to connect to a database other than the default, whether on the same computer or another computer, you need to ensure that Oracle Net is installed, and the database listener is configured and running. Oracle Net services are used by SQL*Plus.
Oracle Net services and the database listener are installed by default during Oracle Database installation. For further information about installing and configuring Oracle Net, see the Oracle Database documentation at
http://www.oracle.com/technology/documentation
. 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.
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 10g Client Administrator installation.
Both the SQL*Plus and OCI packages must be from the same Oracle Database version, for example, 10.2.0.1.
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 must always be American.
- territory can be any valid territory supported by the Oracle Database.
- charset is one of the following character sets:
- US7ASCII
- WE8DEC
- 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 10.2.0.1. - 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 10.2.0.1. - Create a new directory, for example, /home/instantclient10_2 on UNIX or c:instantclient10_2 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 E-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 | orasqlplusic10.dll | SQL*Plus data shared library |
glogin.sql | glogin.sql | SQL*Plus site profile |
Table E-2 Instant Client Files in the Basic OCI Package
Linux and UNIX | Windows | Description |
---|---|---|
libclntsh.so.10.1 | oci.dll | Client code library |
libociei.so | oraociei10.dll | OCI Instant Client data shared library |
libnnz10.so | orannzsbb10.dll | Security library |
Table E-3 Instant Client Files in the Lightweight OCI Package
Linux and UNIX | Windows | Description |
---|---|---|
libclntsh.so.10.1 | oci.dll | Client code library |
libociicus.so | oraociicus10.dll | OCI Instant Client data shared library (English only) |
libnnz10.so | orannzsbb10.dll | Security library |
Installing SQL*Plus Instant Client from the 10g Client Release Media
- Run the installer on the Oracle Database 10g Client Release media and choose the Administrator option.
- Create a new directory, for example, /home/instantclient10_2 on UNIX and Linux, or c:instantclient10_2 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.
Oracle Sql Plus Download Mac Iso
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 10.2.0.1, /usr/bin/sqlplus is a symbolic link to the SQL*Plus binary at /usr/lib/oracle/10.2.0.1/client/bin/sqlplus.
- Set SQLPATH to the directory containing glogin.sql. 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 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 SQLPATH to the directory containing the Instant Client files so glogin.sql can be found. 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:instantclient10_2 to the beginning of PATH.
- Set the user environment variable SQLPATH to the directory containing the Instant Client files so glogin.sql is found.For example, create a user variable SQLPATH set to c:instantclient.
- 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
![Free sql plus Free sql plus](/uploads/1/2/6/7/126705608/120419533.jpg)
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 10g. 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_HOME%networkadmintnsnames.ora file defines the Net Service Name MYDB3:
Oracle Sql Plus Download Dba
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:
See the Oracle Database Administrator's Guide for information on Oracle password files.
Sql Plus App Download
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.
Oracle Sql Plus Download Mac Installer
Uninstalling SQL*Plus Instant Client
- For installations on Linux from RPM packages, use rpm -e only on the SQL*Plus Instant Client packageorFor installations on UNIX and Windows, and installations on Linux from the Client Release media, manually remove the following SQL*Plus specific files:Table E-4 Instant Client Files in the SQL*Plus Package
UNIX Windows Description sqlplussqlplus.exeSQL*Plus executableglogin.sqlglogin.sqlSQL*Plus site profilelibsqlplus.sonot applicableSQL*Plus librarylibsqlplusic.soorasqlplusic10.dllSQL*Plus data shared library - Reset environment variables and remove tnsnames.ora if necessary.
Sql Plus Download Free
Uninstalling the Complete Instant Client
Oracle Sql Plus Download Mac Download
- 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 themorFor installations on UNIX and Windows, and installations on Linux from the Client Release media, manually delete the directory containing the SQL*Plus executable, Oracle libraries and glogin.sql.See Installing SQL*Plus Instant Client from the 10g 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.