GeoRaptor for SQLDeveloper 4.x

GeoRaptor, the popular free and open source spatial plugin for SQLDeveloper, currently only runs within SQLDeveloper version 3.2.  Oracle have improved SQLDeveloper significantly in version 4.0, and are now preparing to release 4.1. Meanwhile GeoRaptor users are stuck with using the older release of SQLDeveloper as the extensibility framework changed in version 4.0 – to make GeoRaptor compatible will require some significant code changes.
Simon Greener has been the primary developer of GeoRaptor for the past few years and has invested a significant amount of unpaid time in getting it to where it is today.  The development effort to support SQLDeveloper 4.x will take more than few hours of free time so some funding will be required.  A crowdsourcing site has been setup to enable this:
https://www.indiegogo.com/projects/georaptor-4-0#home
A very modest target of $1,000 has been set to fund the initial port to 4.x – hopefully this will be exceeded and any additional funding that is raised will go towards a round of development to help iron out bugs, improve usability and look at adding additional functionality.
If you have found GeoRaptor of use in the past and would like to see its development continue, then please get behind this crowdfunding campaign and donate via the link above.  Also, to help focus the development, please add comments to the site to indicate what you find useful about GeoRaptor, what bugs/issues you have found and what improvements and new features you would like to see added.
Thank you,
John O’Toole

Come on folks... $473 as of now of the $1000 goal.
I admit that I don't use it often - but when I need that specific tool, it can be invaluable.
Just 27 people at $20 will put it over the top.
Bryan

Similar Messages

  • Georaptor for sqldeveloper and jdeveloper ?

    Hi,
    georaptor is an add in for sqldeveloper to handle spatial data.
    question: can georaport be used as add in for JDeveloper, and - if so - how to install it ?
    Leo

    If you are building a Java extension, then you can port them relatively easily between the two as SQL Developer is built on the JDev IDE. Extensions do need to be adapted for whether they go into JDev or SQL Developer, but there are a few customer extensions available for both.
    If you have specific technical questions regarding this, then pose those and the developers will get back to you.
    SQL Developer is now available in JDeveloper. You can download the latest JDeveloper 11g (Beta) release to see this.
    (There is also a SQL Developer plugin now available for Eclipse. This is an early adopter release.)
    Sue

  • GeoRaptor for SQL Developer 1.1

    The GA release of GeoRaptor does not seem to work for the latest version of SQL Developer 1.1. GeoRaptor is an extension to SQL Developer to view spatial data. GeoRaptor adds a context menu option to tables containing Oracle Spatial data types and a window to view spatial data.
    The context menu option does not show up anymore in SQL Developer 1.1.
    At the moment of this writing, there is no official patch available for this issue.
    For the time being I've made the CVS head revision (1.7) of GeoRaptor available till the GA is officially being released.
    To install this unofficial version of GeoRaptor, Start SQL Developer, select Help -> Check for Updates..., press Add and enter GeoRaptor for the name and http://testnext.com/oracle/sqldeveloper/georaptor-20070207/install.xml as location.
    Enjoy using GeoRaptor,
    Cheers,
    Jeroen van Schaijk

    Hi *,
    I also second that : My SQL Dev 1.5 also does not work very well with the GeoRaptor plug in. When i add a table to spatial view nothing showed up but no error displayed.
    I thought it was just me (my platform).
    Here is my platform (dunno if it's relevant)
    * OS : MS Windows Vista Ultimate
    * Oracle Database 11g Release 1 (11.1.0.6.0)
    Enterprise/Standard Edition for Microsoft Windows 32-bit
    * JDK 1.6.0_03 build 1.6.0_03-b05
    My SQL developer version 1.2.1 (in Windows Vista) works well with georaptor, connected to Oracle 11gR1 (locally under Vista) or 10gR2 (in other machine under Windows XP Home).
    So the problem probably in SQL Developer 1.5.
    thanks
    =Damon

  • Where is forums for sqldeveloper

    where is forum for sqldeveloper

    A google search found this:
    http://www.oracle.com/technology/products/database/sql_developer/index.html
    and this:
    SQL Developer

  • Two versions for sqldeveloper

    Hi,
    can we have two versions for sqldeveloper (sqldeveloper 1.5.4 and sqldeveloper 3.0.04) on the same machine ?
    Are both good for 10g R2 ?
    Thank you.

    Yes, that works fine - just unzip to a different directory and off you go!

  • Secure Port for SqlDeveloper

    Hi All,
    I want to secure port for my Sqldeveloper which is on my laptop with IP 100.2.10.200 to connect to a scecured PROD server SLES 11.
    My laptop will the one only allowed to connect to the PROD using OEM and SqlDev . How do I configure it?
    What port does Sqldev uses? is it the same listener port 1521? same like the OEM 1158?
    Thanks....

    yxes2013 wrote:
    I want to secure port for my Sqldeveloper which is on my laptop with IP 100.2.10.200 to connect to a scecured PROD server SLES 11.Nonsensical question. SQL-Developer does not listen on a network port. The port it uses will be a client port in the dynamic port range - created when SQL-Developer connects to the Listener port on the Oracle server.
    Also, opened ports are by their very nature not secure. There is thus no such thing as an open and secure port. Open a port as a listening endpoint on a public NIC, and that port, with that service, is exposed to attack.
    The only way to "secure" a port is to remove that from the public network interface all together and run it on localhost (making it a local port only, and inaccessible to everyone else). And this has very limited use. An external client can only use that port via a ssh local tunnel. Which in turns requires you to make port 22/tcp public.

  • FourthElephant plugins for SQLDeveloper 1.1

    Hello world,
    We have released a new version of our performance monitoring and error lookup plugins. They should work now with SQLDeveloper 1.1. Come and get them at
    http://www.fourthelephant.com/downloads.html
    Vadim Bobrov
    Oracle Database Tools
    http://www.fourthelephant.com

    Just installed the latest version of the plugins, and after restarting, no tabs opened. No worksheets, no tables, no nothing.
    This is the IDE reported exception on opening a worksheet through the associated button:
    java.lang.IllegalAccessError: oracle/ide/net/IdeURLStreamHandler
         at oracle.ide.net.URLFileSystem$1.createURLStreamHandler(URLFileSystem.java:87)
         at oracle.ide.boot.URLStreamHandlerFactoryQueue.createURLStreamHandler(URLStreamHandlerFactoryQueue.java:119)
         at java.net.URL.getURLStreamHandler(URL.java:1106)
         at java.net.URL.<init>(URL.java:393)
         at java.net.URL.<init>(URL.java:283)
         at oracle.ide.net.URLFactory.newURL(URLFactory.java:636)
         at oracle.ide.net.URLFactory.newURL(URLFactory.java:136)
         at oracle.dbtools.sqlworksheet.sqlview.SqlEditorNode.<init>(SqlEditorNode.java:65)
         at oracle.dbtools.sqlworksheet.sqlview.SqlEditor.openNewEditor(SqlEditor.java:1971)
         at oracle.dbtools.sqlworksheet.sqlview.SqlEditor.openNewEditor(SqlEditor.java:2030)
         at oracle.dbtools.sqlworksheet.sqlview.SqlEditor.openNewEditor(SqlEditor.java:2048)
         at oracle.dbtools.sqlworksheet.sqlview.SqlEditorWizard.invoke(SqlEditorWizard.java:114)
         at oracle.ide.wizard.WizardManager.invokeWizard(WizardManager.java:310)
         at oracle.dbtools.sqlworksheet.sqlview.SqlEditorController.toolbarAction(SqlEditorController.java:1012)
         at oracle.dbtools.sqlworksheet.sqlview.SqlEditorController.handleEvent(SqlEditorController.java:561)
         at oracle.ide.controller.IdeAction.performAction(IdeAction.java:551)
         at oracle.ide.controller.IdeAction$2.run(IdeAction.java:804)
         at oracle.ide.controller.IdeAction.actionPerformedImpl(IdeAction.java:823)
         at oracle.ide.controller.IdeAction.actionPerformed(IdeAction.java:521)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
         at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
         at javax.swing.AbstractButton.doClick(AbstractButton.java:357)
         at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1170)
         at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1211)
         at java.awt.Component.processMouseEvent(Component.java:6038)
         at javax.swing.JComponent.processMouseEvent(JComponent.java:3260)
         at java.awt.Component.processEvent(Component.java:5803)
         at java.awt.Container.processEvent(Container.java:2058)
         at java.awt.Component.dispatchEventImpl(Component.java:4410)
         at java.awt.Container.dispatchEventImpl(Container.java:2116)
         at java.awt.Component.dispatchEvent(Component.java:4240)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
         at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)
         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
         at java.awt.Container.dispatchEventImpl(Container.java:2102)
         at java.awt.Window.dispatchEventImpl(Window.java:2429)
         at java.awt.Component.dispatchEvent(Component.java:4240)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
         at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
         at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
    This is the exception you get twice in the console on trying to open a table for example:
    Exception in thread "AWT-EventQueue-0" java.lang.IllegalAccessError: oracle/ide/net/IdeURLStreamHandler
    at oracle.ide.net.URLFileSystem$1.createURLStreamHandler(URLFileSystem.java:87)
    at oracle.ide.boot.URLStreamHandlerFactoryQueue.createURLStreamHandler(URLStreamHandlerFactoryQueue.java:119)
    at java.net.URL.getURLStreamHandler(URL.java:1106)
    at java.net.URL.<init>(URL.java:393)
    at java.net.URL.<init>(URL.java:283)
    at oracle.ide.net.URLFactory.newURL(URLFactory.java:636)
    at oracle.ide.net.URLFactory.newURL(URLFactory.java:136)
    at oracle.dbdev.oviewer.base.ViewerNode.<init>(ViewerNode.java:133)
    at oracle.dbdev.oviewer.base.ViewerNode.createInstance(ViewerNode.java:102)
    at oracle.dbdev.oviewer.base.ViewerNode.getInstance(ViewerNode.java:110)
    at oracle.dbdev.oviewer.base.ViewerNode.getUnpinnedInstance(ViewerNode.java:116)
    at oracle.dbdev.oviewer.base.NavSelectionListener.open(NavSelectionListener.java:280)
    at oracle.dbdev.oviewer.base.NavSelectionListener.whenDatabaseObjectSelected(NavSelectionListener.java:242)
    at oracle.dbdev.oviewer.base.NavSelectionListener.mouseClicked(NavSelectionListener.java:433)
    at java.awt.AWTEventMulticaster.mouseClicked(AWTEventMulticaster.java:253)
    at java.awt.AWTEventMulticaster.mouseClicked(AWTEventMulticaster.java:252)
    at java.awt.Component.processMouseEvent(Component.java:6041)
    at javax.swing.JComponent.processMouseEvent(JComponent.java:3260)
    at oracle.ideimpl.explorer.CustomTree.processMouseEvent(CustomTree.java:185)
    at java.awt.Component.processEvent(Component.java:5803)
    at java.awt.Container.processEvent(Container.java:2058)
    at java.awt.Component.dispatchEventImpl(Component.java:4410)
    at java.awt.Container.dispatchEventImpl(Container.java:2116)
    at java.awt.Component.dispatchEvent(Component.java:4240)
    at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
    at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3995)
    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
    at java.awt.Container.dispatchEventImpl(Container.java:2102)
    at java.awt.Window.dispatchEventImpl(Window.java:2429)
    at java.awt.Component.dispatchEvent(Component.java:4240)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
    at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
    at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)
    I had to restart again to go back to normal...
    K.

  • Source file read error for sqldeveloper

    While downloading SQLDeveloper, after almost 70%complete, i got an source file read error.
    i've tried again to download but the page hangs on the license agreement page after clicking I ACCEPT.
    Please resolve this issue.
    Thanks in Advance
    Using:
    MS Win XP Home
    Firefox 1.5.3
    Tony Garabedian

    sybrand_b wrote:
    Why are you assuming utl_file works with binary files? It doesn't!It does in 10g, where file open mode B was introduced. But even with R mode you should be able to open DOC file. You might (or might not) have problem reading it:
    SQL> declare
      2      fh UTL_FILE.FILE_TYPE;
      3      input_buffer varchar2(4000);
      4  begin
      5      fh := UTL_FILE.FOPEN('TEMP','Stats.doc','r');
      6      UTL_FILE.GET_LINE(fh,input_buffer,4000);
      7      DBMS_OUTPUT.PUT_LINE(input_buffer);
      8      UTL_FILE.FCLOSE(fh);
      9    exception
    10      when others then UTL_FILE.FCLOSE(fh);
    11  end;
    12  /
    ÐÏࡱᠠ              >  þÿ                 2          4      þÿÿÿ    1
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
    ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿì¥Á €    ð¿             ¸
    PL/SQL procedure successfully completed.
    SQL> SY.

  • GeoRaptor 3.0 for SQL Developer 3.0 and 2.1 has now been released

    Folks,
    I am pleased to announce that, after 5 months of development and testing, a new release of GeoRaptor for SQL Developer 2.1 and 3.0 is now available.
    GeoRaptor for SQL Developer 3 is available via the SQL Developer Update centre. GeoRaptor 3 for SQL Developer 2.1 is being made available
    via a download fro the GeoRaptor website.
    No release notes have been compiled as the principal developer (oops, that's me!) is currently busy doing real work for a change (another 3 weeks), earning a living
    and keeping the wolves at bay. More extensive notes (with images) will be compiled when I get back. (Unless anyone is offering! See next.)
    We are still looking for people to:
    1. Provide translations of the English dialog menus etc.
    2. Write more extensive user documentation. If you use a particular part of GeoRaptor a lot and think
    you have found out all its functionality and quirks, contact us and offer to write a few pages of
    documentation on it. (Open Office or Microsoft Word is fine.) Easiest way to do this is to simply
    make screen captures and annotate with text.
    3. Conduct beta testing.
    Here are the things that are in the new release.
    New functionality:
    Overhaul of Validation Functionality.
    1. User can specify own validation SELECT SQL as long as it returns three required columns. The SQL is thus totally editable.
    2. Validation update code now allows user to associate a PL/SQL function with an error number which is applied in the UPDATE SQL.
    3. UPDATE SQL can use WHERE clause of validation SELECT SQL (1) to update specific errors.
       NOTE: The generated UPDATE statement can be manually edited. It is NEVER run by GeoRaptor. To run any UPDATE, copy the statement
       to the clipboard and run in an appropriate SQL Worksheet session within SQL Developer.
    4. Main validation table allows:
       a. Sorting (click on column header) and
       b. Filtering.
       c. Copying to Clipboard via right mouse click sub menu of:
          - Geometry's SDO_ELEM_INFO array constructor.
          - SDO_GEOMETRY constructor
          - Error + validation string.
       d. Access to Draw/Zoom functions which were previously buttons.
       e. Added a new right mouse click menu "Show Feature's Individual Errors" that gathers up all the errors
          it can process - along with the ring / element that is host to the error (if it can) - and displays
          them in the Attribute/Geometry tabs at the bottom of the Map Window (where "Identify" places its results).
          The power of this will be evident to all those who have wanted a way of stepping through errors in a geometry.
       f. Selected rows can now be deleted (select rows: press <DELETE> key or right mouse click>Delete).
       g. Table now has only one primary key column, and has a separate error column holding the actual error code.
       h. Right mouse click men added to table menu to display description of error in the new column (drawn from Oracle documentation)
       i. Optimisations added to improve performance for large error lists.
    5. Functionality now has its own validation layer that is automatically added to the correct view.
       Access to layer properties via button on validation dialog or via normal right mouse click in view/layer tree.
    Improved Rendering Options.
    1. Linestring colour can now be random or drawn from column in database (as per Fill and Point colouring)
    2. Marking of SDO_GEOMETRY objects overhauled.
       - Ability to mark or LABEL vertices/points of all SDO_GEOMETRY types with coordinate identifier and
         option {X,Y} location. Access is via Labelling tab in layer>properties. Thus, coordinate 25 of a linestring
         could be shown as: <25> or {x,y} or <25> {x,y}
       - There is a nice "stacked" option where the coordinate {x,y} can be written one line below the id.
       - For linestrings and polygons the <id> {x,y} label can be oriented to the angle between the vectors or
         edges that come in, and go out of, a vertex. Access is via "Orient" tick box in Labelling tab.
       - Uses Tools>Preferences>GeoRaptor>Visualisation>SDO_ORDINATE_ARRAY bracket around x,y string.
    3. Start point of linestring/polygon and all other vertices can be marked with user selectable point marker
       rather than previously fixed markers.
    4. Can now set a NULL point marker by selecting "None" for point marker style pulldown menu.
    5. Positioning of the arrow for linestring/polygons has extra options:
       * NONE
       * START    - All segments of a line have the arrow positioned at the start
       * MIDDLE   - All segments of a line have the arrow positioning in the middle.
       * END      - All segments of a line have the arrow positioning in the END.
       * END_ONLY - Only the last segment has an arrow and at its end.
    ScaleBar.
    1. A new graphic ScaleBar option has been added for the map of each view.
       For geographic/geodetic SRIDs distances are currently shown in meters;
       For all SRIDs an attempt is made to "adapt" the scaleBar units depending
       on the zoom level. So, if you zoom right in you might get the distance shown
       as mm, and as you zoom out, cm/m/km as appropriate.
    2. As the scaleBar is drawn, a 1:<DEMONINATOR> style MapScale value is written
       to the map's right most status bar element.
    3. ScaleBar and MapScale can be turned off/on in View>Properties right mouse
       click menu.
    Export Capabilities.
    1. The ability to export a selection from a result set table (ie result of
       executing ad-hoc SQL SELECT statement to GML, KML, SHP/TAB (TAB file
       adds TAB file "wrapper" over SHP) has been added.
    2. Ability to export table/view/materialised view to GML, KML, SHP/TAB also
       added. If no attributes are selected when exporting to a SHP/TAB file, GeoRaptor
       automatically adds a field that holds a unique row number.
    3. When exporting to KML:
       * one can optionally export attributes.
       * Web sensitive characters < > & etc for KML export are replaced with &gt; &lt; &amp; etc.
       * If a column in the SELECTION or table/view/Mview equals "name" then its value is
         written to the KML tag <name> and not to the list of associated attributes.
         - Similarly for "description" -> <description> AND "styleUrl" -> <styleUrl>
    4. When exporting to GML one can optionally export attributes in FME or OGR "flavour".
    5. Exporting Measured SDO_GEOMETRY objects to SHP not supported until missing functionality
       in GeoTools is corrected (working with GeoTools community to fix).
    6. Writing PRJ and MapInfo CoordSys is done by pasting a string into appropriate export dialog box.
       Last value pasted is remembered between sessions which is useful for users who work with a single SRID.
    7. Export directory is remembered between sessions in case a user uses a standard export directory.
    8. Result sets containing MDSYS.SDO_POINT and/or MDSYS.VERTEX_TYPE can also be written to GML/KML/SHP/TAB.
       Example:
       SELECT a.geom.sdo_point as point
         FROM (SELECT sdo_geometry(2002,null,sdo_point_type(1,2,null),sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)) as geom
                 FROM DUAL) a;
       SELECT mdsys.vertex_type(a.x,a.y,a.z,a.w,a.v5,a.v6,a.v7,a.v8,a.v9,a.v10,a.v11,a.id) as vertex
         FROM TABLE(mdsys.sdo_util.getVertices(mdsys.sdo_geometry(2002,null,null,sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)))) a;
    9. A dialog appears at the end of each export which details (eg total) what was exported when the exported recordset/table contains more
       than on shape type. For example, if you export only points eg 2001/3001 from a table that also contains multipoints eg 2005/3005 then
       the number of points exported, and multipoints skipped will be displayed.
    10. SHP/TAB export is "transactional". If you set the commit interval to 100 then only 100 records are held in memory before writing.
        However, this does not currently apply to the associated DBASE records.
    11. SHP/TAB export supports dBase III, dBase III + Memo, dBase IV and dBase IV + Memo.
        Note: Memo allows text columns > 255 characters to be exported. Non-Memo formats do not and any varchar2 columns will be truncated
        to 255 chars. Some GIS packages support MEMO eg Manifold GIS, some do not.
    12. Note. GeoRaptor does not ensure that the SRID of SDO_GEOMETRY data exported to KML is in the correct Google Projection.
        Please read the Oracle documentation on how to project your data is this is necessary. An example is:
        SELECT OBJECTID,
               CODIGO as name,
               NOME as description,
               MI_STYLE,
               SDO_CS.TRANSFORM(shape,'USE_SPHERICAL',4055) as shape
          FROM MUB.REGIONAL;
    13. NOTE: The SHP exporter uses the Java Topology Suite (JTS) to convert from SDO_GEOMETRY to the ESRI Shape format. JTS does not handle
        circular curves in SDO_GEOMETRY objects you must "stroke" them using sdo_util.arc_densify(). See the Oracle documentation on how
        to use this.
    Miscellaneous.
    1. Selection View - Measurement has been modified so that the final result only shows those geometry
       types that were actually measured.
    2. In Layer Properties the Miscellaneous tab has been removed because the only elements in it were the
       Geometry Output options which have now been replaced by the new GML/KML/etc export capabilities.
    3. Shapefile import's user entered tablename now checked for Oracle naming convention compliance.
    4. Identify based on SDO_NN has been removed from GeoRaptor given the myriad problems that it seems to create across versions
       and partitioned/non-partitioned tables. Instead SDO_WITHIN_DISTANCE is now used with the actual search distance (see circle
       in map display): everything within that distance is returned.
    5. Displaying/Not displaying embedded sdo_point in line/polygon (Jamie Keene), is now controlled by
       a preference.
    6. New View Menu options to switch all layers on/off
    7. Tools/Preferences/GeoRaptor layout has been improved.
    8. If Identify is called on a geometry a new right mouse click menu entry has been added called "Mark" which
       has two sub-menus called ID and ID(X,Y) that will add the labeling to the selected geometry independently of
       what the layer is set to being.
    9. Two new methods for rendering an SDO_GEOMETRY object in a table or SQL recordset have been added: a) Show geometry as ICON
       and b) Show geometry as THUMBNAIL. When the latter is chosen, the actual geometry is shown in an image _inside_ the row/column cell it occupies.
       In addition, the existing textual methods for visualisation: WKT, KML, GML etc have been collected together with ICON and THUMBNAIL in a new
       right mouse click menu.
    10. Tables/Views/MViews without spatial indexes can now be added to a Spatial View. To stop large tables from killing rendering, a new preference
        has been added "Table Count Limit" (default 1,000) which controls how many geometry records can be displayed. A table without a spatial
        index will have its layer name rendered in Italics and will write a warning message in red to the status bar for each redraw. Adding an index
        which the layer exists will be recognised by GeoRaptor during drawing and switch the layer across to normal rendering.
    Some Bug Fixes.
    * Error in manage metadata related to getting metadata across all schemas
    * Bug with no display of rowid in Identify results fixed;
    * Some fixes relating to where clause application in geometry validation.
    * Fixes bug with scrollbars on view/layer tree not working.
    * Problem with the spatial networks fixed. Actions for spatial networks can now only be done in the
      schema of the current user, as it could happen that a user opens the tree for another schema that
      has the same network as in the user's schema. Dropping a drops only the network of the current connected user.
    * Recordset "find sdo_geometry cell" code has been modified so that it now appears only if a suitable geometry object is
      in a recordset.  Please note that there is a bug in SQL Developer (2.1 and 3.0) that causes SQL Developer to not
      register a change in selection from a single cell to a whole row when one left clicks at the left-most "row number"
      column that is not part of the SELECT statements user columns, as a short cut to selecting a whole row.  It appears
      that this is a SQL Developer bug so nothing can be done about it until it is fixed. To select a whole row, select all
      cells in the row.
    * Copy to clipboard of SDO_GEOMETRY with M and Z values forgot has extraneous "," at the end.
    * Column based colouring of markers fixed
    * Bunch of performance improvements.
    * Plus (happily) others that I can't remember!If you find any bugs register a bug report at our website.
    If you want to help with testing, contact us at our website.
    My thanks for help in this release to:
    1. John O'Toole
    2. Holger Labe
    3. Sandro Costa
    4. Marco Giana
    5. Luc van Linden
    6. Pieter Minnaar
    7. Warwick Wilson
    8. Jody Garnett (GeoTools bug issues)
    Finally, when at the Washington User Conference I explained the willingness of the GeoRaptor Team to work
    for some sort of integration of our "product" with the new Spatial extension that has just been released in SQL
    Developer 3.0. Nothing much has come of that initial contact and I hope more will come of it.
    In the end, it is you, the real users who should and will decide the way forward. If you have ideas, wishes etc,
    please contact the GeoRaptor team via our SourceForge website, or start a "wishlist" thread on this forum
    expressing ideas for future functionality and integration opportunities.
    regards
    Simon
    Edited by: sgreener on Jun 12, 2011 2:15 PM

    Thank you for this.
    I have been messing around with this last few days, and i really love the feature to pinpoint the validation errors on map.
    I has always been so annoying to try pinpoint these errors using some other GIS software while doing your sql.
    I have stumbled to few bugs:
    1. In "Validate geometry column" dialog checking option "Use DimInfo" actually still uses value entered in tolerance text box.
    I found this because in my language settings , is the decimal operators
    2. In "Validate geometry column" dialog textboxs showing sql, doesn't always show everything from long lines of text (clipping text from right)
    3. In "Validate geometry column" dialog the "Create Update SQL" has few bugs:
    - if you have selected multiple rows from results and check the "Use Selected Geometries" the generated IN-clause in SQL with have same rowid (rowid for first selected result) for all entries
    Also the other generated IN clause in WHERE-clause is missing separator if you select more than one corrective function
    4. "Validate geometry column" dialog stays annoyingly top most when using "Create Update SQL" dialog

  • Does SQLDeveloper license allow for redistibution?

    Hello, is the license for SQLDeveloper the same "free to develop, deploy, and distribute" as Oracle Database XE? Specifically, would it be within the license terms to include a working copy on a remastered Linux installation cd with connections/preferences/etc. preconfigured? This tool is awesome and I'd like to share it with others I'm working on projects with, but it needs to be simple and preconfigured for the non-tech savvy...
    Thx so much Oracle for all your tools and support!!

    In contrast to e.g. instant client License which "starts" with
    Oracle Technology Network Development and Distribution License Terms for Instant Client
    the license for sql developer "starts" with
    Oracle SQL Developer License Terms
    redistribution in particular is not addressed (in the license agreement).

  • Svn-integration of sqldeveloper not working for Datamodeler

    Hi everyone,
    has anyone been able to use the SVN-integration of SqlDeveloper for the datamodeler? It appears that the Datemodeler has simply been appended to SqlDeveloper without real integration.
    SVN-integration of SqlDeveloper works for SqlDeveloper files, but not for the datamodeler (eg it does not recognize any incoming or outgoing changes etc). It was working in the Standalone version of datamodeler, though.
    Anyone with positive experiences?
    Yours,
    qwe15056.

    Hi qwe15056,
    Data Modeler uses its own svn integration. If you are working with DM from within SQL Developer, you can open View / Data Modeler / Pending Changes to see its own Pending Changes window that you can use to update / commit/ revert /compare changes.
    By the way, there is a separate forum concerning Data Modeler:
    SQL Developer Data Modeler
    Hope that helps,
    Ivaylo

  • Problems using Quick Migrate in SQL Developer 1.5 for MySQL to Oracle 10g

    Hi all,
    I am trying to use SQL Developer 1.5 migration tools (Quick Migrate) to perform online capture and build source model to migrate from MySQL 5.x to Oracle 10g on Windows platform. I get these errors and the Quick Migrate process fails:
    oracle.dbtools.metadata.persistence.PersistableObject.doInsert(PersistableObject.java:238)
    I did a search and used the sqldeveloper.cmd script but still fails. Then I created a new database and truncated the repository. I now get the above error plus two new ones listed below:
    oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
    Error loading nls:OALL8 is in an inconsistent state
    Error occurred during capture: Protocol violation
    It fails during the capture process for MySQL 5.1 database
    when it begins to capture the tables from MySQL.
    Does anyone know how to resolve these issues when migrating from MySQL to Oracle 10g using Quick Migrate with SQL Developer 1.5 release?
    Regards,
    Ben Prusinski
    Message was edited by:
    benprusinski
    Message was edited by:
    benprusinski

    Hi all,
    I put the following in my sqldeveloper.cmd file:
    SET ORACLE_HOME=%CD%
    What is very confusing is that with SQL Developer 1.5, there are several levels and several SQL Developer executables! I am really not sure which of these to use:
    I created the SQLDeveloper 1.5 directory called SQLDeveloper1_5 on Windows:
    1) cd C:\sqldeveloper1_5\sqldeveloper-5338
    there exists a sqldeveloper.exe
    2) cd c:\sqldeveloper1_5\sqldeveloper-5338\sqldeveloper\sqldeveloper.exe
    3) cd c:\sqldeveloper1_5\sqldeveloper-5338\sqldeveloper\sqldeveloer\bin\sqldeveloper.exe
    Which SQLDeveloper 1.5 executable should I be using and where should I place the
    sqldeveloper.cmd file?
    Also I did try to use a different database and schema for the repository with Quick Migrate but it appears a bug exists in SQL Developer 1.5 version that causes errors with Quick Migrate for MySQL to Oracle? Is this correct?
    As an update, I ran the following commands:
    cd to
    c:\sqldeveloper1_5\sqldeveloper-5338\sqldeveloper\sqldeveloper\bin
    sqldeveloper.cmd sqldeveloper.exe
    Start sqldeveloper.exe
    Perform standard capture for MySQL using the new mig2 schema as the new repository
    It starts the capture but fails on the errors below:
    Error loading nls:OALL8 is in an inconsistent state
    UPDATE
    ============================
    I tried this again and it worked with the exception of one error message listed below:
    Here are the steps that I followed:
    1. Create a Windows cmd script
    Put the following entries in the script:
    SET ORACLE_HOME=%CD%
    save the command windows script as sqldeveloper.cmd
    Copy this script to the base installation directory for SQLDeveloper
    Example:
    1. cd c:\SQLDeveloper1_5\sqldeveloper-5338\sqldeveloper
    2. Start SQLDeveloper with the command script that you created earlier
    Example:
    Open a Windows shell prompt window and execute the following scripts:
    a) sqldeveloper.cmd sqldeveloper.exe
    b) sqldeveloper.exe
    3) In SQL Developer 1.5
    From the Migrate menu,
    a) Delete current repository and create a new schema in Oracle target database call it mig2.
    b) Then create a new repository in SQL Developer 1.5
    c) Right mouse click on the MySQL 5.x database and choose capture
    It worked with the exception of one error message:
    o.jdbc.driver.OracleDriver     
    Error while registering Oracle JDBC Diagnosability MBean.
    So it looks like something is screwed up with my JDBC drivers and configuration for MySQL. How do I diagnose the JDBC driver issue for MySQL?
    Thanks!!!
    Ben
    Thanks
    Ben

  • Change font size in Sqldeveloper 3

    Hello! I'm using Oracle Developer Day VM with Oracle sqldeveloper 3.1.05
    How do increase font size for sqldeveloper? It is said I have to change ide.properties file but I can't find one.

    Are you trying to change the font size of the overall application, or just the font of the editors? If just the editors, that's in the preferences dialog
    http://www.thatjeffsmith.com/archive/2011/12/top-10-preferences-to-tweak-when-using-sql-developer/

  • New installation woes - SQLDeveloper on Oracle Linux x64 and Oracle 11g XE

    Note that as an experienced Oracle developer in enterprise environments running MS Windows OS, I am familiar with SQLDeveloper for Windows. I don't have a lot of experience with Linux however. I don't find it intimidating, I just don't have a lot of accumulated knowledge.
    I have recently been trying to set up a development environment on my Windows7 Professional x64 laptop.
    1. Installed Oracle VBox
    2. Installed Oracle Linux 5.2 inside the VBox (because Oracle 11g XE is not certified on 64 bit Windows, needed to go with a Linux OS)
    3. Installed Oracle DB 11.2 XE
    4. Installed JDK as instructed in the SQLDeveloper release notes for Linux x64
    5. Installed SQLDeveloper 3.1.07.42-1
    No apparent issues with any of the installations.
    Problem : I can run SQL Plus from the command line, but when I click on the icon for SQLDeveloper, nothing happens. No error messages, nothing else.
    Question #1 : Unsure how to debug/troubleshoot this. Will read through the installation and release notes for SQLDeveloper, but any suggestions would be welcome.
    Question #2 : Could this be due to an issue with the JDK installation? It appeared to be successful (no obvious issues) but I can't see anything in the Oracle Linux menu system that tells me the JDK was installed successfully. How can I confirm that the JDK installation was successful?
    Edited by: Peter Hartgerink on Jun 19, 2012 9:12 AM

    >
    The Linux x64 version of SQLDeveloper doesn't come bundled with JDK. There is a version of JDK recommended, with an advisory to install it before installing SQLDeveloper. This I did, with apparent success. I guess I'll have to install the JDK again and check my Java versions afterwards. Thanks.
    >
    I don't know what JDK you downloaded since you didn't say. What version was it? Post the link.
    I find it hard to believe that the JDK version recommended was 1.4.2 since that is an ANCIENT version of Java, you have to hunt to even find it for download and most importantly the sql developer main download page clearly announces what version of Java is needed.
    http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html
    >
    JDK Support
    Oracle SQL Developer 3.1 is shipped with JDK1.6.0_11. However, you can connect to and use any JDK 1.6.0_11 or above. To use an existing JDK, download the zip files listed below "with JDK already installed."
    >
    As you can see you need JDK 1.6.0_11 or above.
    If the version you say was recommended was actually 1.4.2 then that is an error; post the details so the developers can get that error fixed.
    I don't know what is on your system and can only go by the information you provide
    >
    4. Installed JDK as instructed in the SQLDeveloper release notes for Linux x64
    java version "1.4.2"
    >
    You either downloaded version 1.4.2, which seems unlikely, or your Linux included 1.4.2 and it is being used when you try to launch sql developer.
    Perhaps your system now has multiple versions of Java on it but the version being used by sql developer is the wrong one. If so that is the issue you need to resolve.

  • Unable to unzip sqldeveloper-3.2.20.09.87-no-jre.zip

    I am unable to unzip the file to c:\sqlDeveloper. I have JDK installed already and JAVA_HOME is set. I don't think it is necessary to unzip the download. I tried 3 times already. I get a dialog saying "Invalid compressed data to extract". When I click Ok, i get another dialog "Would you like Winzip to try to continue with the next file?". I clicked "Yes". Then I get another dialog "Unable to find the local header for sqldeveloper\dataminer\dem...\StarSchemaMining.xml".
    i get another dialog "Would you like Winzip to try to continue with the next file?". I clicked "Yes".Then I get another dialog "Unable to find the local header for sqldeveloper\dataminer\demos\cuec...\TextMining.xml".
    I downloaded from http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html
    Please help. Thanks.

    I tried again using Goole Chrome. Still unable to unzip using Winzip.
    Extracting to "C:\"
    Use Path: yes Overlay Files: no
    Extracting sqldeveloper\dataminer\demos\cuecards\GettingStarted\identify.xml
    Extracting sqldeveloper\dataminer\demos\cuecards\StarSchemaMining\StarSchemaMining.xml
    Extracting sqldeveloper\dataminer\demos\cuecards\TextMining\TextMining.xml
    Extracting sqldeveloper\dataminer\demos\cuecards\Transformations\Transformations.xml
    Extracting sqldeveloper\dataminer\demos\obe\StarSchemaMining\StarSchemaMining.xml
    Extracting sqldeveloper\dataminer\demos\obe\TextMining\TextMining.xml
    Extracting sqldeveloper\dataminer\demos\obe\UsingOracleDataMiner\Targeting_Best_Customers.xml
    Extracting sqldeveloper\dataminer\scripts\XMLSchema.xsd
    Extracting sqldeveloper\dataminer\scripts\alterDBRestrictSession.sql
    Extracting sqldeveloper\dataminer\scripts\alterDBUnRestrictSession.sql
    Extracting sqldeveloper\dataminer\scripts\alterUserDefaultRole.sql
    Extracting sqldeveloper\dataminer\scripts\createuser.sql
    Extracting sqldeveloper\dataminer\scripts\createusersgrantbackup.sql
    Extracting sqldeveloper\dataminer\scripts\createxmlworkflowsbackup.sql
    Extracting sqldeveloper\dataminer\scripts\createxmlworkflowsbackup2.sql
    Extracting sqldeveloper\dataminer\scripts\disconnectODMRSessions.sql
    Extracting sqldeveloper\dataminer\scripts\dmsh.sql
    Extracting sqldeveloper\dataminer\scripts\dmshgrants.sql
    Extracting sqldeveloper\dataminer\scripts\dropDemoData.sql
    Extracting sqldeveloper\dataminer\scripts\dropPublicSynonyms.sql
    Extracting sqldeveloper\dataminer\scripts\dropRepository.sql
    Extracting sqldeveloper\dataminer\scripts\dropRepositoryAndUserObjects.sql
    Extracting sqldeveloper\dataminer\scripts\dropRole.sql
    Extracting sqldeveloper\dataminer\scripts\dropSHDemoData.sql
    Extracting sqldeveloper\dataminer\scripts\dropSchedulerObjects.sql
    Extracting sqldeveloper\dataminer\scripts\dropUserTablesViews.sql
    Extracting sqldeveloper\dataminer\scripts\dropusergrants.sql
    Extracting sqldeveloper\dataminer\scripts\instDemoData.sql
    Extracting sqldeveloper\dataminer\scripts\instInsurCustData.sql
    Extracting sqldeveloper\dataminer\scripts\install_scripts_readme.html
    Extracting sqldeveloper\dataminer\scripts\installodmr.sql
    Extracting sqldeveloper\dataminer\scripts\instgrants.sql
    Extracting sqldeveloper\dataminer\scripts\instmessages.sql
    Extracting sqldeveloper\dataminer\scripts\instmessages_de.sql
    Extracting sqldeveloper\dataminer\scripts\instmessages_en.sql
    Extracting sqldeveloper\dataminer\scripts\instmessages_es.sql
    Extracting sqldeveloper\dataminer\scripts\instmessages_fr.sql
    Extracting sqldeveloper\dataminer\scripts\instmessages_it.sql
    Extracting sqldeveloper\dataminer\scripts\instmessages_ja.sql
    Invalid compressed data to extract.
    Compressed data is invalid.

Maybe you are looking for