Bug in SQl Developer + Ubuntu 64 bits and Open JDK 7

if i use de /usr/lib/jvm/java-1.6.0-openjdk
a have this errors.
SEVERE     283     1     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     282     0     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     281     1     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     280     0     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     279     1     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     278     0     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     277     1     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     276     0     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)
SEVERE     275     1     oracle.dbtools.raptor.controls.grid.ResultSetTableCellRenderer     oracle.dbtools.raptor.controls.grid.ResultSetGridCell.computeDisplayValue(ResultSetGridCell.java:37)

Welcome to the forum!
Please read the FAQ for how to post a question and the information that you need to provide.
The most important thing is that you actually need to post a question. Saying 'when I do this I have errors' is NOT a question. And it does not provide enough information for anyone to help you.
The subject mentions Open JDK 7 but your content uses '/usr/lib/jvm/java-1.6.0-openjdk'. Nothing in what you posted says anything at all about whether you are using sql developer, what version you are using, or how you are trying to launch it.
If you want help you have to provide detailed, specific information about each step you are taking and what results you get.
Have you ever installed or used ANY version of sql developer on ANY platform?
You are on a 64 bit system so are you using 64 bit versions of sql developer and the JDK?
Are you aware that JDK 7 is NOT recommended for use with sql developer at this time?

Similar Messages

  • 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

  • SQL developer with jre but no jdk

    Is there a way i can install sql developer with only jre installed in my windows system.
    Im trying to install to sql developer 64 bit and when i run the exe file it asks for java.exe file path.
    When i give it to the path to exe file in jre/bin it gives an error cannot find j2se sdk installed in jre directory.

    Normally SQLDeveloper requires a JDK and so will not accept a JRE.
    You can try to bypass this check by filling in the SetJavaHome property manually in the sqldeveloper.conf file usually located in
    SQLDEVELOPER_INSTALL_DIR/sqldeveloper/binby doing this you are not guaranteed to succeed, because some of the functions of SQLDeveloper specifically requires the JDK and so if you use these functions you will most probably incur in errors or unexpected behavior.
    The best thing to do IMHO is to install a proper JDK.
    If you do not have the right to do so you can also copy and already installed JDK from another machine and it usually works well enough.

  • Bug report SQL DEVELOPER DATA MODELER

    Hello,
    I think i found a bug using Sql developer data modeler 2.0.0 build 584.
    When importing a DDL file to create a relational model, foreign key constraints might not be created if foreign key uses multiple-field and the fields are not referenced in the same order as the primary key was.
    ex:
    Table FOO ..... PRIMARY KEY (id_1, id_2)
    FOREIGN KEY (id_2, id_1) REFERENCES FOO (id_2, id_1)
    Benjamin
    P.S: Bellow is a portion of SQL code demonstrating the problem:
    -- "_decompte"
    CREATE TABLE "_decompte"(
    numero_rang VARCHAR2(2),
    numero_contrat VARCHAR2(13),
    id_decompte VARCHAR2(19)
    ALTER TABLE "_decompte"
    add CONSTRAINT pk_decompte PRIMARY KEY (numero_rang, numero_contrat, id_decompte);
    -- "_decompte_detail"
    CREATE TABLE "_decompte_detail"(
    numero_rang VARCHAR2(2),
    id_ligne NUMBER(4),
    numero_contrat VARCHAR2(13),
    id_decompte VARCHAR2(19)
    -- "_decompte_detail"
    -- NOT Recognized by SQL DEVELOPER DATA MODELER (fields are not in the same order as primary key definition)
    ALTER TABLE "_decompte_detail"
    add CONSTRAINT fk_decompte_detail_1 FOREIGN KEY (numero_contrat, numero_rang , id_decompte) REFERENCES "_decompte"(numero_contrat, numero_rang , id_decompte);
    -- Recognized by SQL DEVELOPER DATA MODELER
    ALTER TABLE "_decompte_detail"
    add CONSTRAINT fk_decompte_detail_2 FOREIGN KEY (numero_rang, numero_contrat, id_decompte) REFERENCES "_decompte"(numero_rang, numero_contrat, id_decompte);

    Hi,
    Well, I was recently given some database scripts and asked to correct and improve them. These scripts were not generated but rather hand made. Having no access to a DBMS I was just curious about the result of this option in Data modeler and tried it for a better DB overview. I don't need it at all, but I was surprised to discover that the result was a failure. So I tried various scripts until I found the mistake.
    regards.

  • Bug in SQL Developer relating to handling of XMLTYPE columns

    Hi,
    I have found a bug in SQL Developer relating to its handling of XMLTYPE columns.
    Given a table with the following data:
    ID, XML_DATA
    1, <xml here>
    2, <xml here>
    3, <xml here>
    And the following SQL to extract a value from the XML and also an XML fragment as an XMLTYPE:
    SELECT
    EXTRACTVALUE(t.column_value,'/*/USER_ID/text()')user_id
    , t.column_value user_data
    FROM dbuser.mytable m
    , TABLE(XMLSEQUENCE(EXTRACT(m.xml_data, '/*/USER_LIST/USER'))) t
    I get the following:
    user_id, user_data
    jsmith26, (XMLTYPE)
    mjones45, (XMLTYPE)
    sborga31, (XMLTYPE)
    Note that the user_id is correctly extracted, however the XMLTYPE column (user_data) is empty in SQL Developer.
    The same query returns the correct XML data in TOAD.
    Edited by: 1008733 on May 29, 2013 5:07 PM

    Steve,
    So your example is slightly more complex than the one documented for a table in the standard OE schema here:
    http://docs.oracle.com/cd/B19306_01/server.102/b14200/functions052.htm
    That example works fine on an 11.2.0.1 database with SQL Developer 3.2.20.09.87. Please try the following with your case:
    Tools -> Preferences -> Database -> Advanced -> Display Struct Value In Grid (check it off if not already)If that still does not work for Run Statement (query result displayed in the grid, not as script output using Run Script), then please provide a test case based on the Warehouse table in the OE schema (or your case with DDL and DML scripts including the xml data) and I will log a bug.
    Thanks,
    Gary
    SQL Developer Team

  • SQL Developer 1.1 and Java problems.

    I downloaded and tried to run the sqldeveloper.exe. I am getting a prompt with a browse option to java.exe. I currently have JRE 1.6 installed and somehow SQL Developer didn't like it. So I went and installed JRE 1.5 and it's still complaining that it can't find the SDK.
    Do I really need to install the FULL SDK with compiler and stuff in order to run SQL Developer?
    Gena01

    It requires the JDK for some of the debugging logic. In 1.0, you could get by with just the JRE if you didn't use the debugger, but that may have changed with 1.1. It isn't that big of a download, so you may just want to give it a whirl.

  • SQL Developer 3 crashes when opening a local 172mB SQL file

    The crash occurs when trying to open a 172mB SQL file from my local C:\ drive on Windows 7 Ultimate 32-bit, running on a typical quad-core AMD Phenom CPU with the usual 3.3gb of RAM.
    Crash dump as follows:
    java.io.IOException: exception loading C:\...\mySQLfile.sql
         at oracle.ide.model.TextNode.openImpl(TextNode.java:530)
         at oracle.ide.model.Node.open(Node.java:974)
         at oracle.ide.model.Node.open(Node.java:922)
         at oracle.ide.model.Node.ensureOpen(Node.java:2132)
         at oracle.ide.model.TextNode.acquireTextBuffer(TextNode.java:732)
         at oracle.dbtools.worksheet.editor.WorksheetGUI.<init>(WorksheetGUI.java:587)
         at oracle.dbtools.worksheet.editor.Worksheet.createGUI(Worksheet.java:753)
         at oracle.dbtools.worksheet.editor.Worksheet.getWorksheetGUI(Worksheet.java:1056)
         at oracle.dbtools.worksheet.editor.Worksheet.getGUI(Worksheet.java:910)
         at oracle.ide.editor.Editor.getDefaultFocusComponent(Editor.java:233)
         at oracle.dbtools.worksheet.editor.Worksheet.getDefaultFocusComponent(Worksheet.java:873)
         at oracle.dbtools.worksheet.editor.Worksheet.open(Worksheet.java:1141)
         at oracle.ideimpl.editor.EditorState.openEditor(EditorState.java:283)
         at oracle.ideimpl.editor.EditorState.createEditor(EditorState.java:184)
         at oracle.ideimpl.editor.EditorState.getOrCreateEditor(EditorState.java:95)
         at oracle.ideimpl.editor.SplitPaneState.canSetEditorStatePos(SplitPaneState.java:232)
         at oracle.ideimpl.editor.SplitPaneState.setCurrentEditorStatePos(SplitPaneState.java:195)
         at oracle.ideimpl.editor.TabGroupState.createSplitPaneState(TabGroupState.java:102)
         at oracle.ideimpl.editor.TabGroup.addTabGroupState(TabGroup.java:379)
         at oracle.ideimpl.editor.EditorManagerImpl.createEditor(EditorManagerImpl.java:1403)
         at oracle.ideimpl.editor.EditorManagerImpl.createEditor(EditorManagerImpl.java:1337)
         at oracle.ideimpl.editor.EditorManagerImpl.openEditor(EditorManagerImpl.java:1263)
         at oracle.ide.cmd.OpenCommand.openWithNoProject(OpenCommand.java:327)
         at oracle.ide.cmd.OpenCommand.access$100(OpenCommand.java:61)
         at oracle.ide.cmd.OpenCommand$1.run(OpenCommand.java:256)
         at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
         at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
         at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
    Caused by: java.lang.OutOfMemoryError: Java heap space
         at oracle.javatools.buffer.VectorBuffers.consolidateBuffers(VectorBuffers.java:131)
         at oracle.javatools.buffer.VectorBuffers.getAllBuffers(VectorBuffers.java:156)
         at oracle.javatools.buffer.EOLNormalizer.processFinish(EOLNormalizer.java:190)
         at oracle.javatools.buffer.EOLNormalizer$ReaderNormalizer.normalizeData(EOLNormalizer.java:312)
         at oracle.javatools.buffer.AbstractTextBuffer.read(AbstractTextBuffer.java:1365)
         at oracle.javatools.buffer.AbstractTextBuffer.read(AbstractTextBuffer.java:1309)
         at oracle.ide.model.TextNode$FacadeTextBuffer.read(TextNode.java:1218)
         at oracle.ide.model.TextNode.loadTextBuffer(TextNode.java:293)
         at oracle.ide.model.TextNode.openImpl(TextNode.java:518)
         at oracle.ide.model.Node.open(Node.java:974)
         at oracle.ide.model.Node.open(Node.java:922)
         at oracle.ide.model.Node.ensureOpen(Node.java:2132)
         at oracle.ide.model.TextNode.acquireTextBuffer(TextNode.java:732)
         at oracle.dbtools.worksheet.editor.WorksheetGUI.<init>(WorksheetGUI.java:587)
         at oracle.dbtools.worksheet.editor.Worksheet.createGUI(Worksheet.java:753)
         at oracle.dbtools.worksheet.editor.Worksheet.getWorksheetGUI(Worksheet.java:1056)
         at oracle.dbtools.worksheet.editor.Worksheet.getGUI(Worksheet.java:910)
         at oracle.ide.editor.Editor.getDefaultFocusComponent(Editor.java:233)
         at oracle.dbtools.worksheet.editor.Worksheet.getDefaultFocusComponent(Worksheet.java:873)
         at oracle.dbtools.worksheet.editor.Worksheet.open(Worksheet.java:1141)
         at oracle.ideimpl.editor.EditorState.openEditor(EditorState.java:283)
         at oracle.ideimpl.editor.EditorState.createEditor(EditorState.java:184)
         at oracle.ideimpl.editor.EditorState.getOrCreateEditor(EditorState.java:95)
         at oracle.ideimpl.editor.SplitPaneState.canSetEditorStatePos(SplitPaneState.java:232)
         at oracle.ideimpl.editor.SplitPaneState.setCurrentEditorStatePos(SplitPaneState.java:195)
         at oracle.ideimpl.editor.TabGroupState.createSplitPaneState(TabGroupState.java:102)
         at oracle.ideimpl.editor.TabGroup.addTabGroupState(TabGroup.java:379)
         at oracle.ideimpl.editor.EditorManagerImpl.createEditor(EditorManagerImpl.java:1403)
         at oracle.ideimpl.editor.EditorManagerImpl.createEditor(EditorManagerImpl.java:1337)
         at oracle.ideimpl.editor.EditorManagerImpl.openEditor(EditorManagerImpl.java:1263)
         at oracle.ide.cmd.OpenCommand.openWithNoProject(OpenCommand.java:327)
         at oracle.ide.cmd.OpenCommand.access$100(OpenCommand.java:61)
    I've tried...
    - Closing all possible applications except for SQL Developer
    - Rebooting and running only SQL Developer
    - Ensuring SQL Developer is running using the included Java SDK
    I'm unsure of what to do next - In the past, I've been able to open 200-300mb SQL files without any issue, but since I've updated to SQL Developer 3 I'm suddenly experiencing these crashes.
    Edited by: user13275297 on Jun 10, 2011 9:46 AM

    You are running out of memory. In the stack notice this line:
    Caused by: java.lang.OutOfMemoryError: Java heap space
    Edit the sqldeveloper.conf file and add this
    AddVMOption -Xmx1024M
    That will bump it up some.
    -kris

  • PL/SQL Bug in SQL Developer?

    SQL Developer v 1.1.1.25 running on Windows XP.
    I have a PL/SQL procedure that does not compile with debug in SQL Developer. Compiling it with debug produces the following error:
    an Error(1): PLS-00801: internal error [79110].The only way I was able to get the procedure to compile in SQL Developer was to add the 4th line. If I uncomment the 4th line it compiles with debug. Why??
    Here is the procedure:
    CREATE OR REPLACE
    PROCEDURE BOGUS AS
      CURSOR c1 IS
        SELECT dummy FROM DUAL;
    --  x c1%ROWTYPE;
      PROCEDURE test ( rec IN OUT c1%ROWTYPE) IS
      begin
        null;
      end;
    BEGIN
      NULL;
    END BOGUS;Message was edited by:
    marife
    I played around some more with the procedure and discovered the problem. The key is the compiling with debug. I believe that compile with debug cannot build the debug information for a %ROWTYPE as a parameter. But if I define a local variable of that %ROWTYPE, then the compile with debug knows what debug information to track for the %ROWTYPE.
    I discovered that in SQL*Plus it compiles, but when you issue the ALTER PROCEDURE bogus COMPILE DEBUG, it does not compile. This is a problem with the debug option for compiling and not a problem with SQL Developer.
    Sorry for the posting. Hopefully this information will save other times and fustration.
    Mike

    Just for anyone else searching on this bug - I get the same error with certain procedures in TOAD when compiling with DEBUG.
    Fortunately nobody here has the first clue how to use TOAD debug so it's only ever switched on by accident or after a reinstall (it's the default) - so turning debug off fixes the problem.

  • Bug report: SQL Developer 3.2.09 Crashes for some Replace Regexp

    Hi,
    SQL Developer 3.2.09 (tested on Win XP with SQL Developer built-in Java) crashes for some Replace Regexp.
    Try the following:
    New SQL-sheet
    CTRL-R for Replace
    Enter "||" (two chars) as search-expression
    Enter "" (nothing) as replace-with-expression
    Check Regular Expressions Check Box
    Hit OK
    -->100% CPU usage, no reaction.
    Can you confirm the bug?
    Edited by: blama on Sep 4, 2012 3:48 PM

    I believe the pipe character is a regexp meta character and your regexp probaby matches everything repeatedly. If you want to replace the concatenation operator you don't need a regexp.
    Having said that, I am using SQL Developer on Linux with Java 1.6.0_33 and I don't get the hang, just replacing the same thing again and again.
    On windows with 1.6.0_24, I do get the hang. It may be a java issue.
    Edited by: Jim Smith on Sep 4, 2012 5:39 PM

  • How to connect sql developer OE schema and Hr schema,

    Hi ,
    I downloaded Oracle 10g express edition and SQL developer downloaded in my computer, I don't know how to connect to OE and HR schema, by default the SQL developer and Oracle 10g has only sytem and sys database. And as well I wanted to migrate datas from third party datas , could anyone please , pllease guide me. I am new to this field and just started to learn. what is listener and how to activate Listener and Repositary
    Please guide me.
    Thanks in advance
    Chan

    The HR schema installs fine in XE, but the OE schema doesn't quite. I've done it, but there will be errors. The reason is that the OE schema uses some features of XML DB that are not supported in XE. If you want to use the OE schema in XE and you don't mind if it isn't a complete OE schema, then you can get the installation scripts from an Oracle SE or EE installation.
    You can also get it from the companion disk for Oracle SE or EE, but this is a bit challenging, because you can't get it by running OUI unless you first install Oracle SE or EE. You need to run an archive utility like WinZip or 7-Zip and look for the scripts inside a compressed file - I forget which one, but I'll look it up if you like. Oh, and since the OE schema isn't really supposed to be installed on XE, Oracle does not support any of the methods for putting it there.

  • Bug report: sql developer/application express application import

    I noticed some bugs on deploying an application using sql developer 1.5.1-5440.
    Using a single file deployment generated by apex including install/upgrade/remove scripts: Here's what happens:
    # I tried installing version 1.1 of my application already existing. Connected to the parsing schema of the version 1.0 I can clearly see my app "dashboard(101)"
    # using sql dev I tried an application import. Using the following import options buildstatus =runonly, autoassign app_id and checked run install scripts
    # The install runs, but instead of using the upgrade script it simply runs the install script causing a lot of errors of course since the objects already exist in the schema
    # After this installation the application is visible in the workspace using a browser dashboard(102), however it remains invisible in sql developer where i can still only see dashboard(101)
    After this failure I decided to go ahead and try once more doing the same thing but now just not check run install scripts.
    To my amazement it still runs the install scripts???
    Now I have 3 application showing in the browser and still only 1 in sql developer
    Final problem with sql developer is that I choose to drop dashboard(101) it only deinstalls the application. It does not run the deinstall script for supporting objects included in dashboard(101).
    All this makes an easy deployment a real hassle, since the browser interface can't handle a run only apllication with supporting object as all (it simply doesn't run the install script) I need to use sql developer, which is then fine for the first install, but then doen't upgrade properly. Finaly deinstalling a run only application again is impossible from a workspace and does work from sql developer, but then you still have to do the deinstall of the db objects manually.
    I know as an apex admin I can work arround al this by switching the build status etc etc, but then again I can do anything if I'm apex admin and db sys.Point in having a single file deployment is allowing a novice user to easily install.
    Geert

    Hi Scott
    Thanks for the reply
    sspadafo wrote:
    Run Only applications don't show up in the application list because they should not be editable. But perhaps it could display an icon indicating that.In my opinion they should and they do. The single app that is appearing in the list in sql developer is run only. Having it here allows me to select drop amongst other functionality the browser interface currently still lacks. Even when I drop all apps and than reinstall them again it seems like I can only see 1 version of an app with the same name.
    sspadafo wrote:
    The problem you described where you can't use the Application Install wizard to install supporting objects if the application is set to Run Only should be fixed in the upcoming 3.1.2 release/patch.I've installed the patch and I'm afraid the patch is no good either. Indeed is has improved. After the app installs it shows the supporting object dialogue. But if you then select yes and press Next it does absolutely nothing and redirects tot the application showing Application not available for edit.
    So if you would be so kind to reopen bug 7286162
    So while I'm on this section in my opinion the following bugs exist/features are missing
    SQL Developer interface
    # Not all application for parsing schema are shown in connection explorer. It seems like it can multiple show apps with different names only not when you install the same app twice with different app_id's. Then it only show the lowest app_id.
    # Installing runonly app with supporting objects installs supporting object regardless of option selected
    # Installing runonly app with upgrade scripts ignores update scripts and runs install scripts regardless of "install supporting objects" checkbox's state
    # De installing app shows unpredictable behaviour for running deinstall scripts. It seemingly prompts random. Sometimes it does, sometimes it doesn't. When it does show I get behaviour like initially prompting for running deinstall script, failing to run deinstall script, causing neither app or objects to be dropped, on retry not showing prompt anymore and only dropping app.
    Browser interface
    # Installing a runonly app always finishes with a white page showing only Application not available for edit instead of showing a proper installation summary
    # Installing a runonly app still prevents installation of supporting objects
    # De installing a runonly application is not possible. Possible a button for de install could be included on page 4000:733
    # Unable to perform important application level task from workspace like changing status, alias, global notification, proxy \\      (which are all available in the sql developer interface and imho could all be added to page 400:733 of the browser interface)
    Hope this helps,
    Geert

  • SQL Developer 3.0 and Scheduler

    Why do you only have the scheduler functionality available to your own schema, it would be better to see all scheduler jobs and be able to have total dbms_scheduler capability to all schemas.

    Scheduler follows the SQL Developer paradigm of putting user owned objects in the top level folders and other user's objects under the "Other Users" hierarchy.
    The bad new is that the Scheduler category folder does not appear under the "Other Users" hierarchy. This is a known problem and is being tracked by bug no. 10064602 THERE SHOULD BE SCHEDULER NODE IN OTHER USERS .
    So for the moment you can't edit other user Scheduler object, but you will be able to upon resolution of the above bug.
    Regards
    Rob

  • Fallo en SQL Developer , bugs in SQL Developer

    He detectado que si hacemos clic con el botón derecho sobre una tabla y seleccionamos EXPORT ==> SQL INSERT. la exportación no se lleva a cabo.
    ¿Alguien ha detectado este problema?

    Mucho mas tarde, doy confirmacion del problema en mi sistema Linux SuSE 10.0 con Oracle 10g release 2 y la ultima version de SQL Developer (Build 14.67). No tengo ningun dato en el fichero ni en el "clipboard". Pero si no selecciono todas las columnas, el fichero o el clipboard se rellenan normalement. Eso explica que algunos dicen que funciona y otros que no funciona.
    Como solucion pratica, creo una vista (view) con una columno mas ( *, 1 as nada) y no la selecciono. Solo me queda cambiar el nombre de la tabula en el texto SQL que produce la exportacion.
    A few weeks later, I certify there is a bug (en my Linux SuSE 10.0 system con Oracle 10 g release 2 and Build 14.67 of SQL Developer). I obtain an empty file or nothing in the clipboard. If I don't select all fields, the file or clipboard are full of data. This explains why some assert there is no problem and other say there is one. As a practical solution, I created a view with an extra field ( *, 1 as dummy) and didn't select it. I only have to rename the table in the exported SQL text.

  • Mining Models used in SQL Developer 3.0 and models created PL/SQL scripts

    Hi,
    Pardon my ignorance if some of my questions are very basic. I am just gaining understanding about building/using mining models.
    I installed sql developer and went thru some OBE exercises to build models ( classification models)
    While building workflows the exercise required to supply data for the pre built models ( the four models pre-created). The question is - is this exercise is about building models or using models ?
    How those pre-built models were created? Are these models are restricted in their usage. or are they generic models that they can be applied for solving similar problems?
    What type of models can be used in workflows?
    I am also seeing some smaples of pl/sql scripts used in creating some models. Is it correect to assume they are created using PL/SQL APIs ( DBMS_DATA_MINING, DBMS_DATA_MINING_TRANSFORM etc).
    What is the differrence between these two model building process ?
    Thanks

    Hi,
    The OBE exercises show you both how to build models and then to apply (Score) new data using the built models.
    A model is always built using some form of input data, so it is built specifically with that form of data in mind.
    It is not a generic model at all.
    When you apply a model you provide data in the same format as the original data.
    In the case of a Classification or Regression model, you are applying the model to generate a prediction on new data that conforms with the build data provided to the model.
    The online help provides details on all the models that are available.
    Data Miner uses the data mining pl/sql packages (package name DBMS_DATA_MINING) to create and test models.
    There are also sql data mining prediction functions as well.
    Thanks, Mark

  • SQL Developer 1.1 and XLS

    I am trying to load data from an XLS format spreadsheet.
    The new features matrix for SQL Developer 1.1 includes this as a capability but I can not find any option in the tool and I can't find information in the documentation.
    Can someone step me through this please.
    Or, can someone point me to the correct document.
    Thanks

    Yeah, as with a fair part of sqldev, it's quite hidden (as in: don't look for it in the menu):
    Right-click on the table you want to populate, Import Data, Excel.
    Hope it works for you as expected,
    K.

Maybe you are looking for