Picasso Database Query Optimizer Visualizer

©Indian Institute of Science, Bangalore, India

 

TROUBLE-SHOOTING

 

  1. If you get connection errors to the database engines, make sure that you have the appropriate database connection libraries present in the Libraries directory, and that you have executed the activatedb script.
  2. If you get visualization errors, make sure that you have the appropriate graphics libraries present in the Libraries directory.
  3. If the AutoConvert SQL Dialect  button is greyed out, you will need to download the SwisSQL.API.jar  library file into the Libraries directory (see the licenses documentation for download details). Note that this optional library is not provided even with the full distribution of Picasso.
  4. If you have problems running Picasso with the Java3D installed on your system, copy the library files j3dcore.jar, j3dutils.jar and vecmath.jar from the system’s Java3D directory to the Libraries directory.
    In Windows, if the problem persists, edit runClient.bat as follows:
    Change “java -Xmx256m …” to
                “java –Djava.library.path=<JDK_HOME>\jre\bin  –Xmx256m …”
    This directory contains J3D.dll and J3dUtils.dll which are required to run Picasso.
  5. If the Picasso Client doesn’t seem to be responding, or is taking a long time for some operation, check the console from which the Client was run. If there is any error message like “Out of memory exception”, then close the Client and restart it. If the problem persists, increase the JVM memory amount to 1 GB by providing -Xmx1024m argument. By default it is set to 256 MB.
  6. During its operations, the Picasso Client may throw an error message “Out of Memory Error, Please Restart PicassoClient”.  This happens when too many diagrams are created in the current session of the client.  When this happens, close the Client and start it again.
  7. After clicking on a diagram tab, you may sometimes receive a black diagram screen instead of the picture.  This is usually because your system does not have sufficient video memory to host all the diagrams retrieved from the server.  To conserve video memory, try lowering the screen resolution and reducing the color quality.  Alternatively, set the flag LOW_VIDEO in PicassoConstants.java to True (the default value is False), recompile the client, and resume operations – with this flag set to true, the video memory is flushed before each new diagram is loaded. 
  8. The Picasso Client window always starts in a maximized state.  If it is resized to some other state during its operations, then the Status Bar may not be visible.  To see the status bar, maximize the Client window.
  9. The Plan Legend may not show sometimes – in such cases, try resizing the window to Normal size and then revert to Maximized size.
  10. If the Picasso Client or the Picasso Server seems to hang, it could be because the associated console is in the ‘Select’ mode, perhaps due to a mouse click.  In this situation, try to bring the console back to the normal mode by pressing the ‘Enter’ key in the console.
  11. If the Machine field of the DBConnection Settings dialog accepts the IP of a machine, but does not accept the machine name, then add the machine to the file Windows\system32\drivers\etc\hosts | /etc/hosts in Windows | Unix and try again.
  12. For a Picasso error that appears related to the database engine, first check if the query can be independently and successfully executed directly on the database engine, in order to make sure the error is not due to the query syntax or semantics (such as missing table, wrong schema, etc), and take measures accordingly.

Note: If the above solutions do not address your problem, please contact us at picasso@dsl.serc.iisc.ernet.in with a description of the problem. Both the Picasso Server and the Picasso Client write their outputs and errors into log files in the PicassoRun/Logs directory.  The log files typically take up a few tens of kilobytes space for each freshly processed query template. With your email, please attach the Server and Client log files, the SelLog text file (created in Logs directory by executing Save in the File menu for the SelLog screen),  as well as screen dumps of the Server and Client consoles.


   
 KNOWN  ISSUES:

  1. In a Linux environment, the client may throw the exception (<unknown>:8407): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == gdk_drawable_get_depth (window)' failed. This is an open bug currently being examined by Sun Developer Network. For more details, please refer to this page.

 

Documentation Home