Back on the Mac - SQL.Plus, gqlplus, SQL Developer etc Oracle 10g Instant Client for Mac OS X. Although the RDBMS software itself won't run on Intel Mac, it turns out that SQL.Plus does. The client software will also allow other applications to connect to the database. Find 'Macintosh OSX' and download both the Basic and SQL.Plus packages from. Sql oracle free download - SQL Assistant for Oracle, SQL PathFinder for Oracle, Oracle SQL Handler, and many more programs. Instant Client Downloads for macOS (Intel x86) See the Instant Client Home Page for more information about Instant Client. The installation instructions are at the foot of the page. Client-server version interoperability is detailed in Doc ID 207303.1.For example, Oracle Call Interface 19.3 and 18.1 can connect to Oracle Database 11.2 or later. PHP Release Management Process – Setting Web Development Environment (Mac OS X) PHP Release Management Process – Setting Database Development Environment (Mac OS X) PHP Release Management Process – Collaboration within Team (Mac OS X) PHP Release Management Process – Common Issues with Git (Mac OS X). Oracle SQL Developer 3.1 is available for Windows XP, Vista (including 64-bit), Windows 7 (including 64-bit), and Windows Server 2008, Linux or Mac OS X. Oracle to MS SQL Download.
Note:
This guide assumes that you plan to download the SQL Developer kit (.zip) file and install it as a freestanding tool.
If you plan to use SQL Developer as part of an Oracle Database release installation, see the Oracle Database installation documentation.
Please read the information in this chapter before you install Oracle SQL Developer. This chapter contains the following major sections:
1.1 SQL Developer System Recommendations
This section describes the recommended minimum values for CPU, memory, display, disk storage, and other resources on the supported systems.
Note:
SQL Developer requires JDK 7 or later, and Oracle recommends that you use the latest available JDK, which you can download from:
Table 1-1 Recommendations for Windows Systems
Table 1-2 Recommendations for Linux Systems
Table 1-3 Recommendations for Mac OS X Systems
1.2 Installing and Starting SQL Developer
This section contains subsections with instructions for installing SQL Developer on all supported systems.
SQL Developer does not require an installer. To install SQL Developer, you will need an unzip tool. You can download a free, cross-platform unzip tool, Info-Zip, available at
http://www.info-zip.org/ .
Important:
Do not install SQL Developer into any existing ORACLE_HOME . You will not be able to uninstall it using Oracle Universal Installer.
Also, do not install SQL Developer into an existing
sqldeveloper folder or directory. Either delete the existing sqldeveloper folder or directory first, or ensure that the new SQL Developer version is installed into a different location.
Important:
If you are using a prerelease (Early Adopter) version of SQL Developer, and if you want to be able to continue to use this prerelease version after installing the official release kit, you must unzip the official release kit into a different directory than the one used for the prerelease version.
If Oracle Database (Release 11 or later) is also installed, a version of SQL Developer is also included and is accessible through the menu system under Oracle. This version of SQL Developer is separate from any SQL Developer kit that you download and unzip on your own, so do not confuse the two, and do not unzip a kit over the SQL Developer files that are included with Oracle Database. Suggestion: Create a shortcut for the SQL Developer executable file that you install, and always use it to start SQL Developer.
Before you install SQL Developer, look at the remaining sections of this guide to see if you need to know or do anything else first.
The steps for installing SQL Developer depend on whether or not you will be using it on a Windows system that does not have Java SDK (JDK) release 7 or later installed:
1.2.1 Windows Systems
If a Windows 64-bit SQL Developer kit that includes JDK 7 is available, you can download and install that on a Windows 64-bit system, and SQL Developer will use the embedded JDK that is provided with that kit.
However, if you need or simply want to use a JDK on your Windows 64-bit system, you can install the JDK (if it is not already installed) and the Windows 32/64-bit SQL Developer kit, and SQL Developer will use the JDK that is installed on your system.
Note:
Do not install SQL Developer into an existing sqldeveloper folder. Either delete the existing sqldeveloper folder first, or ensure that the new SQL Developer version is installed into a different location.
To install on a Windows system, follow these steps:
The installation itself is simple. For example, on a Windows PC you can unzip the downloaded file into If you are asked to enter the full pathname for the JDK, click Browse and find it. For example, on a Windows system the path might have a name similar to C: , which will create C:sqldeveloper with files and folders in and under it.
C:Program FilesJavajdk1.7.0_51 .
If you are asked to enter the full pathname for the JDK, click Browse and find java.exe. For example, the path might have a name similar to
C:Program FilesJavajdk1.7.0_51 .
After SQL Developer starts, you can connect to any database by right-clicking the Connections node in the Connections Navigator and selecting New Connection. Alternatively, if you have any exported connections (see Section 1.4 or Section 1.10), you can import these connections and use them.
You can learn about SQL Developer by clicking Help, then Table of Contents, and reading the help topics under SQL Developer Concepts and Usage.
1.2.2 Linux and Mac OS X SystemsOracle Sql Plus Download Mac
SQL Developer requires that JDK 7 or later be installed on the system, and Oracle recommends that you install the latest available JDK version. If you need to install a JDK, go to
http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html .
Note:
Do not install SQL Developer into an existing sqldeveloper directory. Either delete the existing sqldeveloper directory first, or ensure that the new SQL Developer version is installed into a different location.
Note:
On Macintosh systems, a native Macintosh application in the form sqldeveloper xxx .tar.gz is provided. When it is expanded, it appears as a Macintosh application that can be put into the applications folder. If you choose to expand this file, it will replace any older sqldeveloper applications in that folder.
To install and start SQL Developer, follow these steps:
After SQL Developer starts, you can connect to any database by right-clicking the Connections node in the Connections Navigator and selecting New Connection. Alternatively, if you have any exported connections (see Section 1.4, 'Migrating Information from Previous Releases' or Section 1.10, 'Uninstalling SQL Developer'), you can import these connections and use them.
You can learn about SQL Developer by clicking Help, then Table of Contents, and reading the help topics under SQL Developer Concepts and Usage.
1.3 Migrating User Settings from a Previous Release
The first time you start SQL Developer after installing it or after adding any extensions, you are asked if you want to migrate your user settings from a previous release. (This occurs regardless of whether there was a previous release on your system.)
These settings refer to database connections, reports, and certain SQL Developer user preferences that you set in a previous version by clicking Tools and then Preferences. However, some user preferences are not saved, and you must respecify these using the new release.
To migrate user settings from a previous SQL Developer release:
See also Section 1.4, 'Migrating Information from Previous Releases'.
1.4 Migrating Information from Previous Releases
If you have used a previous release of SQL Developer, you may want to preserve database connections that you have been using. To preserve database connections, save your existing database connections in an XML file. To save the connections, right-click the Connections node in the Connections Navigator and select Export Connections. After you complete the installation described in this guide, you can use those connections by right-clicking the Connections node in the Connections Navigator and selecting Import Connections
If you want to use any user-defined reports or the SQL history from a previous version, see Section 1.5 for information about where these are located. If you have user-defined reports and SQL history from Release 1.0, they are modified by any later SQL Developer release to a format that is different from and incompatible with Release 1.0.
SQL Developer preferences (specified by clicking Tools and then Preferences) from a prerelease version of the current release cannot currently be saved and reused; you must respecify any desired preferences.
Mac dre livin it download. Jan 20, 2015.
Note:
If you want to uninstall your prerelease version of SQL Developer before installing this release, see Section 1.10, 'Uninstalling SQL Developer'.
1.5 Location of User-Related Information
SQL Developer stores user-related information in several places, with the specific location depending on the operating system and certain environment specifications. User-related information includes user-defined reports, user-defined snippets, SQL Worksheet history, code templates, and SQL Developer user preferences. In most cases, your user-related information is stored outside the SQL Developer installation directory hierarchy, so that it is preserved if you delete that directory and install a new version.
The user-related information is stored in or under the
IDE_USER_DIR environment variable location, if defined; otherwise as indicated in Table 1-4, which shows the typical default locations (under a directory or in a file) for specific types of resources on different operating systems. (Note the period in the name of any directory named .sqldeveloper .)
Table 1-4 Default Locations for User-Related Information
If you want to prevent other users from accessing your user-specific SQL Developer information, you must ensure that the appropriate permissions are set on the directory where that information is stored or on a directory above it in the path hierarchy. For example, on a Windows system you may want to ensure that the
SQL Developer folder and the <user-name>Application DataSQL Developer folder under Documents and Settings are not sharable; and on a Linux or Mac OS X system you may want to ensure that the ~/.sqldeveloper directory is not world-readable.
1.6 Database Certification for SQL Developer (Oracle and Third-Party)
This section describes Oracle and non-Oracle (third-party) databases that are certified for use with SQL Developer.
Table 1-5 lists the Oracle database certifications.
Table 1-5 Oracle Database Certification for SQL Developer
SQL Developer can be used to view metadata and data of several non-Oracle (third-party) databases. Table 1-6 lists the third-party database certifications.
Table 1-6 Non-Oracle (Third-Party) Database Certification for SQL Developer
For information about creating and using connections to third-party databases, see the information about database connections in the SQL Developer online help or Oracle SQL Developer User's Guide.
1.7 Advanced Security for JDBC Connection to the Database
You are encouraged to use Oracle Advanced Security to secure a JDBC connection to the database. Both the JDBC OCI and the JDBC Thin drivers support at least some of the Oracle Advanced Security features. If you are using the OCI driver, you can set relevant parameters in the same way that you would in any Oracle client setting. The JDBC Thin driver supports the Oracle Advanced Security features through a set of Java classes included with the JDBC classes in a Java Archive (JAR) file and supports security parameter settings through Java properties objects.
1.8 Finding SQL Developer Accessibility Information
For the latest configuration information or for information on addressing accessibility and assistive technology issues, see the Oracle Accessibility FAQ at
http://www.oracle.com/us/corporate/accessibility/faqs/ .
Also, check the SQL Developer release notes (
readme.txt file) to see if there are any currently known issues regarding accessibility.
1.9 Using a Screen Reader and Java Access Bridge with SQL Developer
Note:
Unless otherwise indicated, the information is this section also applies to Data Modeler and Data Miner.
To make the best use of our accessibility features, Oracle Corporation recommends the following minimum configuration:
Follow these steps to set up a screen reader and Java Access Bridge.
The preceding steps assume you are running Windows and using a Windows-based screen reader. A console window that contains error information (if any) will open first and then the main SQL Developer window will appear, after SQL Developer has started. Any messages that appear will not affect the functionality of SQL Developer.
1.9.1 If You Need to Install Java Access Bridge
If you are using Java J2SE 1.6.0_24 or later but before Java 7 Update 6, you must manually install Java Access Bridge 2.0.2 after you install the screen reader (if it is not already installed).
1.10 Uninstalling SQL Developer
Before you uninstall SQL Developer, if you plan to install SQL Developer (the same or an updated version) later, you may want to save your existing database connections; and if so, see Section 1.4 before uninstalling.
To uninstall SQL Developer, remove the entire SQL Developer installation directory (that is, the directory named
sqldeveloper and all directories and files under it in the hierarchy).
If you also want to remove all user-specific SQL Developer information, you should also delete the directory under which that information is stored (that is, the SQL Developer user information directory). For the location of this directory, see Section 1.5.
If you have created a shortcut for SQL Developer, and if you do not plan to install SQL Developer into the same location again, you should remove that shortcut or modify the shortcut properties to reflect the new location.
1.11 SQL Developer Documentation
SQL Developer provides user documentation in the Oracle SQL Developer User's Guide and in the online help. To see the help, click the Help menu, or click the Help button or press the F1 key in relevant contexts while you are using SQL Developer.
In addition to the user's guide and installation guide, the following migration-related guides are available:
1.12 Oracle on the Web
Oracle provides a number of resources on the web. These are some sites you may find helpful:
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:
Choosing the SQL*Plus Instant Client to Install
SQL*Plus Instant Client can be installed in two ways:
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:
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
Installing SQL*Plus Instant Client from the UNIX or Windows Zip Files
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
Table E-2 Instant Client Files in the Basic OCI Package
Table E-3 Instant Client Files in the Lightweight OCI Package
Oracle Sql Plus Mac Download VersionInstalling SQL*Plus Instant Client from the 10g Client Release Media
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 ClientInstall Sql Plus
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.
Configuring SQL*Plus Instant Client on Linux (from Client Media or Zip File) and UNIX
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.
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 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:
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.
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
Uninstalling the Complete Instant Client
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |