It’s amazing to me that there is yet another outcome from installing Oracle Database 11g on Windows 7. This one installs without an error but then raises the following error message dialog when you try to launch SQL Developer from the menu. Naturally, it seems to depend on having more than one Java JVM installed when you run the Oracle Universal Installer (OUI) without setting the
%JAVA_HOME% environment variable.
Text of error message from image:
Windows is searching for SQLSERVER.BAT. To located the file yourself, click Browse.
While the installation release notes (E10842-02) that download or ship with the product don’t mention the
%DEV_TOOLS% environment variables, it appears you should set them before the installation. You can discover this by double clicking on the SQL Developer menu option, and then choose Properties. You should see the following in the dialog.
Windows 7 searches for the
sqldeveloper.bat file when the OUI installation fails to configure the
SetJavaHome parameter in the
sqldeveloper.conf file. OUI does configure the
SetJavaHome parameter when OUI resolves the JVM address.
You should put this in the Target field:
Although, that may be a simplifying assumption of what causes the problem, I didn’t go through all the Oracle Universal Installer (OUI) background tasks to discover the actual code element. Also, I didn’t take the time to retest by setting those parameters. I solved this problem by replacing the
sqldeveloper.bat value with a
sqldeveloperw.exe value in the menu link, applying the change, and saving it. If you’ve a better solution, please share it.
The configuration file is found here:
While you can provide a
sqldeveloper.bat file, it’s much simpler to simply put the JVM physical address in the
sqldeveloper.conf file. That’s what I did to solve the problem and what I think the development team expects.
SetJavaHome value points to a 32-bi JVM, and in my testing environment that is:
SetJavaHome C:\Program Files (x86)\Java\jdk1.6.0_34
Another post on this topic can be found here. As always, I hope this saves somebody time working with the Oracle product stack.