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. On Macintosh systems, a native Macintosh application in the form sqldeveloper xxx.
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. 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. It also causes many files and directories to be placed in and under that directory.
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. 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. 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. Note the period in the name of any directory named. 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.
Table lists the Oracle database certifications. SQL Developer can be used to view metadata and data of several non-Oracle third-party databases. Table lists the third-party database certifications. For MySQL 5. Do not use the latest MySQL driver 5. Start SQL Developer by running the file sqldeveloper. 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. Refer to the Java Access Bridge documentation available from this website for more information about installation and the Java Access Bridge. Install Java Access Bridge by running Install.
The installer first checks the JDK version for compatibility, then the Available Java virtual machines dialog displays. Click Search Disks. Then select to search only the drive that contains the SQL Developer build and the JDK version in the program files directory if it exists.
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. Confirm that the file accessibility. 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.
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.
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.
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:.
You will not be able to uninstall it using Oracle Universal Installer. 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.
Either delete the existing sqldeveloper folder first, or ensure that the new SQL Developer version is installed into a different location. 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. 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 migrate user settings from a previous SQL Developer release: Unzip the kit for the current release so as to create a new sqldeveloper directory. See also Section 1. 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.
SQL Developer preferences specified by clicking Tools and then Preferences from a pre-release version of the current release cannot currently be saved and reused; you must re-specify any desired preferences.
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.
Note the period in the name of any directory named. The following table shows the typical default locations under a directory or in a file for specific types of resources on different operating systems.
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.
SQL Developer can be used to view metadata and data of several non-Oracle third-party databases. Table lists the third-party database certifications. For any Access release: no JDBC driver needed, but you must ensure read access to system tables in the. For MySQL 5. Do not use the latest MySQL driver 5. JDBC driver files tdgssconfig. If you are using the OCI driver, you can set relevant parameters in the same way that you would in any Oracle client setting.
Also, check the SQL Developer release notes readme. To make the best use of our accessibility features, Oracle Corporation recommends the following minimum technology stack:. Follow these steps to set up a screen reader and Java Access Bridge. If you are using JAWS 3. Install the screen reader, if it is not already installed. See the documentation for your screen reader for more information about installation.
Install SQL Developer. Download Java Access Bridge for Windows version 1. See the Java Access Bridge documentation available from this Web site for more information about installation and the Java Access Bridge. Install Java Access Bridge by running Install. The installer first checks the SDK version for compatibility, then the Available Java virtual machines dialog displays. Click Search disks. Then select to search only the drive that contains the SQL Developer build and the SDK version in the program files directory if it exists.
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.
0コメント