You can't install the database server software directly on OS X 1. Oracle made a decision some time ago not so support it any more, presumably because it wasn't used enough to justify the costs involved. I seem to recall its demise roughly coincided with Apple dropping their Xserve line, but I may have imagined that. A client like SQL Developer is a very different proposition from a support perspective. SQL Developer is a Java application, and requires a JVM/JDK to be installed. Java's write-once-run-anywhere may not be entirely true, but it's still likely to be rather less work to support a relatively small Java application than a natively-compiled beast like an full RDBMS.
They obviously have to do some work to have a.app bundle and there are some application difference from the Windows version, but they don't have to worry about different architecture, system libraries, etc. As that's the JVM's problem. You can use SQL Developer on a Mac to connect to a database running on Windows or Unix/Linux etc., so it still has a place; the fact you can't have a local server running on the same hardware isn't really relevant for most people. It just allows developers to use a Mac instead of forcing them on to a Windows or Linux PC. If you only have access to a Mac then the simplest route is still, to install and one of the Oracle provides. You can also install Windows or Linux on Bootcamp or in your own VM in Virtualbox, Parallels or VMWare; and then install Oracle natively. Using a pre-built image saves you needing to learn how to install the database server software, and also makes it easier to go back - if you really mess something up you can trash it and start again fairly simply.
If you're worried about performance or power use I'd suggest you start with a VM and see how you get on; you can always add Bootcamp later and even move the data across if you want to go down that route. 1 You could try to hack something together of course; with 10g but I haven't seen anyone trying it recently so it may not be as easy on Yosemite and 11g/12c.
Note: 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:. For a Windows system with JDK release 8 or later installed, follow the instructions in. For all other systems (Linux and Mac OS X systems, and Windows systems with no JDK release 8 or later installed), follow the instructions in.
If a Windows 64-bit SQL Developer file that includes JDK 8 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. However, if you 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 file, and SQL Developer will use the JDK that is installed on your system. The bit level (32-bit or 64-bit) of the JDK that you install will determine if SQL Developer runs as a 32-bit or 64-bit application. 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:. Go to the Oracle Technology Network page for SQL Developer at. If you do not need or want to install a suitable Java Development Kit (JDK 8 or later), go to step 3. Otherwise, download and install the JDK as follows:. On the Java SE Development Kit 8 Downloads page , in the table of Java SE Development Kits, accept the Oracle Binary Code License Agreement for Java SE.
Click the link for the download that you need (for example, the Windows x64 link for a Windows 64-bit system). Save the file anywhere on your system (such as a 'temp' folder). Install the JDK (for example, on Windows, double-click the.exe file name and follow the displayed instructions). On the Oracle Technology Network page for SQL Developer at, click the Downloads tab (next to Overview).
Read and accept the license agreement. Follow the instructions for downloading and installing SQL Developer. 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: Program Files Java jdk1.8.051. Unzip the SQL Developer file into a folder (directory) of your choice, which will be referred to as. Ensure that the Use folder names option is checked when unzipping the file.
Unzipping the SQL Developer file causes a folder named sqldeveloper to be created under the folder. For example, if you unzip the file into C:, the folder C: sqldeveloper is created, along with several subfolders under it. To start SQL Developer, go to sqldeveloper, and double-click sqldeveloper.exe.
On Linux systems, type sh sqldeveloper.sh. 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 Files Java jdk1.8.051. 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 or ), 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. 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:. Unzip the SQL Developer kit into a directory (folder) of your choice.
(Ensure that the Use folder names option is checked when unzipping the kit.) This directory location will be referred to as. Unzipping the SQL Developer kit causes a directory named sqldeveloper to be created under the directory. It also causes many files and directories to be placed in and under that directory. To start SQL Developer, go to the sqldeveloper directory under the directory, and run sh sqldeveloper.sh.
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 or ), 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. 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:.
Unzip the kit for the current release so as to create a new sqldeveloper directory. When you start the SQL Developer current release, click Yes when asked if you want to migrate settings from a previous release. In the dialog box that is displayed, you can accept the default option to migrate the settings from the most recent SQL Developer installation. Or, if you want to migrate the settings from an earlier installation, you can click to show all builds and then select the desired one. 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 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. To migrate the SQL Developer preferences (specified by clicking Tools and then Preferences) from a previous release, ensure that the previous installation of the software is available in the same system. 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 IDEUSERDIR environment variable location, if defined; otherwise as indicated in, 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-6 Non-Oracle (Third-Party) Database Certification for SQL Developer Database Releases Notes IBM DB2 DB2 UDB DB2 8.x DB2 9.x For any DB2 release: db2jcc.jar and db2jcclicensecu.jar files required; available from IBM. Microsoft SQL Server SQL Server 7 SQL Server 2000 SQL Server 2005 SQL Server 2008 For any Microsoft SQL Server release: JDBC driver jtds-1.2.jar required; included in jtds-1.2-dist.zip available from sourceforge.net; also available through Help, Check for Updates. MySQL MySQL 3.x MySQL 4.x MySQL 5.x For any MySQL release: JDBC driver required. For MySQL 5.x: mysql-connector-java-5.0.4-bin.jar, which is included in mysql-connector-java-5.0.4.zip; also available through Help, Check for Updates. (Do not use the latest MySQL driver 5.1.) Sybase Adaptive Server Sybase 12 Sybase 15 For any Sybase Adaptive Server release: JDBC driver jtds-1.2.jar required; included in jtds-1.2-dist.zip available from sourceforge.net; also available through Help, Check for Updates.
Teradata Teradata 12 Teradata 13 JDBC driver files tdgssconfig.jar and terajdbc4.jar required; included (along with a readme.txt file) in the TeraJDBCindepindep.12.00.00.110.zip or TeraJDBCindepindep.12.00.00.110.tar download. 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.
Oracle Sql For Mac Download
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.
Oracle Sql For Mac
For more information about using Oracle Advanced Security, see Oracle Database JDBC Developer's Guide. 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:.
Windows XP, Windows Vista. Java 7 Update 6 Java 7 Update 6 includes the Java Access Bridge.
However, if you are using Java J2SE 1.6.024 or higher 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). Download Java Access Bridge for Windows version 2.0.2.
The file you will download is accessbridge-202-fcs-bin-b06.zip. It is available from: (Refer to the Java Access Bridge documentation available from this website for more information about installation and the Java Access Bridge.). JAWS 12.0.522 Follow these steps to set up a screen reader and Java Access Bridge. Install the screen reader, if it is not already installed. Refer to the documentation for your screen reader for more information about installation.
Oracle Sql Developer For Mac
Install SQL Developer. If you are using Java J2SE 1.6.024 or higher but before Java 7 Update 6, go to and follow the instructions there. Start your screen reader. Start SQL Developer by running the file sqldeveloper.exe located in the folder sqldeveloper sqldev bin. 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. The search process can take a long time on a large disk with many instances of JDK or SQL Developer, or when searching multiple disks. However, unless you complete an exhaustive search of your disk, Access Bridge will not be optimally configured, and will not be correctly installed to all of the Java VMs on your system. After selecting the disk to search, click Search. Confirm that you want to install the Java Access Bridge into each of the Java virtual machines displayed in the dialog, by clicking Install in All. Click OK when you see the Installation Completed message. Confirm that the following files have been installed in the Winnt System32 directory (or the equivalent Windows XP or Vista directory), or copy them from installerfiles because they must be in the system path in order to work with 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 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. 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.