Performance issues for sql developer

1. Does leaving DB connection open from a SQLNavigator has any impact on the DB resources and performance?

That depends.
If you run a query or browse a table with parallel setup and leave a grid open - you could leave many processes sitting idle on the server waiting for you to fetch the records down.
But in general, 'no.'
Also, what do you mean by a 'SQLNavigator' - you mean SQL Developer, yes?

Similar Messages

Password issue for SQL Developer

Hi All,
I have downloaded the SQL developer and I am facing the issue with the username and Password while creating the new connection. Please let me know what is the username and
password.
Thanks in advance.
Best regards,
Pavan

Please post your question in the appropriate forum.
Database - General
General Database Discussions
SQL Developer
SQL Developer

Serious UI issues in SQL Developer 4.0 for Mac

I've encountered some serious UI issues in SQL Developer 4.0 for Mac (4.0.0.13) that impact it up to the point where it becomes unusable.
If the database and tables are expanded in the "Connections" view, sometimes a node in the tree seems to become sticky. Whenever you scroll the up or down, it will immediately scroll back to make the old selection visible again. If you want to work with an item that's outside the current view (e.g. to collapse the "Tables" node), you can no longer use it. SQL Developer needs to be restarted.
If the context menu is opened (ctrl click), it appears in the wrong place. It's too far to the right and bottom. If you then move the mouse pointer towards the menu, a rectangle appears and follows the mouse pointer as if you had initiated a drag and drop operation.
If the "Data" tab of a table is selected and if a cell is clicked to edit the cell value, the text cursor is drawn in the wrong position. It can be off by more than one character and it is often drawn in the middle of a character instead of between two characters. It's hardly possible to edit the cell value as you cannot tell for sure where insertions and deletions will happen. You basically need to copy the value into a separate editor, edit it there and copy it back.
The scrolling in the "Data" tab of a table is a pain. For no obvious reason, it first scrolls downwards a few rows and then jumps to the top (at least using a Magic Mouse). If all rows have been loaded, this problem seems to disappear. But generally, the scrolling distance is far too short. With a long finger swipe, one would expect to scroll the contents by several pages. However, it only scrolls about half a page. For shorter swipes, it's similar. It sometimes only scrolls by a few pixels.
Am I the only one to experience these severe problems? Or is the Mac version not as mature as the Windows version yet?

In terms of diagnosis, perhaps not -- probably very time-consuming to debug. I did find some unpublished bugs against dual monitor use ...
Bug 13727841 - FORUM: 64BIT WIN7 SOME DIALOGS SHOW ON DISPLAY 1 WHEN SQLDEV ON DISPLAY 2
Bug 18504928 - NEW CONSTRAINT UI MENU IN TABLE DIALOG AT WRONG LOCATION ON DUAL MONITOR
The first turned out to be an issue in the 64-bit Java AWT libraries, not the 32-bit libraries, and specifically for Windows 7 as opposed to, say XP, but this was all quite a bit in the past and was fixed for 4.0. The second one (on 64-bit Linux), however, just came in yesterday, so you can wait to see if a fix for that also covers your situation or, if you are able, pursue it directly with Oracle Support.

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

GeoRaptor 3.2.1 Released for SQL Developer 3.x

Spatialites!
After 6 months of development and testing, GeoRaptor 3.2.1 has been released for SQL Developer 3.x (tested on 3.0, 3.1 and 3.2). This release no longer supports SQL Developer 1.x or 2.x releases due to internal changes to the SQL Developer APIs.
GeoRaptor can be downloaded from the GeoRaptor project's sourceforge page: http://sourceforge.net/projects/georaptor and installed via Help>Check for Updates>Install from Local File. Installation via SQL Developer's update mechanism should be available soon.
The release notes for this release are:
* Fixed issues with validate geometry functionality in particular the update dialog box.
* Revamped "About GeoRaptor" form. Includes clickable URLs, links to mailing lists, version number listing, thanks to testers etc.
* Placed "About GeoRaptor" icon on GeoRaptor's map toolbar.
* SQL Developer NLS settings accessed: improvements in the display and entry and numeric data.
-- Tolerances in Spatial Layer properties will display with the NLS decimal separator eg 0,05.
     Some parts of GeoRaptor such as Validation that show and accept numbers have not been changed from when someone else modified the code.
     If you double click on the left MBR/right MBR icon in the map at the bottom, the current centre position will display according to the NLS settings.
     Editing the value to jump the map to that point works even with grouping separators and decimal separators being commas!
* Spatial Layer Draw has been modified to use NLS based decimal formatting.
* New geometry marking/labelling options have been added. In particular you can now label the vertices of a linestring/polygon with the following additional elements:
-- Cumulative length
-- Measure (M)
-- Z value
-- Labelling of vertices with <id>{X,Y} now also honours 3/4D geometries. If geometry has XYY then it will be labelled as {X,Y,Z} etc.
* You can also label each vector/segment of a linestring/polygon with:
-- Length
-- Cumulative Length
-- Bearing (approximate for geodetic/geographic data)
-- Distance (approximate for geodetic/geographic data)
-- Bearing and Distance (approximate for geodetic/geographic data)
* The font properties of the mark text can be changed independently of the feature label. This includes the offset and label position (CC, LL, UR etc).
* New feature labelling options have been provided:
-- First/middle/last vertex,
-- Any supplied sdo_point within a line/polygon's sdo_geometry object, or
-- Calculated by GeoRaptor on the client side using Java Topology Suite.
* Result sets now have the ability to:
-- Copy to clipboard all geometries across many rows and columns.
-- Display one or more (selected) geometries in a popup image window. This functionality is also available in the result set generated by an Identify command.
* New GeoRaptor Preferences:
-- Width and height in pixels of the new popup image window (displaying one or more geometry objects) can be set;
-- Colours of orphan, missing and correct metadata entries for Metadata Manager;
-- Prefixing with MDSYS for all currently supported spatial objects - sdo_geometry, sdo_point, sdo_elem_info, sdo_ordinates, sdo_dim_info - has been made an option.
-- There is now a new property called "Show Number Grouping Separator" in Tools>GeoRaptor>Visualisation.
     If it is ticked a number will be formatted with the thousands separator in Tools>Database>NLS eg 10000.000 will display as 10,000.000.
* Sdo_Geometry display of all spaces in text between elements of the sdo_geometry array have been removed.
   This was done mainly to compact the sdo_geometry strings so that they are as small as possible when displaying or copying to clipboard.
* Help pages added to the following dialogs with more to follow:
-- Metadata Manager,
-- Shapefile Importer and
-- Layer Properties dialogs.
* GeoRaptor menu entries renamed. New "Manage All Metadata" entry added to View>GeoRaptor menu.
* Spatial Index creation dialog now supports additional index parameters and parallel build settings.
* Metadata Manager overhauled:
a. Shows:
     1. Metadata entries which have no underlying oracle object (orphan)
     2. Metadata entries for existing underlying objects (existing case)
     3. Database objects with sdo_geometry for which no metadata entry exists (new)
b. All orphan/existing/missing colours for (a) can be set via Preferences>GeoRaptor>Visualisation
c. All actions for main (bottom) metadata table are in a single right mouse click menu.
     Some entries will only appear if a single row is selection (metadata copy), others (delete and copy to clipboard) will appear for one or more.
d. Can now switch between open connections to modify metadata of other objects in schemas other than the starting object.
e. Buttons revamped.
* Tab/Shapefile export:
a. Export now supports NULL valued columns. Can be exported as an empty string (if DBase override in GeoRaptor Preferences is ticked) or
     as a predefined value eg NULL date => 1900-01-01 (set in new GeoRatptor Import/Export Preferences).
b. Some work attempted on export of NLS strings (still not corrected).
c. Objects with no rows now correctly processed.
* Shapefile Import
-- Bug relating to Linux file names corrected.
* Fixed issue (identified by John O'Toole) with spatial index underlying a view not being used in map display.
* Reinstated sdo_nn as the principal method for Identify (requested by John O'Toole).
* Fixed problem with handling single click zoom in and out in GeoRaptor map etc.
* Fixed problem with rendering lines from database item (identified by Vladimir Pek).The new "About GeoRaptor" should be read by all people installing GeoRaptor.
Please, please consider registering your email address with our private email list so that we can get a feel for the sorts of people downloading and installing GeoRaptor.
Please consider helping us with documentation or the internationalisation via translating properties files from English to your native language.
GeoRaptor is written and maintained by people who use SQL Developer and Spatial every day but we don't pretend we know everything that users want: please let us know via our feature request page at SourceForge.
We don't get paid for what we do so are always looking for additional help.
Here are some of the requests we have had for improvements:
1. MySQL access
2. WMS access;
3. Ability to import shapefile data into an existing table;
4. Ability to processing multiple shapefiles into separate tables (current version can import one or more into a single target table);
5. Ability to export/import layer definitions to give to others;
6. Support for non-English character sets for varchar exports to shapefiles.Some are relatively simply, some require a lot of engineering work. For the latter, we are considering alternative funding methods to the currently completely free development approach.
Thanks to the following for their invaluable assistance:
Holger Labe, Germany
John O'Toole, Ireland
Vladimir Pek, Czech Republic
Pieter Minnaar, Holland
Olaf Iseeger, Germany
Sandro Costa, Brazil;
Marco Giana, Australia.regards
Simon Greener
Principal GeoRaptor Developer
Edited by: Simon Greener on Sep 10, 2012 2:43 PM

Simon,
I will admit, I almost never use SQL Developer. I have been a long time Toad user, but for this tool, I fumbled around a bit and got everything up and running quickly.
That said, I tried the new GeoRaptor tool using this tutorial (which is I think is close enough to get the jist). http://sourceforge.net/apps/mediawiki/georaptor/index.php?title=A_Gentle_Introduction:_Create_Table,_Metadata_Registration,_Indexing_and_Mapping
As I stumble around it, I'll try and leave some feedback, and probably ask some rather stupid questions.
Thanks for the effort,
Bryan

Java extension for SQL Developer 2.1 (SqlEditor)

Hello,
we are developing a java extension for SQL Developer. It was working fine in version 1.5.5 but it seems that some of the java classes were changed in version 2.1 so it does not any more. In the SQL editor, we want to have a context menu action that gets the selected SQL statement and calls a database function with it as an argument. Our code looks like
@RegisteredByExtension("our.developer.extension")
public final class OurCommand extends Command {
public int doit() {
SqlEditor sqlEditor = (SqlEditor)getContext().getView();
String query = sqlEditor.getView().getSqlStatement();
sqlEditor.executeSql(query, "");
//or
//sqlEditor.getView().scriptRunner(query);
Unforunately, in SQL Developer 2.1 the class oracle.dbtools.sqlworksheet.sqlview.SqlEditor does not exist. Does anybody know how to write this example for version 2.1? Is there an API documentation (alas, [http://wiki.oracle.com/page/SDK+2.0] is an empty article)?
BTW, does anybody know how to open the dialog for connecting to a database when sqlEditor.getConnection() is null?

I got it to work using a BASIC call instead of my normal TNS call.
We use MS SMS to package the Oracle client and SQL Developer and push it out to users so we don't have people visiting desktops. Also, we use OID to store the entries instead of a tnsnames file so that we don't have to maintain a TNSNAMES file.
I am testing 2.1 as we would eventually upgrade when it goes GA.
2.1 seems to be built on Oracle 11g. Issue will be that since 99% of our databases are 10gr2 as well as 100% of our client population will be be forced to upgrade the Oracle client to use 2.1 as we do today without lots of changes for the end user?
We don't broadcast the information the average user requires for a BASIC connection so that is out for non technical users..
We have SQL Developer 1.5.5 right now and this is not and issue.
Hopefully, this will be resolved during EAI for 2.1.

No oci jdbc11 in java.librar.path for SQL Developer 2.1 EAI

Just migrated my connections from 1.5.5 and tested.
I have the one with the JDK built-in.
I browsed to it and it comes up.
However when I access a connection I get the below:
no oci jdbc11 in java.librar.path for SQL Developer 2.1 EAI

I got it to work using a BASIC call instead of my normal TNS call.
We use MS SMS to package the Oracle client and SQL Developer and push it out to users so we don't have people visiting desktops. Also, we use OID to store the entries instead of a tnsnames file so that we don't have to maintain a TNSNAMES file.
I am testing 2.1 as we would eventually upgrade when it goes GA.
2.1 seems to be built on Oracle 11g. Issue will be that since 99% of our databases are 10gr2 as well as 100% of our client population will be be forced to upgrade the Oracle client to use 2.1 as we do today without lots of changes for the end user?
We don't broadcast the information the average user requires for a BASIC connection so that is out for non technical users..
We have SQL Developer 1.5.5 right now and this is not and issue.
Hopefully, this will be resolved during EAI for 2.1.

Performance Issue for BI system

Hello,
We are facing performance issues for BI System. Its a preproductive system and its performance is degrading badly everyday. I was checking system came to know program buffer hit ratio is increaasing everyday due to high Swaps. So asked to change the parameter abap/buffersize which was 300Mb to 500Mb. But still no major improvement is found in the system.
There is 16GB Ram available and Server is HP-UX and with Netweaver2004s with Oracle 10.2.0.4.0 installed in it.
The Main problem is while running a report or creating a query is taking way too long time.
Kindly help me.

Hello SIva,
Thanks for your reply but i have checked ST02 and ST03 and also SM50 and its normal
we are having 9 dialog processes, 3 Background , 2 Update and 1 spool.
No one is using the system currently but in ST02 i can see the swaps are in red.
Buffer                 HitRatio   % Alloc. KB Freesp. KB   % Free Sp.   Dir. Size FreeDirEnt   % Free Dir    Swaps    DB Accs
Nametab (NTAB)                                                                                0
   Table definition     99,60     6.798                                                   20.000                                            29.532    153.221
   Field definition     99,82      31.562        784                 2,61           20.000      6.222          31,11          17.246     41.248
   Short NTAB           99,94     3.625      2.446                81,53          5.000        2.801          56,02             0            2.254
   Initial records      73,95        6.625        998                 16,63          5.000        690             13,80             40.069     49.528
                                                                                0
boldprogram                97,66     300.000     1.074                 0,38           75.000     67.177        89,57           219.665    725.703bold
CUA                    99,75         3.000        875                   36,29          1.500      1.401          93,40            55.277      2.497
Screen                 99,80         4.297      1.365                 33,35          2.000      1.811          90,55              119         3.214
Calendar              100,00       488            361                  75,52            200         42              21,00               0            158
OTR                   100,00         4.096      3.313                  100,00        2.000      2.000          100,00              0
                                                                                0
Tables                                                                                0
   Generic Key          99,17    29.297      1.450                  5,23           5.000        350             7,00             2.219      3.085.633
   Single record        99,43    10.000      1.907                  19,41           500         344            68,80              39          467.978
                                                                                0
Export/import          82,75     4.096         43                      1,30            2.000        662          33,10            137.208
Exp./ Imp. SHM         89,83     4.096        438                    13,22         2.000      1.482          74,10               0
SAP Memory      Curr.Use %    CurUse[KB]    MaxUse[KB]    In Mem[KB]    OnDisk[KB]    SAPCurCach      HitRatio %
Roll area               2,22                5.832               22.856             131.072     131.072                   IDs           96,61
Page area              1,08              2.832                24.144               65.536    196.608              Statement     79,00
Extended memory     22,90       958.464           1.929.216          4.186.112          0                                         0,00
Heap memory                                    0                  0                    1.473.767          0                                         0,00
Call Stati             HitRatio %     ABAP/4 Req      ABAP Fails     DBTotCalls         AvTime[ms]      DBRowsAff.
Select single     88,59               63.073.369        5.817.659      4.322.263             0                         57.255.710
Select               72,68               284.080.387          0               13.718.442             0                        32.199.124
Insert                 0,00                  151.955             5.458             166.159               0                           323.725
Update               0,00                    378.161           97.884           395.814               0                            486.880
Delete                 0,00                    389.398          332.619          415.562              0                             244.495
Edited by: Srikanth Sunkara on May 12, 2011 11:50 AM

Performance issue for this function-module(HR_TIM_REPORT_ABSENCE_DATA)

Hi Friends
I am having performance issue for this function-module(HR_TIM_REPORT_ABSENCE_DATA) and one my client got over 8 thousend employees . This function-module taking forever to read the data. is there any other function-module to read the absences data IT2001 .
I did use like this .if i take out this F.M 'HR_TIM_REPORT_ABSENCE_DATA_INI' its not working other Function-module.please Suggest me .
call function 'HR_TIM_REPORT_ABSENCE_DATA_INI'
exporting "Publishing to global memory
option_string = option_s "string of sel org fields
trig_string = trig_s "string of req data
alemp_flag = sw_alemp "all employee req
infot_flag = space "split per IT neccessary
sel_modus = sw_apa
importing
org_num = fdpos_lines "number of sel org fields
tables
fieldtab = fdtab "all org fields
field_sel = fieldnametab_m. "sel org fields
To Read all infotypes from Absences type.
RP_READ_ALL_TIME_ITY PN-BEGDA PN-ENDDA.
central function unit to provide internal tables: abse orgs empl
call function 'HR_TIM_REPORT_ABSENCE_DATA'
exporting
pernr = pernr-pernr
begda = pn-begda
endda = pn-endda
IMPORTING
SUBRC = SUBRC_RTA
tables
absences = absences_01
org_fields = orgs
emp_fields = empl
REFTAB =
APLTAB =
awart_sel_p = awart_s[]
awart_sel_a = awart_s[]
abstp_sel = abstp_s[]
i0000 = p0000
i0001 = p0001
i0002 = p0002
i0007 = p0007
i2001 = p2001
i2002 = p2002
i2003 = p2003.
Thanks & Regards
Reddy

guessing will not help you much, check with SE30 to get a better insight
SE30
The ABAP Runtime Trace (SE30) - Quick and Easy
what is the total time, what are the Top 10 in the hitlist.
Siegfried

How to set naming standards for SQL Developer

I am using SQL Developer version 3.0.04.
In the newly integrated and very useful Data Modeler, we can set preferences for the naming standards to be applied when creating logical and relational model objects ( primary keys, foreign keys, et cetera). I would like to know if there is a way to set naming standards for the relational objects we create in SQL Developer on existing tables ( ( primary keys, foreign keys, et cetera).
Any help in setting such preferences would be appreciated.

Hi,
If you want to set up a diagram for an existing database, you can use File/Data Modeler/Import/Data Dictionary to import its definitions.
Alternatively you can open a Data Modeler Browser (using View/Data Modeler/Browser), expand the node for Design "Untitled_1",
expand the node for Relational Models, and select Show from the Right-click drop-down menu for "Relational_1" to create a Relational Model diagram.
You can then drag Tables from SQL Developer's Connections tree onto the diagram.
Once you have a Relational Model you can reverse engineer it to an Entity-Relationship model using the << button in the button bar
(or by selecting "Engineer to Logical Model" from the drop-down menu for the Relational Model).
Note that there is now a separate forum for SQL Developer Data Modeler topics: SQL Developer Data Modeler
David

Mouse moving issue in sql developer 3.2

Hi,
I'm using sql developer 3.2 in vmware .I'm facing issue when i try to select the package/procedure from left side tree structure with mouse,mouse pointer is moving to some other place.
If i try to click on one object name(procedure/package/function) then mouse pointer is moving to other object name automatically.It is very difficult to work .Can some advice why it is ? And how i can resolve?
And at the same time no issue with sql developer 1.1 .
Environment:
In side vmware
Os:Xp
Sql developer Version 3.2.20.09

Enable security descriptors = Allow virtual applications full write permission to the virtual file system.
Here is how it looks like:
https://twitter.com/packageologist/status/462180503995813888/photo/1

I cant get Fourth Elephant (Insider for SQL Developer)

hi,guys
please, help me.
I want to user insider for sql developer of fourth elephant.
but I cant access
http://fourthelephant.com/sqldeveloper/download/
who used it?
thanks.

yes, I see
I want to know someone downloaded it.
can anyone share it?

Need java 1.6.0_4 for SQL developer 3.2 64bit, Win 7

Hi All
I Need java 1.6.0_4 for SQL developer 3.2 64bit, Win 7.
SQL developer behaves weirdly sometimes. It frequently drops connection, doesn;t show compile button when i open a procedure and certain other things.... I found ver 3.0 quiet stable.
I think it may be because of my incorrect java version (1.6.0). Please tell me how can I get this Java version 1.6.0_4. I checked oracle.com, version 35 is available there....
Can you please help me by providing this ?
Thanks

>
I Need java 1.6.0_4 for SQL developer 3.2 64bit, Win 7.
I think it may be because of my incorrect java version (1.6.0). Please tell me how can I get this Java version 1.6.0_4.
Can you please help me by providing this ?
>
No - we can't provide it. You have to download it yourself. If you have trouble with the download you should report the problem to Oracle.
>
I checked oracle.com, version 35 is available there....
>
If you checked at the Java SE Downloads page
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Then you should have seen the 'Previous Releases' link jus above the download Icons near the top of the page.
http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase6-419409.html#jre-6u1-oth-JPR
All of the available prior versions are available at that link.
But I strongly suggest you heed the advice given to use the latest 1.6 version of Java available unless you have a very good reason not to.

Re: GeoRaptor 3.2.1 Released for SQL Developer 3.x

Hey,
Referencing this that was posted in early September 2012:
GeoRaptor 3.2.1 Released for SQL Developer 3.x
I am supporting GRE's and the like at UC Berkeley and I really want to hook them up with this plug because it will make their life MUCH easier. But I have some pretty basic problems:
1. A VERY simply table that has an 8307 linestring. The query that GR defaults when the table is added :
SELECT rowid,"ID","NETWORK_ID","BEG_NODE_ID","END_NODE_ID","LENGTH","SPEED_LIMIT","DETAIL_LEVEL",
"IN_SYNCH","CREATED","MODIFIED","CREATED_BY","MODIFIED_BY","MODSTAMP","NET_GEN_ID",t.GEOM as GEOM
FROM VIA.LINKS_HOLD t
WHERE SDO_FILTER(t.GEOM,?,?) = 'TRUE'This seems to do something but nothing is ever displayed. The table definition is as follows:
CREATE TABLE LINKS_HOLD (
ID NUMBER,
NETWORK_ID NUMBER,
BEG_NODE_ID NUMBER,
END_NODE_ID NUMBER,
GEOM MDSYS.SDO_GEOMETRY ,
LENGTH NUMBER(9,3),
SPEED_LIMIT NUMBER(3,0),
DETAIL_LEVEL NUMBER(3,0),
IN_SYNCH NUMBER(1,0),
CREATED DATE,
MODIFIED DATE,
CREATED_BY VARCHAR2(30 BYTE),
MODIFIED_BY VARCHAR2(30 BYTE),
MODSTAMP TIMESTAMP (6),
NET_GEN_ID NUMBER
)And some sample data. I am only including the geometry
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18477, 34.02929, -118.18156, 34.02932))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18268, 34.02393, -118.18269, 34.02631))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18269, 34.02631, -118.18268, 34.02393))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18257, 34.02731, -118.18387, 34.0273))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18387, 34.0273, -118.18257, 34.02731))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18256, 34.02631, -118.18269, 34.02631))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18269, 34.02631, -118.18256, 34.02631))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18131, 34.02632, -118.18256, 34.02631))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18256, 34.02631, -118.18131, 34.02632))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18257, 34.02731, -118.18256, 34.02631))Since the query I tried to substitute for the system generated one was:
select geom from links_hold ;When I tried to run that the system responded with and error and pasted the following into the clipboard:
SELECT rowid, GEOM as GEOM FROM (
select
rowid,geom
from
via.links_hold
? MDSYS.SDO_GEOMETRY(2003,8307,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(-180.0,-165.78279266572636, 180.0,165.78279266572636))
? Please keep in mind that very same query will display all the links where I run in the generic map view (GMV) of SQLD and
since GMV has little in the way of additional features it is rather frustrating to see your tool not really working, or what
is more likely is that I have a lack of understanding because I cannot find documentation that will allow me to
move forward w/o bugging you.
So Any light you can throw on this would be of great assistance. Thanks much!

Flying Guy,
The non-display is a major bug that was discovered after GeoRaptor 3.2 was released. I knew it was there a few days after
the release - it got past our testers as well. I hoped to have a release out very soon after but a bunch of things conspired to
stop this from happening. Anyway, no one complained so I figured no one was using it enough to find the bug.
The bug is fixed which you can test if you download the Early Access release from our SourceForge website.
There are some other new functions in this EA that you might discover. The main one being the ability to have a feature count
(those drawn within the map window) displayed on the view / layer tree. See GeoRaptor preferences. Another is the restoration
of right mouse click menus on the sdo_geometry columns of table/mv/view connection nodes. Also, if a table has more than one
sdo_geometry column, the first is no longer selected if you right mouse click/map etc on table node. It will display a pick list
of sdo_geometry columns for you to chose from. (There has also been a major revamp of connection management as I noted
problems since SQL Developer 3.2.)
Please download and try it. Consider joining the GeoRaptor lists to help with testing and documenting. If you find bugs in
the EA please email the right georaptor list, or use the GeoRaptor SourceForge site to register the bug. Or email me
directly simon at spatialdbadvisor dot come.
I hope to have a release ready by the end of the week but I have not heard back from the small group of testers
that we have something that is ready to go.
Wrt documentation we have added some where users have created some for me with my input. Please volunteer to
create documentation.
The simple fact of life is that:
1. GeoRaptor is downloaded by lots and lots of people (a good thing).
But:
<complain>
2. Very few responses ever occur to postings made about GeoRaptor on this forum or on our sourceforge forum: disheartening;
3. Very few bug reports or enhancement requests ever get created at sourceforge: disheartening;
4. I have become the only developer which is a bad thing. I known of some Java developers who have used GeoRaptor but
most/all expect someone else to fix bugs or develop the tool. I have spend thousands of hours on a tool that I find useful because SQL Developer
is my main Oracle access tool. But I have never, ever heard from more than 10 people over the past 3 years that they too find it useful: disheartening;
5. Attempts to contact downloaders routinely fall on deaf ears or fail: disheartening;
6. Requests for documenters, developers, testers are ignored or fail because we can't contact anyone who downloads GeoRaptor: disheartening.
</complain>
Like a lot of open source projects I do not get paid for anything I do. But what annoys me is that no one - other than a tiny brace of people - will help with anything
even when we ask.
I have also decided that major new functionality added to GeoRaptor eg GeoRasters; WMS; WFS; etc will only be done when sufficient funding, via a fundraising website
makes a set amount. This is something that the PostGIS have started doing and I think it only fair considering how many months each year I spend on development "in
the dark" for no income.
regards
Simon

Writing extension for SQL Developer

Hello all,
I'm new to writing extensions for SQL Developer using JDeveloper. Can you help me with some example with common functionality, like how to get the current connection? Is there some documentation for the oracle.sqldeveloper package? The example may include some techniques like how to get the schema name for a chosen table, get some other info for the table and so on.
Thank you in advance!

Hello all,
I'm new to writing extensions for SQL Developer using JDeveloper. Can you help me with some example with common functionality, like how to get the current connection? Is there some documentation for the oracle.sqldeveloper package? The example may include some techniques like how to get the schema name for a chosen table, get some other info for the table and so on.
Thank you in advance!

Performance issues for sql developer

Similar Messages

Maybe you are looking for