Note again, a full Java JDK install must be used. Note in the screenshot above, the JDK 1.7 Update 40 release was the specific version installed. Note the JDK location being used by SQL Developer is stored in a nf configuration file as the SetJavaHome parameter If the 64-bit Oracle RDBMS Client install is being used, then a separate 32-bit Java JDK will need to be downloaded and installed. After referencing a proper 32-bit JDK location to the bin java.exe, SQL Developer should launch successfully. Note the screenshot above references an Oracle 32-bit RDBMS Client that is included with Oracle’s EPM software installation. If the 32-bit Oracle RDBMS Client has been installed, a 32-bit Java JDK is included that can be referenced and used with SQL Developer. Note this must be a full Java JDK(Java Development Kit), not a JRE(Java Runtime Environment) location. When launching the SQL Developer icon for the first time, the above prompt will appear, and require a valid location for a 32-bit Java JDK install to be provided, specifically to the java.exe executable in the JDK’s bin folder. If this is the case, manually update the program icon to reference sqldeveloper.exe. With some installs, the created program icon will instead reference a non-existent SQLDEVELOPER.BAT file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |