Oracle Sql Developer Mac Os X Download
2021年1月25日Download here: http://gg.gg/o0c8x
*Oracle Sql Developer Download
*Oracle Sql Developer Download Mac
*Download Oracle Sql Developer For Mac Os X Platform
Ensure you have a JDK installed, if not, download here (For 64-bit Intel Macs, download Java for Mac OS X 10.5, Update 1. For the latest version of Mac OS, use the Software Update feature) Download the file for OS X on the Downloads page; Double-click the SQL Developer icon. SQL Developer, SQL Developer Downloads Release 3.2.2. Installation Notes 174 MB. SQL Developer 3.0 EA, Mac OS X 10.6.6 workaround 830194 Jan 11, 2011 11:28 AM Downloaded ’sqldeveloper-3.0.02.83-macosx.tar.gz’ and installed SQLDeveloper into ’/Applications/db/’. I am attempting to install Oracle SQL Developer Version 4.1.1. Onto my MacBook Pro after installing OS X El Capitan. After I download the application and attempt to click on the icon to install it, the application’s loading prompt appears and the ’loading’ bar moves about 5% to the part where it says ’registering extensions’ right above the. Re: Installing SQL Developer on MAC OSX Ronald Rood Feb 10, 2013 9:49 AM ( in response to 987952 ) On MacOSX you just unzip the package and run the application to connect to the database where your username/password have to be created before you can connect to it.
Note:
This guide assumes that you plan to download SQL Developer and run it as a freestanding tool.
For information about operating system versions supported for Oracle JDK 8, see http://www.oracle.com/technetwork/java/javase/certconfig-2095354.html.
If you plan to use SQL Developer as part of an Oracle Database release installation, see the Oracle Database installation documentation. Starting with Oracle Database Release 19c, SQL Developer is no longer available with Oracle Database.
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 8 or 9, which you can download from:
Table 1-1 Recommendations for Windows SystemsResourceRecommended Minimum Value
Operating System
Windows Server 2008
Windows Server 2012
Windows 7
Windows 8
Windows 10
CPU Type and Speed
Pentium IV 2 GHz MHz or faster
Memory
2 GB RAM
Display
65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space
500 MB if you already have JDK 8
110 MB if you do not have JDK 8
Java SDK
JDK 8 or 9 for Windows, available at: http://www.oracle.com/technetwork/java/javase/downloads/index.html.
Table 1-2 Recommendations for Linux SystemsResourceRecommended Minimum Value
Operating System
Oracle Linux 5.5
Red Hat Enterprise Linux 5.5
SUSE Linux Enterprise Server 10 SP2
Ubuntu Linux 10.04
CPU Type and Speed
Pentium IV 2 GHz or faster
Memory
2 GB RAM
Display
65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space
110 MB
Java SDK
JDK 8 or 9 for Linux, available at: http://www.oracle.com/technetwork/java/javase/downloads/index.html
Table 1-3 Recommendations for Mac OS X SystemsResourceRecommended Minimum Value
Operating System
Apple Mac OS X Version 10.8.3
CPU Type and Speed
Dual 1.25 GHz G4/G5 (1 GHz G4 minimum)
Memory
2 GB RAM
Display
’Thousands’ of colors
Hard Drive Space
110 MB
Java SDK
JDK 8 or 91.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://infozip.sourceforge.net/.
Note:
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.
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.
Note:
Starting with Oracle Database Release 19c, SQL Developer is no longer available with Oracle Database.
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 Windows Systems.
*
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 Linux and Mac OS X Systems. 1.2.1 Windows Systems
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 http://www.oracle.com/technetwork/developer-tools/sql-developer/.
*
If you do not need or want to install a suitable Java Development Kit (JDK 8 or 9), go to step 3. Otherwise, download and install the JDK as follows:
*
On the Java SE Development Kit 8 Downloads page (http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html), 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 http://www.oracle.com/technetwork/developer-tools/sql-developer/, 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 the JDK folder. For example, on a Windows system the path might have a name similar to C:Program FilesJavajdk1.8.0_51.
*
Unzip the SQL Developer file into a folder (directory) of your choice, which will be referred to as <sqldeveloper_install>. 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 <sqldeveloper_install> 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_install>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 the JDK folder. For example, the path might have a name similar to C:Program FilesJavajdk1.8.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 Migrating Information from Previous Releases or 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.2.2 Linux and Mac OS X Systems
SQL Developer requires that JDK 8 or 9 be installed on the system. If you need to install a JDK, go to http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.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 sqldeveloperxxx.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 <sqldeveloper_install>.
Unzipping the SQL Developer kit causes a directory named sqldeveloper to be created under the <sqldeveloper_install> 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 <sqldeveloper_install> 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 Migrating Information from Previous Releases or 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.)
If you choose not to migrate your user settings and then later want to do so, go to the SQL Developer user preferences location, which is C:Users<user name>AppDataRoamingSQL Developersystemn.n.n.n.n for Windows and ~/.sqldeveloper/systemn.n.n.n.n for Linux or Mac, and delete the system.n.n.n.n folder. Then restart SQL Developer, and you will be asked about migrating settings from the previous release.
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:Oracle Sql Developer Download
*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.
Related Topics1.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 Location of User-Related Information 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.
Note:
If you want to uninstall your prerelease version of SQL Developer before installing this release, see 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 InformationResource TypeSystem (Windows, Linux, or Mac OS X)
User-defined reports
Windows: C:Users<user-name>AppDataRoamingSQL DeveloperUserReports.xml
Linux or Mac OS X: ~/.sqldeveloper/UserReports.xml
User-defined snippets
Windows: C:Users<user-name>AppDataRoamingSQL DeveloperUserSnippets.xml
Linux: ~/.sqldeveloper/UserSnippets.xml
Mac OS X: /Users/<Your user>/Library/Application Support/ SQLDeveloper/UserSnippets.xml
SQL history
Windows: C:Users<user-name>AppDataRoamingSQL DeveloperSqlHistory.xml
Linux: ~/.sqldeveloper/SqlHistory.xml
Mac OS X: /Users/<Your user>/Library/Application Support/ SQLDeveloper/ SqlHistory.xml
Code templates
Windows: C:Users<user-name>AppDataRoamingSQL Developer CodeTemplate.xml
Linux: ~/.sqldeveloper/CodeTemplate.xml
Mac OS X: /Users/<Your user>/Library/Application Support/ SQLDeveloper/ CodeTemplate.xml
SQL Developer user preferences
Windows: C:Users<user-name>AppDataRoamingSQL Developersystemn.n.n.n.n
Linux or Mac OS X: ~/.sqldeveloper/systemn.n.n.n.n
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>AppDataSQL Developer folder under Users 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 DeveloperProductReleases
Oracle Database
Oracle 11gR2
Oracle 12c, 18c, 19c
Oracle Database Express Edition
Release 18c
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 DeveloperDatabaseReleasesNotes
IBM DB2
DB2 UDB
DB2 8.x
DB2 9.x
For any DB2 release: db2jcc.jar and db2jcc_license_cu.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 TeraJDBC__indep_indep.12.00.00.110.zip or TeraJDBC__indep_indep.12.00.00.110.tar download.
Note:
If you need to use SQL Developer to migrate a Microsoft Access database. use the previous version of SQL Developer (4.0.3) and the 32-bit version of the Java 7 JDK.
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 i
https://diarynote-jp.indered.space
*Oracle Sql Developer Download
*Oracle Sql Developer Download Mac
*Download Oracle Sql Developer For Mac Os X Platform
Ensure you have a JDK installed, if not, download here (For 64-bit Intel Macs, download Java for Mac OS X 10.5, Update 1. For the latest version of Mac OS, use the Software Update feature) Download the file for OS X on the Downloads page; Double-click the SQL Developer icon. SQL Developer, SQL Developer Downloads Release 3.2.2. Installation Notes 174 MB. SQL Developer 3.0 EA, Mac OS X 10.6.6 workaround 830194 Jan 11, 2011 11:28 AM Downloaded ’sqldeveloper-3.0.02.83-macosx.tar.gz’ and installed SQLDeveloper into ’/Applications/db/’. I am attempting to install Oracle SQL Developer Version 4.1.1. Onto my MacBook Pro after installing OS X El Capitan. After I download the application and attempt to click on the icon to install it, the application’s loading prompt appears and the ’loading’ bar moves about 5% to the part where it says ’registering extensions’ right above the. Re: Installing SQL Developer on MAC OSX Ronald Rood Feb 10, 2013 9:49 AM ( in response to 987952 ) On MacOSX you just unzip the package and run the application to connect to the database where your username/password have to be created before you can connect to it.
Note:
This guide assumes that you plan to download SQL Developer and run it as a freestanding tool.
For information about operating system versions supported for Oracle JDK 8, see http://www.oracle.com/technetwork/java/javase/certconfig-2095354.html.
If you plan to use SQL Developer as part of an Oracle Database release installation, see the Oracle Database installation documentation. Starting with Oracle Database Release 19c, SQL Developer is no longer available with Oracle Database.
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 8 or 9, which you can download from:
Table 1-1 Recommendations for Windows SystemsResourceRecommended Minimum Value
Operating System
Windows Server 2008
Windows Server 2012
Windows 7
Windows 8
Windows 10
CPU Type and Speed
Pentium IV 2 GHz MHz or faster
Memory
2 GB RAM
Display
65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space
500 MB if you already have JDK 8
110 MB if you do not have JDK 8
Java SDK
JDK 8 or 9 for Windows, available at: http://www.oracle.com/technetwork/java/javase/downloads/index.html.
Table 1-2 Recommendations for Linux SystemsResourceRecommended Minimum Value
Operating System
Oracle Linux 5.5
Red Hat Enterprise Linux 5.5
SUSE Linux Enterprise Server 10 SP2
Ubuntu Linux 10.04
CPU Type and Speed
Pentium IV 2 GHz or faster
Memory
2 GB RAM
Display
65536 colors, set to at least 1024 X 768 resolution
Hard Drive Space
110 MB
Java SDK
JDK 8 or 9 for Linux, available at: http://www.oracle.com/technetwork/java/javase/downloads/index.html
Table 1-3 Recommendations for Mac OS X SystemsResourceRecommended Minimum Value
Operating System
Apple Mac OS X Version 10.8.3
CPU Type and Speed
Dual 1.25 GHz G4/G5 (1 GHz G4 minimum)
Memory
2 GB RAM
Display
’Thousands’ of colors
Hard Drive Space
110 MB
Java SDK
JDK 8 or 91.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://infozip.sourceforge.net/.
Note:
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.
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.
Note:
Starting with Oracle Database Release 19c, SQL Developer is no longer available with Oracle Database.
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 Windows Systems.
*
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 Linux and Mac OS X Systems. 1.2.1 Windows Systems
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 http://www.oracle.com/technetwork/developer-tools/sql-developer/.
*
If you do not need or want to install a suitable Java Development Kit (JDK 8 or 9), go to step 3. Otherwise, download and install the JDK as follows:
*
On the Java SE Development Kit 8 Downloads page (http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html), 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 http://www.oracle.com/technetwork/developer-tools/sql-developer/, 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 the JDK folder. For example, on a Windows system the path might have a name similar to C:Program FilesJavajdk1.8.0_51.
*
Unzip the SQL Developer file into a folder (directory) of your choice, which will be referred to as <sqldeveloper_install>. 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 <sqldeveloper_install> 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_install>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 the JDK folder. For example, the path might have a name similar to C:Program FilesJavajdk1.8.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 Migrating Information from Previous Releases or 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.2.2 Linux and Mac OS X Systems
SQL Developer requires that JDK 8 or 9 be installed on the system. If you need to install a JDK, go to http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.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 sqldeveloperxxx.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 <sqldeveloper_install>.
Unzipping the SQL Developer kit causes a directory named sqldeveloper to be created under the <sqldeveloper_install> 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 <sqldeveloper_install> 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 Migrating Information from Previous Releases or 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.)
If you choose not to migrate your user settings and then later want to do so, go to the SQL Developer user preferences location, which is C:Users<user name>AppDataRoamingSQL Developersystemn.n.n.n.n for Windows and ~/.sqldeveloper/systemn.n.n.n.n for Linux or Mac, and delete the system.n.n.n.n folder. Then restart SQL Developer, and you will be asked about migrating settings from the previous release.
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:Oracle Sql Developer Download
*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.
Related Topics1.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 Location of User-Related Information 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.
Note:
If you want to uninstall your prerelease version of SQL Developer before installing this release, see 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 InformationResource TypeSystem (Windows, Linux, or Mac OS X)
User-defined reports
Windows: C:Users<user-name>AppDataRoamingSQL DeveloperUserReports.xml
Linux or Mac OS X: ~/.sqldeveloper/UserReports.xml
User-defined snippets
Windows: C:Users<user-name>AppDataRoamingSQL DeveloperUserSnippets.xml
Linux: ~/.sqldeveloper/UserSnippets.xml
Mac OS X: /Users/<Your user>/Library/Application Support/ SQLDeveloper/UserSnippets.xml
SQL history
Windows: C:Users<user-name>AppDataRoamingSQL DeveloperSqlHistory.xml
Linux: ~/.sqldeveloper/SqlHistory.xml
Mac OS X: /Users/<Your user>/Library/Application Support/ SQLDeveloper/ SqlHistory.xml
Code templates
Windows: C:Users<user-name>AppDataRoamingSQL Developer CodeTemplate.xml
Linux: ~/.sqldeveloper/CodeTemplate.xml
Mac OS X: /Users/<Your user>/Library/Application Support/ SQLDeveloper/ CodeTemplate.xml
SQL Developer user preferences
Windows: C:Users<user-name>AppDataRoamingSQL Developersystemn.n.n.n.n
Linux or Mac OS X: ~/.sqldeveloper/systemn.n.n.n.n
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>AppDataSQL Developer folder under Users 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 DeveloperProductReleases
Oracle Database
Oracle 11gR2
Oracle 12c, 18c, 19c
Oracle Database Express Edition
Release 18c
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 DeveloperDatabaseReleasesNotes
IBM DB2
DB2 UDB
DB2 8.x
DB2 9.x
For any DB2 release: db2jcc.jar and db2jcc_license_cu.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 TeraJDBC__indep_indep.12.00.00.110.zip or TeraJDBC__indep_indep.12.00.00.110.tar download.
Note:
If you need to use SQL Developer to migrate a Microsoft Access database. use the previous version of SQL Developer (4.0.3) and the 32-bit version of the Java 7 JDK.
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 i
https://diarynote-jp.indered.space
コメント