NOTE: When upgrading, install in a new directory and change to a new workspace. This will resolve all the following issues:
"JVM terminated. Exit code=-1"
change the values in dboptimizer.ini (located in the root directory of the DB Optimizer install)
For some installs the following might work and be more flexible on memory constraints
The argument "-vm" will have to be changed depending on the location of javaw.exe on the user's machine.
"Unable to read workbench state. Workbench UI layout will be reset"
"Error opening the editor.
No editor descriptor for id
If you had an earlier version of DB Optimizer, make sure it's installed in a different directory and that the workspace is different.
"Cannot restore workbench layout."
If you have already installed the beta version of DB Optimizer 1.5 you will get an error about the workspace not being compatible. You will have to change the default workspace or clear out the old one. By default it is
C:\Documents and Settings\USER\dboptimizer\workspace
Where “USER” is your logon user. This is prompted for at startup time and easily modifiable or it can be changed after starting by choosing the menu
No data returned when running queries in SQL Editor
If 1.5 beta was installed but never de-installed, then de-install the beta and re-install the production version
At startup, after accepting the workspace directory, the application never opens and the dboptimizer.exe runs in the backgrounds "spinning"
Choose a different workspace when the workspace is prompted for. An easy option would be to add the days date for example "workspace090520". DB Optimizer will create this new workspace directory and it should startup. Development is investigating this issue
DB Optimizer log files by default are in (the [workspace]/.metadata/.log file)
C:\Documents and Settings\<user>\dboptimizer\workspace
to verify this location choose menus
File -> switch workspace
which will popup a window with the current workspace directory
Zip this directory and send it to support whenever getting unusual errors
99% of the new information just all gets sent to the error log (the [workspace]/.metadata/.log file).
add this line to the bottom and then restart the application: