Garbage collection SQL Developer

When data grids are closed in SQL Developer, how long until the garbage collector frees that associated memory and releases it back into the pool? Are there preference(s) or configuration setting(s) that we can change to reduce the time from closing a data grid until that associated memory is released?
What I am trying to accomplish is staying within the memory constraints as dictated by the real memory constraints of the machine without having to quit and then restart SQL Developer.
Thanks in advance,
ScottK

Hi Scott,
You might want to review some of the information here:
Reduce SQLDeveloper memory footprint with JDK 1.7
In summary, the improved garbage collection algorithm can be enabled in the later jdk1.6.0 updates. I believe G1GC first becomes the default algorithm in jdk1.7.0_04, along with other JVM optimizations merged in from JRockit. Just note that Java 7 is not certified with SQL Developer at this time (search the forum for details), but it does seem to reduce memory consumption and offer smoother performance.
Regards,
Gary
SQL Developer Team

Similar Messages

SQL Developer - cannot query collections

Hi,
I have a problem with my SQL Developer that cannot query on objects with collections. I get the same error when trying to query these DB objects.
Error starting at line 1 in command:
select * from customers
Error report:
SQL Error: Fail to construct descriptor: Unable to resolve type "OE.CUST_ADDRESS_TYP"
However when I am using PL/SQL Developer I have no problem to access the objects.
I am using SQL Developer Version 2.1.1.64 with the letest jave SDK on windowns XP.
Please let mw know how to fix it.
Thanks in advance.

I already posted my problem in the SQL Developer forum but I see that this forum is more active and many here probably use the SQL Developer so they might know the solution to my problem.

SQL Developer cannot read collections

Hi,
I have a problem with my SQL Developer that cannot query on objects with collections. I get the same error when trying to query these DB objects.
Error starting at line 1 in command:
select * from customers
Error report:
SQL Error: Fail to construct descriptor: Unable to resolve type "OE.CUST_ADDRESS_TYP"
However when I am using PL/SQL Developer I have no problem to access the objects.
I am using SQL Developer Version 2.1.1.64 with the letest jave SDK on windowns XP.
Please let mw know how to fix it.
Thanks in advance.

I already posted my problem in the SQL Developer forum but I see that this forum is more active and many here probably use the SQL Developer so they might know the solution to my problem.

SQL Developer SQL History no longer working 3.2.20.09.87

Hi guys, The SQL History (F8) option has started to no longer work within my copy of OSD.
it was working at one point but has gone away.
I have confirmed that "Enable Local History" is enabled and has been set for 30 days history and 50 max revisions
I have confirmed that I still have a SqlHistory.xml file located in my user\operator\AppData\Roaming\SQL Developer\ directory with entries in it (6933 rows of data)
This started to happen after I started to play with the Garbage Collection settings to reduce the memory footprint of OSD.
I have since restored all of my backed up delivered settings, rebooted and the SQL History will not show up again.
My snippets and custom reports are working and I can still see the log detail where I used to see log and sql history options at the bottom of OSD.
I'm using Windows 7 and can provide an OSD dump if it helps.
Thanks...
Tom
Edited by: ERPDude on Mar 6, 2013 10:03 AM

Hi Tom,
Be careful about which preference settings relate to the functionality in question.
1. Tools > Preferences > Environment > Local History > Enable relates to a worksheet's History tab when you File > Open
2. Tools > Preferences > Database > Worksheet > SQL History Limit relates to View > SQL History pane.
You do not say how you backed up and restored your settings during all your experimentation, but let's assume whatever you did was valid. Whenever some UI component mysteriously disappears, one thing I always check (usually just delete) is the windowinglayout.xml in system3.2.20.09.87\o.ide.11.1.1.4.37.59.48 of my user settings.
For example, I can use the SQL History pane's tab context menu to Float it, then adjust it's size by dragging it's edges down to a grey square a few pixels wide/high. Close SQL Developer, reopen, View > SQL History. Darn! Where did it go?
Hope this helps,
Gary

SQL Developer - Memory Usage

We have SQL Developer installed on our Citrix farm and we are facing hard times right now. Unfortunately SQL Developer is consuming in some cases more than 650 MB/session. And since we have on each site more than 50 users in same time, server gets exceeded very fast. Currently server is running Windows 2003 R2 edition x86. We know that this is bad and we are planning on switching on Windows Server 2008 R2. And here comes my questions:
Will Windows Server 2008 R2 work more effectively with Java x64 and SQL Developer x64 and resolve our memory issues?
Thank you.

Hi,
I have no idea if Windows Server 2008 runs Java applications better than 2003 but, regardless of which you run, here are a couple of ideas that may be of help:
1. x32 Java/SQL Developer starts up with a smaller working set (246,000 KB) than x64 Java/SQL Developer (318,000 KB).
2. Try tweaking the garbage collection algorithm, using Garbage-First:
Re: Memory Leak or Bad Java Garbage Collector
I ran across this (old) comment from a blog on blogs.msdn.com:
Even though Windows Server 2008 R2 is exclusively a 64-bit operating system, 32-bit applications are
supported by enabling the WoW64 optional feature. If this feature is not enabled and you try to run a
32-bit application, the application will fail to execute. The WoW64 execution layer is an optional component
that is installed by default on R2 releases after beta1. You can save resources by removing the feature if
you are not going to be running 32-bit applications on your Server Core install. Regards,
Gary
SQL Developer Team

SQL Developer Memory Footprint

We're looking at replacing around 200 TOAD licenses with SQL Developer. The only technical concern is the memory footprint, as in many cases it would be run from a terminal server with dozens of people logging on. A VM Size of 150MB seems to be not unusual for SQL Developer, and that all adds up of course.
Are there any recommendations for reducing the memory footprint, or at least not letting it get much higher than 150? Features that can be turned off by default, versions of JDK, etc?

Hi,
The memory consume is quite worrying.
However change the code into VB / Delphi will lose its availability as Java's write once run anywhere. :-)
You won't be able to use this tool on Solaris, Linux, and Mac without changing the code and compiler. Thus would be less acceptable.
I wonder if limiting SQL Dev's initial class load would give impact on memory consume.
And why it seems that Java's garbage collector didn't do any collecting since the memory gets higher and higher time by time.
Or maybe the code doesn't allow the object's become collectable?
I ever get memory reach up to 500MB after doing a canceled Export Wizard for USER.
But..... memory would never come down.
Regards,
Buntoro

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 > < & 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

How to configure Oracle Sql Developer for 9i

Hi,
We are using oracle 9i for existing application, and i am trying to connect oracle 9i through SQL developer 1.5.1, i got an error message "Unsupported Oracle Database Version".
Appreciate if any body guide me in this.
regards
Husal.

After removing dictionary statistics with dbms_stats.delete_schema_stats(ownname => 'SYS') I noticed the initial SQL Developer object list query became very slow.
Removal of dictionary statistics increased the predicted Oracle optimizer (CBO) costs. Previous SYS statistics were collected perhaps without realising the consequences.
You may wish to try dbms_stats.gather_schema_stats(ownname => 'SYS', method_opt => 'FOR ALL COLUMNS SIZE AUTO', sample_size => dbms_stats.auto_sample_size).
Recent Oracle 10G versions include a gather_dictionary_stats routine.
Suggest you try this on a development DB first.

How strong ,soft ,weak ,phantom references are used in garbage collection

Hi
to all here.I have doubt that how garbage collection is deciding to cleaning up heap , and what are the roles of strong , soft , weak and phantom reference in garbage collection, i went throgh sun's java docs but i couldn't get any clear idea about those , please can anyone explain me with nice examples for which i will be really thankful.

See:
http://java.sun.com/developer/technicalArticles/ALT/RefObj/

SystemManager and Garbage Collection

Hi everyone, I have a question regarding the SystemManager and Garbage Collection. I have and application that loads in its assets via a swc created in Flash. In that swc I have different MovieClips that act as the different screens of my application each one being tied to its own custom class. For example one MovieClip is a login screen another is the main menu etc. These screens contain components, text fields and animations. The problem that I am having is when I move from one screen to the other the garbage collector is not cleaning up everything. There are still references to the MovieClips that have animations for example. So even though I remove the screen via removeChild and set the variable reference to that object to null it is not releasing the MovieClips. When I pull it up in the profiler it shows me that SystemManager is holding references to them. Also if I debug the applicaion and look inside the instance of the MovieClip I can see that the private property "listeners" has values, but I am not adding listeners. It appears that the SystemManager is adding listeners. Does anyone know how I can clear these listeners or force the SystemManager to release these items. Any ideas or help would be greatly appreciated. I am fairly new to dealing with memory management and garbage collection in Flex. I am using Flash CS4 to create the swc and Flash Builder 4 Beta with the 3.4 framework and Flash Player 10 to create the app. If you need me to clarify any of this please let me know. Again any help or ideas on where to go from here would be great!

This chain says that the focusManager is referencing UserMenu. Is there a default button or focusable objects in UserMenu and references from UserMenu to the objects in question?
BTW, the CS4 fl.managers.FocusManager and any fl.. classes are incompatible with Flex, so make sure you're not using them in your MovieClips.
Alex Harui
Flex SDK Developer
Adobe Systems Inc.
Blog: http://blogs.adobe.com/aharui

SQL Developer export forgot to check to include semicolons in DDL

Hi,
I used the SQL Developers Export-function (select tables and right click on them, then select export) to backup tables.
However, I forgot to set the 'Abschlusszeichen' (sorry for the german). That apparently means my create table statements are not finished by an ';', and they sinmply don't execute using the @script.sql method, or the sql developers import-function.
One sql-file is 2 GB in size, so I currently have no idea how to edit it and add the semicolons manually. Is there any hope to rescue the data?
I'm running sql developer 3.2.20.09, oracle Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production as well as Windows 8.1
For clarification, this is how the create table part looks:
-- Datei erstellt -Montag-September-30-2013
-- DDL for Table ZZ_BEN_0
CREATE TABLE "PIERUSCHM"."ZZ_BEN_0"
   (    "BENUTZER_ID" NVARCHAR2(30),
    "NAME" NVARCHAR2(30),
    "GUELT_VON" NVARCHAR2(30),
    "GUELT_BIS" NVARCHAR2(30),
    "IST_KORREKTUR" NVARCHAR2(30),
    "IST_HALBTAGSKRAFT" NVARCHAR2(30),
    "LADE_DAT" DATE
-- DDL for Table ZZ_BEN_1
CREATE TABLE "PIERUSCHM"."ZZ_BEN_1"
   (    "BENUTZER_ID" NVARCHAR2(30),
    "NAME" NVARCHAR2(30),
    "GUELT_VON" NVARCHAR2(30),
    "GUELT_BIS" NVARCHAR2(30),
    "IST_KORREKTUR" NVARCHAR2(30),
    "IST_HALBTAGSKRAFT" NVARCHAR2(30),
    "LADE_DAT" DATE
-- DDL for Table ZZ_BEN_10

Also i'd like to add that the file begins with table definitions but then contains the actual (and randomly generated) data as well.
You still need to have the file regenerated or you should expect to have problems with ANY method you use to try to automatically 'fix' the problem.
1. No experienced developer that I have worked with would EVER try to execute such a monolithic script because there is virtually NO chance that a 2 GB script will EVER run successfully without an error of some sort. Objects have to be created in the proper order when dependencies exist between them. For example, you can't create an index if the table hasn't been created yet. There can even be circular references that will prevent all objects from being VALID even if they are created.
2. There is virtually NO chance that ANY method you use will put terminators in EXACTLY the right place without causing a problem of some sort.
3. When there is an error the script may continue to try to executed and that usually causes further errors. It also creates garbage objects that are not valid but will keep the script from working correctly the next time since the objects will already exist.
You need to create a SET of scripts that are of manageable size so that you can control the process of executing them in the proper order.
If you don't take the time to do that, up front, you are going to wasted a tremendous amount of time when the script fails trying to cut and paste the pieces you need out of that 'master' script.
There are NO SHORTCUTS: take the time to do it right the first time.

Difference in data retrieved from sql developer and sqlplus prompt

SQL> select distinct snap_time from perfstat.stats$idx_stats;
SNAP_TIME
21-MAY-07
05-JUN-07
but using sql developer
select distinct snap_time from perfstat.stats$idx_stats;
SNAP_TIME
21-MAY-07
05-JUN-07
13-JUN-07
but can anyone explain the difference because it's the same database

SQL> select distinct snap_time from
perfstat.stats$idx_stats;
SNAP_TIME
21-MAY-07
05-JUN-07
but using sql developer
select distinct snap_time from
perfstat.stats$idx_stats;
SNAP_TIME
21-MAY-07
05-JUN-07
13-JUN-07
but can anyone explain the difference because it's
the same databaseIt looks to me during the interim between you run the query in sqlplus and SQL Developer, statspack generated a new snapshot.
Check your DBA_JOBS see if there's any auto statspack collection job.

SQL Developer vs TOAD: connection stability

I am trying to persuade a group of developers to switch from TOAD to SQL Developer. The feature set of version 1.5 is quite nice; and most of our users don't need the extra bells and whistles of TOAD. However, in side-by-side situations, it seems that TOAD gets better response times. In particular, the connection for SQL Developer sometimes seems to freeze and then come back later, while TOAD does not seem to be affected.
Our DBA thinks that the difference may be from SQL Developer using a JDBC connection while TOAD uses Oracle SQLNET. He said that switching to an LDAP server for name resolution might make the difference; but we really don't have much experience at this level of detail on the connections.
Is anyone else having a similar issue? Has anyone been able to 'equalize' the performance of the two products?
You insights are welcome.

However, in side-by-side situations, it seems that
TOAD gets better response times. In particular, the
connection for SQL Developer sometimes seems to
freeze and then come back later, while TOAD does not
seem to be affected.
Our DBA thinks that the difference may be from SQL
Developer using a JDBC connection ... I think the problem ist not SQL Developer\JDBC itself but rather the Java Runtime Environment. The behavior you describe sounds like that Garbage Collector hits you. SUN trys to make the GC better in each Java version, so I suggest you update your JRE to the newest one you can get(today: 1.6.0_06 from java.sun.com).
After doing that, install "Oracle SQL Developer for Windows, with JDK already installed" to make sure that SQL Dev. use the new one. You can check the used java version within SQL Dev. at the "About" dialog (register: version)
If you are familiar with java you should play with some gc and memory settings. Details about that you find here: http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html
Andreas

Sql Developer Data Modeler 3.0 EA1: Custom transformation script

What is the object model used by:
Tools -> Design Rules -> Transformations
From looking at the examples (and guessing) I have managed to create ID attributes on all my entities, but how do I set its sequence number or set it as the primary key?
entities = model.getEntitySet().toArray();
for (var e = 0; e<entities.length; e++)
entity = entities[e];
att = entity.createAttribute();
att.setName('ID');
- Marc de Oliveira

content of XML files:
1) class described, parent class if there is one
2)<property .../>
describes property - set and get method, data type of property, default value
3) <collection ... />
describes collection of objects belonging to class - 5 collections are defined in Table.xml - columns, indexes, table check constraints, column groups and spatial definitions
- get method - to get collection
- create item method - method of described class used to create item for that collection; so for columns collection table.createColumn() will create column in table
- other methods - add, move, remove if are defined
4)other meta data
definitions in 1) .. 4) are used by Oracle SQL Developer Data Modeler, so it'll be wrong to modify those xml files
5)<roproperty ../>
Data Modeler doesn't parse/process these definitions, we decided to not filter them out however you should not rely that much on them
6)some junk left
For each object you can set your own properties and they will be persisted (also included in compare/merge in versioning) together with other information for object - look at "template table" example in transformation scripts. Here are methods you can use:
void setProperty(String key, String value);
     String getProperty(String key);
     boolean hasProperty(String key);
     boolean hasProperty(String key, String value);
     void removeProperty(String key);
     void clearProperties();
     Iterator getPropertyNames();
Philip

SQL Developer not working

I installed SQL developers dot rel. 3.2.20.09.87 in my windows XP machine today. The downloadable zip file is available at oracle website http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html.
Version I downloaded is :
Windows 32-bit - zip file includes the JDK1.6.0_35 Download Download 209 M
On clicking sqldeveloper.exe , the small Oracle SQL Developer window pops but it goes away in few seconds.
Any pointers to resolve this issue is highly appreciated !

Hi,
To avoid losing the window before you can read what went wrong, run the sqldeveloper.exe version in directory
<SQLDev_Install_Dir>\sqldeveloper\sqldeveloper\bin\sqldeveloper.exeinstead.
If you should need to do a more in-depth investigation, the following offers some good advice on debugging:
http://www.thatjeffsmith.com/archive/2012/06/how-to-collect-debug-info-for-oracle-sql-developer/
Regards,
Gary
SQL Developer Team

Garbage collection SQL Developer

Similar Messages

Maybe you are looking for