Sharts and graphs with Dataminer in SQL DEVELOPER

How can I view the results of my worklofw diagrams in SQL Developer

Right click on the build model node and then select View Models from the menu. You will get a list of the models that were build. Select one of these and you can then see the details of the model. For example if you select the Decision Tree model, you will see the decision tree etc

Similar Messages

  • Problems with printing from SQL Developer Data Modeler 2.0

    Hi,
    I am not able to print my Relational Model (SubView) from Data Modeler 2.0 Build 584. Only an empty page comes out. If I don't reduce the Print Scale (usually to 10-30%) I get something but then it is lots of pages. I have tried A4 and A3 format. Printing to JPEG or PDF seems to be ok.
    I have relational data model with 25 tables in my SubView.
    Is there any restriction on Print Scale or number of objects in the diagram?
    Do I have to install SQL Developer as well? I have just Data Modeler insalled.
    Regards,
    Alex

    Hi Alex,
    There is newer version of Data Modeler (3.0 EA2) and it is free
    You can download it from here
    http://www.oracle.com/technetwork/developer-tools/datamodeler/ea2-downloads-185792.html
    Regards
    Edited by: Dimitar Slavov on Dec 9, 2010 2:15 AM

  • Extension.xml and catching compile event in sql developer

    Hi,
    recently I've been trying to make a few plug-in/extensions for sql developer. One allows you to search through entire schema to find and procedures or functions that utilize any given procedure or function, this one works fine. The second one and the one that is giving me trouble is an extension that allows you to see if any items (procedures, functions,...) are broken, the goal with this one is for it to do this task automatically when a procedure or function is compiled to show if the compilation of the function or procedure broke anything else. I have this one working as a button in the toolbar and choice in the main menu, but I can not for the life of me figure out how to hook it on to a compile or run event. Please help!!!!
    here is my extension file so far:
    <extension id="brokenSearch" version="1.0" esdk-version="1.0" rsbundle-class="infinTech.brokensearch.Res"
    xmlns="http://jcp.org/jsr/198/extension-manifest">
    <name>Broken Search</name>
    <dependencies>
    <import>oracle.jdeveloper.db.connection</import>
    <import>oracle.ide</import>
    </dependencies>
    <trigger-hooks xmlns="http://xmlns.oracle.com/ide/extension">
    <!-- TODO Declare triggering functionality provided by extension: infinTech.schemasearch -->
    <triggers>
    </triggers>
    </trigger-hooks>
    <hooks>
    <!-- TODO Declare functionality provided by the yourcompany.showmepassword extension. -->
    <jdeveloper-hook xmlns="http://xmlns.oracle.com/jdeveloper/1013/extension">
    <actions>
    <action id="infinTech.brokenitems.BrokenItems">
    <properties>
    <property name="Name">Broken Items</property>
    <property name="SmallIcon">${OracleIcons.PLACEHOLDER}</property>
    <property name="LongDescription">Broken Items</property>
    </properties>
    <controller-class>infinTech.brokensearch.ShowMeDatabasePasswordController</controller-class>
    <command-class>infinTech.brokensearch.ShowMeDatabasePasswordCommand</command-class>
    </action>
    </actions>
         <context-menu-listeners>
    <site idref="navigator">
    <listener-class>infinTech.brokensearch.MenuContextMenuListener</listener-class>
    </site>
    <site idref="editor">
    <listener-class>infinTech.brokensearch.MenuContextMenuListener</listener-class>
    </site>
    <site idref="explorer">
    <listener-class>infinTech.brokensearch.MenuContextMenuListener</listener-class>
    </site>
    </context-menu-listeners>
    </jdeveloper-hook>
    <!-- Hook into menus and toolbars -->
    <menu-hook>
    <menus>
    <!--
    Add the action in its own separator group at the top of the File
    menu.
    -->
    <menubar id="javax.ide.view.MAIN_WINDOW_MENUBAR_ID">
    <menu id="javax.ide.VIEW_MENU_ID">
    <section id="schema.search"
    before="javax.ide.NEW_SECTION_ID">
    <item action-ref="infinTech.brokenitems.BrokenItems"/>
    </section>
    </menu>
    </menubar>
    </menus>
    <toolbars>
    <toolbar id="javax.ide.view.MAIN_WINDOW_TOOLBAR_ID">
    <section id="SCHEMA_SEARCH_SEACTION" weight="2.0">
    <item action-ref="infinTech.brokenitems.BrokenItems"/>
    </section>
    </toolbar>
    </toolbars>
    </menu-hook>
    <feature-hook>
    <description>Simple utility that finds any/all broken items.</description>
    </feature-hook>
    </hooks>
    </extension>

    Hi,
    That's not an XML-specific issue, please see the dedicated forum for SQL Developer : {forum:id=260}

  • Schema Binding with VSS in SQL Developer

    Hi guys is it possible to bind a Sql Developer or TOAD with Visual Source Safe or i can change database object in toad or sql developer and check in into VSS?
    Thanks
    Purvik

    TOAD can do version control with any software that uses Microsoft's Source Code Control (SCC) API, which includes VSS. Look at the help pages for more info.
    While SQL Developer only supports Subversion and CVS directly, I've used its External Tools capability to add ClearCase check out, check in, undo check out, and add capabilities. If you can do basic version control operations from the command line with Visual SourceSafe, you ought to be able to do the same thing. Just look up the syntax for the command line tools, and build your commands by selecting the Tools menu, select External Tools, and add a new tool. This is very much like creating a new desktop shortcut in Windows.

  • Issue in connection with database using SQL Developer.

    Hi,
    I am facing a problem in connecting to a remote oracle database, below are the configuration setting which i am trying to use in sql developer to make the connection
    TNS Configuration Details (SUDHIR)
    SUDHIR=
    (DESCRIPTION=
    (ADDRESS=
    (PROTOCOL=TCP)
    (HOST=52.12.xxx.xxx)
    (PORT=1526)
    (CONNECT_DATA=
    (SERVICE_NAME=sudhir)
    User : system
    Password : xxxxxxxxxxx
    Database : sudhir
    Connect as : Normal
    I got the above credential details from Onsite team I need to connect this in my local sytem SQL Developer I am proving the connection as below
    Hostname : 52.12.xxx.xxx
    Port : 1526
    Service Name : sudhir
    Username : xxxxxxxxxxxxxx
    password : xxxxxxxxxxxxx
    I get following error when say test connection in sql developer.
    "The Network Adapter could not establish the connection."
    Please suggest me using the above details how to make the connection success. Please let me know.
    Thanks
    Sudhir
    Edited by: BluShadow on 30-Mar-2012 11:56
    data anonymised by moderator

    (o_0)
    Hopefully for you, the machine is not reachable from internet !
    Your giving online everything needed to log in as system ! that is quite dangerous. I guess the "Onsite team" would be pretty mad discovering that.
    You should edit your previous post before too much people get to it.
    Regarding your problem, I guess you can't get to the machine itself (maybe in a different network).
    Can you try to ping it from your computer ?ping 51.17.130.121
    This is a made-up IP, you'll have to replace with yours

  • ORA-06550 and PLS-00201 in PL/SQL Developer

    Hi all ,
    I am facing the following error when i try to view the DDL of a table using pl/sql developer.
    ( right click on table and then DBMS_Metadata -> DDL)
    ORA-06550: line 7, column 5:
    PLS-00201: identifier 'SYS.DBMS_LOB' must be declared
    ORA-06550: line 7, column 5:
    PL/SQL: Statement ignored
    ORA-06550: line 12, column 3:
    PLS-00201: identifier 'SYS.DBMS_LOB' must be declared
    ORA-06550: line 12, column 3:
    PL/SQL: Statement ignored
    ORA-06550: line 13, column 3:
    PLS-00201: identifier 'SYS.DBMS_LOB' must be declared
    ORA-06550: line 13, column 3:
    PL/SQL: Statement ignoredPlease suggest me what to do ?
    regards
    Kkukreja

    Hi VT ,
    When i execute this .. I get this output :
    Argument Name                  Type                    In/Out Default?
    LOB_LOC                        BLOB                    IN/OUT
    NEWLEN                         NUMBER(38)              IN
    PROCEDURE TRIM
    Argument Name                  Type                    In/Out Default?
    LOB_LOC                        CLOB                    IN/OUT
    NEWLEN                         NUMBER(38)              IN
    PROCEDURE WRITE
    Argument Name                  Type                    In/Out Default?
    LOB_LOC                        BLOB                    IN/OUT
    AMOUNT                         NUMBER(38)              IN
    OFFSET                         NUMBER(38)              IN
    BUFFER                         RAW                     IN
    PROCEDURE WRITE
    Argument Name                  Type                    In/Out Default?
    LOB_LOC                        CLOB                    IN/OUT
    AMOUNT                         NUMBER(38)              IN
    OFFSET                         NUMBER(38)              IN
    BUFFER                         VARCHAR2                IN
    PROCEDURE WRITEAPPEND
    Argument Name                  Type                    In/Out Default?
    LOB_LOC                        BLOB                    IN/OUT
    AMOUNT                         NUMBER(38)              IN
    BUFFER                         RAW                     IN
    PROCEDURE WRITEAPPEND
    Argument Name                  Type                    In/Out Default?
    LOB_LOC                        CLOB                    IN/OUT
    AMOUNT                         NUMBER(38)              IN
    BUFFER                         VARCHAR2                IN.
    That means this exists... Tomorrow the database will be undegoing backup and so will shutdown and startup..
    So probably on monday I can check if i can login.. becuase I tried to view the same details using TOAD and i faced no errors as such...
    So lets wait till monday... if no other solution..
    Thanks
    Kkukreja

  • How to pass and work with a PL/SQL or Temp table in a Procedure?

    My problem is that I have a query that involves about 10 tables or so, but everything starts from one base table. I am trying to split the base table so that the query actually finishes.
    Problem Query:
    with base_table as
    select * from table_a
    , t1 as
      select * from table_b
    -- There are some manipulation in the SQL, but not listing it here.
    , t2 as
      select * from table_c INNER JOIN t1 on t1.id = table_c.id
    ) What I want to do is limit base table and thus create a procedure such that it evalutes a temporary table and the temporary table will be limited by 1000 rows or so.
    Thanks for your help.

    Currently I am using:
    DECLARE
       l_start                       NUMBER;
       l_increment                   NUMBER;
       l_max                         NUMBER;
    BEGIN
       l_start := 1;
       l_increment := 100;
       SELECT COUNT(*) AS the_count
         INTO l_max
         FROM table_a;
       LOOP
       INSERT INTO new_table
         WITH base_table AS
         (SELECT p.*
            FROM (SELECT DENSE_RANK () OVER (ORDER BY alpha_id) rnum, a.*
                    FROM table_a a) p
           WHERE rnum BETWEEN l_start AND l_start + l_increment - 1)
       , t1 AS
         (SELECT *
            FROM table_b
    -- There are some manipulation in the SQL, but not listing it here.
       , t2 AS
         (SELECT *
            FROM table_c INNER JOIN t1 ON t1.ID = table_c.ID
    SELECT *
      FROM t2, temp_base;
    COMMIT;
          l_start := l_start + l_increment;
          EXIT WHEN l_start > l_max;
       END LOOP;Is it better to create a Temporary table or pass the data as a cursor:
    SELECT DENSE_RANK () OVER (ORDER BY alpha_id) rnum, a.*
    FROM table_a a
    Thanks.

  • Importing data into tables with grant access (sql developer 3.2)

    Hello,
    I want to import data into a table PAY_BALANCE_BATCH_LINES which is an interface table. I'm logged in to a schema (APPS) and this table belongs to the HR schema. However, if you look at the grants, the APPS schema has all access to this particular table. In TOAD, this used to work great.
    But in sqldeveloper, when I filter the tables dropdown, I am not able to find this table. Since this is my primary way of uploading data I'm not sure how else I can get access to upload data into this table. I don't know the password for the HR schema by the way.
    Is there a way out?
    Many Thanks

    Scroll down the tree to the 'Other Users' node, expand it, and then drill down into HR > Tables. Then do your import.
    For an alternative browser, right-click on your connection in the tree and open a Schema Browser.

  • SQL Developer 3.0 against Oracle 10g

    Hi,
    I have used SQL Developer in previous employments and prefer use it now (ie SQL Developer 3.0), but unsure if the mix will work.
    I am on a Windows Server 2003 Std 64bit Edition and with Service Pack 2. and have Oracle client 10g home with basic tools against an Oracle 10G database server.
    So before installing, I would like some tips on the best mix for Client and Server with respect to SQL Developer.
    I also understnad that it will require Java JDK install prior to SQL Developer. Will this require me to take into consideration current Java installs under
    "C:\Program Files (x86)\Java\jre6\bin" and dated back to 30 Sept 2010
    Many thanks before hand
    Chris

    You can can download SQL Developer with a JDK included. This is 32-bit, but will run fine in a 64-bit OS.
    Alternatively you can download the 64-bit version of SQL Developer. This requires you to have a 64-bit JDK.
    You can install multiple JDKs without interfering with each other. Your existing JRE installation won't work anyway as you need a JDK.
    If you download a JDK, don't get Java 7 as SQL Developer doesn't work properly with that. Get the latest version of Java 6.
    Edited by: Jim Smith on Dec 20, 2011 4:31 PM

  • CRYSTAL REPORT GRAPH WITH DATE AND TIME

    Post Author: Dino Dentone
    CA Forum: Charts and Graphs
    Dear forum,
    I am developing a Visual Studio .net 2005 Windows Form,i have a sql table with 2 field:1) DATA (date and time)2) Temperatura (numeric)I have to make a line graph with numeric data axes.I have insert two parameters' to customize the filtering, so i can have a graph of the temperature between to date and time.If i choose two date's and time (parameters) like 20/04/2008 00:00:00 trought 20/05/2008 00:00:00 i have no problemBut if a choose a range minor of 1 day (some hours like from 15/05/2008 00:00:00 trought 15/05/2008 08:00:00) i have no graph.It sound like it don't use the time values?Thank's for the Help.

    There is some debugging info on the website. I've had problems getting the text to work. It was generally that I installed either the wrong 'version' of ImageMagick (the recommended one works for me--I'm running Vista x64 and one time installed the x64 version and it didn't work). I also installed Ghostscript to get the font list to work correctly. At one time I installed the x64 version of Ghostscript and it didn't work with the plug-in, either.
    I installed two items:
    ImageMagick: ImageMagick-6.4.9-3-Q16-windows-dll.exe
    Ghostscript: gs863w32.exe
    I don't know if it is necessary but I also added the fonts from
    ghostscript-fonts-std-8.11.tar.gz to the c:\Program Files (x86)\gs\fonts directory. Some, none, perhaps all, may already be installed just by installing ghostscript--it has been so long that I don't remember exactly. I do know that the contents of the gs fonts directory contains all the files in the .gz, I just don't remember if I put them there separately or as part of the gs install :)
    You need to make sure the font size is large enough. I usually use about 2-4% of height and export a single photo to make sure I see the text correctly.
    Tim does respond to email when he can so if you can't get it to work you can always drop him a line.

  • 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

  • Statement terminator problems when exporting data with SQL Developer 3.2

    I've ran across what appears to be a bug with SQL Developer 3.2.20.09. If someone can let me know if this is indeed a bug, or just something I need to configure differently, please let me know.
    The problem is related to exporting a database as a SQL script, and terminator characters at the end of "create" statements, especially when columns have comments, and problems that occur when using SQLPlus to run the export script to create the tables. With the old SQL Developer 1.5.4, with the "Terminator" and "Pretty Print" options checked, statements like the following are generated:
    -- DDL for Type NUM_ARRAY
    CREATE OR REPLACE TYPE "NUM_ARRAY"
    IS TABLE OF NUMBER(20)
    -- DDL for Sequence MYTABLE_SEQ
    CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
    -- DDL for Table MYTABLE
    CREATE TABLE "MYTABLE"
    (     "MYTABLE_ID" NUMBER,
         "COL2" NUMBER,
         "COL3" NUMBER
    -- DDL for Table ANOTHERTABLE
    CREATE TABLE "ANOTHERTABLE"
    (     "ANOTHERTABLE_ID" NUMBER,
         "COL2" VARCHAR2(1024),
         "COL3" VARCHAR2(1024)
    COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.';
    When I then run the script using SQLPlus, everything works fine. However, with SQL Developer 3.2.20.09, with the same options enabled, the same statements are generated like this:
    -- DDL for Type NUM_ARRAY
    CREATE OR REPLACE TYPE "NUM_ARRAY"
    IS TABLE OF NUMBER(20)
    -- DDL for Sequence MYTABLE_SEQ
    CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
    -- DDL for Table MYTABLE
    CREATE TABLE "MYTABLE"
    (     "MYTABLE_ID" NUMBER,
         "COL2" NUMBER,
         "COL3" NUMBER
    -- DDL for Table ANOTHERTABLE
    CREATE TABLE "ANOTHERTABLE"
    (     "ANOTHERTABLE_ID" NUMBER,
         "COL2" VARCHAR2(1024),
         "COL3" VARCHAR2(1024)
    COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.';
    Notice all of the extra slashes in there. If a slash is not used as a statement terminator, SQLPlus treats slashes as a command to repeat the last SQL statement, which causes many errors about tables or sequences already existing. So, I tried removing the "Terminator" flag from the export options. This lead to statements that looked a bit more promising:
    -- DDL for Type NUM_ARRAY
    CREATE OR REPLACE TYPE "NUM_ARRAY"
    IS TABLE OF NUMBER(20)
    -- DDL for Sequence MYTABLE_SEQ
    CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE
    -- DDL for Table MYTABLE
    CREATE TABLE "MYTABLE"
    (     "MYTABLE_ID" NUMBER,
         "COL2" NUMBER,
         "COL3" NUMBER
    -- DDL for Table ANOTHERTABLE
    CREATE TABLE "ANOTHERTABLE"
    (     "ANOTHERTABLE_ID" NUMBER,
         "COL2" VARCHAR2(1024),
         "COL3" VARCHAR2(1024)
    COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.'
    The big problem, though, is in the statement for the table with a comment. Notice that there are two statements, but there is not a semicolon after either of them. This unfortunately causes the "COMMENT" statement to be appended to the "CREATE TABLE" statement before being executed, which causes the table to not be created (which causes even more errors later on when the script attempts to populate the table with data).
    So, it would appear that this is a bug, but I'm not sure. Is there a way I can configure the export options to make SQL Developer export these statements like it used to in older versions?
    Thanks,
    -Bill

    >
    So, it would appear that this is a bug, but I'm not sure.
    >
    That would be a bug. Thanks for reporting it and providing the detailed example.
    >
    Is there a way I can configure the export options to make SQL Developer export these statements like it used to in older versions?
    >
    No.
    Leave the thread open. One of the developers for sql developer should be monitoring the forum and can provide more information.

  • Plsql_optimize_level = 3 and native compilation in SQL Developer?

    SQL Developer: Version 3.1.06 (Build MAIN-06.82)
    Oracle: 11gR2
    OS: Ubuntu 10.10
    Whenever I compile a PL/SQL unit in SQL Developer (using 'Compile' button) it is compiled with the following settings:
    PLSQL_OPTIMIZE_LEVEL = 2
    PLSQL_CODE_TYPE = 'INTERPRETED'
    However, if I issue the following commands in an SQL Worksheet:
    ALTER SESSION SET plsql_optimize_level = 3;
    ALTER PACKAGE PACKAGE_NAME COMPILE PLSQL_CODE_TYPE = NATIVE;
    the query SELECT PLSQL_OPTIMIZE_LEVEL, PLSQL_CODE_TYPE FROM ALL_PLSQL_OBJECT_SETTINGS WHERE NAME = 'PACKAGE_NAME'; resullts in
    PLSQL_OPTIMIZE_LEVEL     PLSQL_CODE_TYPE
    3     NATIVE
    3     NATIVE
    Is it possible to make SQL Developer to use these settings by default?
    P.S. It seems that Tools > Preferences > Database > PL/SQL Compiler menu section is missing the options I need (Optimization level drop-down menu have numbers 0-2, but not 3). Are there any plans to support these features in the future releases?
    Edited by: Ravshan Abbasov on Feb 6, 2012 6:28 AM

    Hi Ravshan,
    I thought a workaround would be to create a sql script like the following:
    alter session set plsql_code_type=native;
    alter session set plsql_optimize_level=3;  then point to it in the setting for Tools|Preferences|Database|Filename for connection startup script. That doesn't work however, as the other preference setting for plsql_optimize_level overrides the session value of 3 during compilation from the UI.
    According to Oracle documentation, level 3 was added for Oracle 11g. Prior to that, the same effect could be achieved by level 2 in conjunction with the INLINE pragma in the PL/SQL code.
    You might want to make a feature request for this on the SQL Developer Exchange so the community can vote and comment.
    Regards,
    Gary
    SQL Developer Team
    Edited by: Gary Graham on Feb 6, 2012 2:32 PM
    And, of course, Compile for Debug does not work with the 'native' setting.

  • SQL developer not installed with the client software

    Hi All,
    OS: Windows
    Clinet: 11g 64 bit
    I have installed oracle client for windows 64 bit, as we know with client installation the sql developer also comes with. But in my case, I am able to find every other component but sql developer.
    I am thninking of downloading the same from Oracle site, is there a alternate way for the same?
    Regards,
    Sphinx

    What, exactly, did you install?
    Did you install the Instant Client?  Or did you do a full client install?  If you did a full client install, which option did you pick during the installation process-- Administrator, Runtime, or Custom?  If you did a full client install that didn't include SQL Developer, you can always restart the Oracle Universal Installer, do a custom install, and choose to install just SQL Developer.
    That being said, my bias would generally be to download the most recent version of SQL Developer from OTN separately.  SQL Developer gets released much more frequently than the Oracle client so the version on OTN is generally multiple revisions more recent than the version that was shipped with the client.  If you're going to be developing code, you may as well leverage all the new features of SQL Developer rather than settling for whatever version was current when 11.2 was released.
    Justin

  • SQL Developer 3.2 crashes with java error when using OCI/Thick Driver

    I just installed SQL Developer 3.2 on my linux desktop. SQL Developer crashes with a java error when I select a database from the object tree.
    When I check Use OCI/Thick driver the application will crash when I navigate to the tree and open a database.
    The app does not crash then I have Use OCI/Thick driver unchecked.
    Here are some details of my environment:
    Desktop OS: Fedora 17 Linux
    $ uname -a
    Linux 3.5.1-1.fc17.x86_64 #1 SMP Thu Aug 9 17:50:43 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
    Java:
    $ java -version
    java version "1.6.0_34"
    Java(TM) SE Runtime Environment (build 1.6.0_34-b04)
    Java HotSpot(TM) 64-Bit Server VM (build 20.9-b04, mixed mode)
    Oracle instant client:
    $ sqlplus -V
    SQL*Plus: Release 11.2.0.3.0 Production
    Here are the error messages:
    $ sqldeveloper
    Oracle SQL Developer
    Copyright (c) 1997, 2011, Oracle and/or its affiliates. All rights reserved.
    # A fatal error has been detected by the Java Runtime Environment:
    # SIGSEGV (0xb) at pc=0x00007f6de7157664, pid=3049, tid=140109371119360
    # JRE version: 6.0_34-b04
    # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.9-b04 mixed mode linux-amd64 compressed oops)
    # Problematic frame:
    # V [libjvm.so+0x516664] unsigned+0xd4
    # An error report file with more information is saved as:
    # /tmp/hs_err_pid3049.log
    # If you would like to submit a bug report, please visit:
    # http://java.sun.com/webapps/bugreport/crash.jsp
    /opt/sqldeveloper/sqldeveloper/bin/../../ide/bin/launcher.sh: line 544: 3049 Aborted (core dumped) ${JAVA} "${APP_VM_OPTS[@]}" ${APP_ENV_VARS} -classpath ${APP_CLASSPATH} ${APP_MAIN_CLASS} "${APP_APP_OPTS[@]}"

    I also had the problem of SQL Developer crashing when using OCI/Thick driver but I've managed to solve it. My configuration is:
    - Windows 64-bit
    - Java 64-bit (1.6.0.34)
    - SQL Developer 3.2.09 64-bit
    - OCI Instant client 11.2.0.3 64-bit (without installation).
    The thing that solved the problem was copying two files, ojdbc5.jar and ojdbc6.jar, from Instant client installation folder to JAVA_HOME/lib/ext folder+.
    After that, I haven't had a single crash or error message.
    The same trick that solved the problem on 64-bit installation also solved the problem on another windows computer with 32-bit SQL Developer installation.

Maybe you are looking for