Sql developer bug list

I find the link of sql developer 1.2 bug fix list. Where can I find the place of bug list of sql developer 1.2 so that we can pay attention to the bugs?

With a Metalink account, users can ask if a bug has been logged and if it is logged to be made public. If there is no bug, a new bug can be logged. Development teams across Oracle use the bug database all the time to track issues. This includes issues between releases and those raised during the development cycle. It does not make sense to publish all bugs.
While monitoring this forum, the SQL Developer team logs bugs and, when related to a specific thread, provide the bug number and publish the bug. Metalink remains the primary support mechanism for logging and tracking bugs.
Sue

Similar Messages

Another SQL Developer bug - End of file in comment

I found another SQL Developer bug in version 3.0.0.4.
If I try to compile some package from file (so I open file with package body in SQL Developer and assign it to some connection) with this kind of comment: /* comment */ behind end of package, I get this error
I got Error(1250,28): PLS-00111: end-of-file in commentFunny is, that when the package is compiled directly from the database - it works.
When I try to compile the package from file with this kind of comment --comment behind the end of package, it also works...

Hi, I think I finally got it. This looks like an ugly fat bug :)
First, we are not using the .sql extensions. For package specification - we use .pks. For package body - we use .pkb.
Create this script:
CREATE OR REPLACE PACKAGE TEST_xxx AS
PROCEDURE TEST_PROCEDURE;
END TEST_xxx; /*0123456789*/Now save this as e.g. "TEST.pks" file. Open this file in SQL Developer and compile it. You will get the "Error(3,27): PLS-00111: end-of-file in comment".
Now look at the result in the database -> Open the package specification from the database and you see this:
create or replace
PACKAGE TEST_xxx AS
PROCEDURE TEST_PROCEDURE;
END TEST_xxx; /*0123456789*The last slash is missing...
Now go back to the file with the package specification and delete one letter from the comment. Compile it again... it works now.
It looks like the length of this kind of comment is limited to 9 characters.
The limitation is there only when:
1) Compiling from file with different extension than .sql !!! If you rename the file to "TEST.sql", SQL Developer opens it as a script file and runs it as a script, so there is no problem with it.
2) It has to be this kind of comment: /* */. One line comments are not limited.

SQL Developer bug or database bug?

This is in SQLPlus,
SQL> alter session set nls_date_format='YYYY-MM-DD HH24:MI:SS';
Session altered.
SQL> select sysdate from dual;
SYSDATE
2006-10-12 12:31:20
SQL> begin
2 dbms_session.set_nls('nls_date_format','''DD-MON-YY''');
3 end;
4 /
PL/SQL procedure successfully completed.
SQL> select sysdate from dual;
SYSDATE
12-OCT-06
dbms_session.set_nls works perfectly, however, in SQLDeveloper, when I run the same thing:
alter session set succeeded.
SYSDATE
2006-10-12 12:30:42
1 rows selected
anonymous block completed
SYSDATE
2006-10-12 12:30:42 <-- Notice how the format is not changed.
1 rows selected
I am wondering if this is a SQLDeveloper bug(more likely) or database bug?

I run the following in SQLDeveloper,
alter session set nls_date_format='YYYY-MM-DD HH24:MI:SS';
select * from v$nls_parameters where parameter='NLS_DATE_FORMAT';
select sysdate from dual;
begin
dbms_session.set_nls('nls_date_format','''DD-MON-YY''');
end;
select * from v$nls_parameters where parameter='NLS_DATE_FORMAT';
select sysdate from dual;
Here's the output from SQL Developer:
alter session set succeeded.
PARAMETER VALUE
NLS_DATE_FORMAT YYYY-MM-DD HH24:MI:SS
1 rows selected
SYSDATE
2006-10-13 12:38:06
1 rows selected
anonymous block completed
PARAMETER VALUE
NLS_DATE_FORMAT DD-MON-YY <-- This proves it's not the database.
1 rows selected
SYSDATE
2006-10-13 12:38:06
1 rows selected
I believe this proves beyond doubt, that it's SQL Developer bug. Perhaps caching NLS settings?

Fallo en SQL Developer , bugs in SQL Developer

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

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

Stupid SQL Developer bug

Hi,
I have this problem. I open some table in SQL Developer, scroll in the middle, put focus on some cell or entire line. Then I open another table in another tab. Then switch back to the first tab. The focus is still as it was before, however the table is always scrolled to the first line.
This happens everytime when I switch to another table tab, so I need always to scroll back. When I switch e.g. on another package and then back, the scroll position is correct...
Is there any workaround or bug fix. It is really annoyng...
Thanks, Dan

Well the carret position is preserved even when you scroll down with a mouse and than click some cell or select entire line. Only the table is scrolled back to the top...
Lets hope they will fix this soon together with dozen of other bugs.
To mwickham:
I use pin by default, otherwise new table would open always in the same window...

SQL Developer Bug: NVL() function error when debug/run stored procedure

Version:
SQL Developer: 1.5.3 (build main-5783)
Oracle DB connected: Oracle9i Enterprise Edition Release 9.2.0.6.0
Stored procedure code like this:
procedure search(V_STATUS_IN IN CHAR(1)) is
begin
declare
V_STATUS CHAR(1) := NULL;
begin
V_STATUS := NVL(V_STATUS_IN, '%'); -- error line
end;
end;
The stored procedure runs well (I mean no oracle exception) when called through Java code (and in TOAD). But when debug/run in SQL Developer, following error at the error line:
$Oracle.EXCEPTION_ORA_6502:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
--------------------------------------------------*/

What parameter are you passing in? It is possible you are trying to cram a multibyte character into a singlebyte container. What are the nls settings for the database and for sqldeveloper?

SQL Developer bug? It does not return DATEs if database is only MOUNTED

I'm logging into a mounted database as SYS to check on things using the V$ views, but any query I do involving DATEs never returns any data. If I remove the DATE column, the query works fine. If the database is OPEN, the query works fine with the DATEs. This is a bit of a problem when I want to check on standby databases for example. Is this the way it's supposed to work?
Help!

The original thread appeared to have gone nowhere, so I raised the issue again. If I have violated forum rules, please forgive me.
I have a choice of using either TOAD or SQL Developer at the site that I have just started at, and I have not used either much. I was leaning towards SQL Developer as its price to functionality ratio is very attractive. However, this issue of not working with a mounted database is a show stopper for me for SQL Developer as I prefer to use a single tool that handles all of the DBA work that I do. So far, TOAD does, and SQL Developer does not.

SQL Developer BUG - ORA-00980 Synonym Translation No Longer Valid

We have a read only database of our Production and when I try to access any data using the SQL Developer, I'm getting the following Error.
Error at Command Line:1 Column:14
Error report:
SQL Error: ORA-00980: synonym translation is no longer valid
If I access the same from SQL Plus, Toad or SQL Station, It works fine. Seems some error in SQL Developer.
Any one with Ideas or suggestions.

we have DB cloned from Prod everynight and is available for us on readonly access. No read /write privs to any user including DBA.
I think the DB is opened with ALTER DATABASE OPEN READ ONLY;
Also to mention, all the tables in the db can be accessible only by read only user who was given select permission on synonyms.
--VB

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.

SQL Developer fails to access update center via http proxy

Hi,
I've configured HTTP Proxy exactly like MS-IE. Anyway, sql developer fails to access web. This is the error message:
java.io.IOException: Server returned HTTP response code: 407 for URL: http://htmldb.oracle.com/pls/otn/f?p=38606:2
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1149)
     at oracle.ideimpl.webupdate.CheckMasterListRunnable.run(CheckMasterListRunnable.java:131)
     at java.lang.Thread.run(Thread.java:595)
Using the same URL in IE gives the following result:
<?xml version="1.0" encoding="UTF-8" ?>
- <centers xmlns="http://xmlns.oracle.com/jdeveloper/update/master">
- <center id="oracle.sqldeveloper.webupdate.internal">
<url>http://htmldb.oracle.com/pls/otn/f?p=raptor:internal</url>
<name>Internal Update Cetner</name>
<domain>.*\.us.oracle.com</domain>
</center>
- <center id="oracle.sqldeveloper.webupdate.otncenter">
<url>http://htmldb.oracle.com/pls/otn/f?p=raptor:center</url>
<name>Official Oracle Extensions</name>
</center>
</centers>
What's wrong?
I'm using sql developer 1.0.0.14.22.
Martin

Given that the update centre worked for me with proxy authentication in v1422 (and Production v1467 - I would recommend that you upgrade to this with a full download if you can't sort out your proxy issues), I would assume that it is not a SQL Developer bug.
Are you still getting HTTP 407 errors when you have entered your username and password?
Unfortunately, I don't know what username/password expectations a RADIUS based proxy authentication would expect. The only thing I can suggest to try is to explicitly put your username/password in your MS-IE proxy setup and see if you can still access the http://htmldb.oracle.com/pls/otn/f?p=38606:2 URL through IE. If this fails through IE, the username/password that you are supplying are not what the proxy is expecting.

Sql developer tool

Hi,
Any body describe sql developer tools in oracle with its feature.
Thanks,
Ritesh

Hi!
Oracle SQL Developer 3.0 - Overview:
http://www.oracle.com/technetwork/developer-tools/sql-developer/sqldev30-overviewpresentation-350356.pdf
Oracle SQL Developer Feature List:
http://www.oracle.com/technetwork/developer-tools/sql-developer/featurelist-094691.html
Oracle SQL Developer 3.0: SQLPlus Support:*
http://www.oracle.com/technetwork/developer-tools/sql-developer/sql-worksheet-commands-097146.html
Best regards,
Matt

Oracle SQL Developer Data Modeler 3.0 Bugs, Resolution and workarounds

The purpose of this thread is to list bugs discovered while using ORACLE SQL Developer Data Modeler 3.0
Mainly with SQL SERVER 2005 and ORACLE 10g models.

SQL Server Physical model doesn't save table identity column.
here are the steps to get this bug:
1. create a table in relational model with a column as an integer to be used as an identity.
2. create or open a physical model for SQL-SERVER 2005
3. open the table in the physical model
4. edit the integer column property dialog
5. tick the identity check box and close the property dialog
6. save the model and close it
7. open it again, you will find the identity check is removed! (probably not saved from the start)

SQL Developer 3.0 Bug

In ORACLE Developer 3.0.04 is a bug in showing the functions or procedures of a package. When "for update nowait" is included in source code no functions or procedures will be shown.
select vts_server
into v_server
from vt_server
where vts_status = 1
and vts_verfuegbar_knz = 'J'
and vts_server = i.vts_server
for update nowait
When this line will be comment out, the list is already fine.

Known issue. See package body procedures are not displayed (3 posts down from yours.)
Brian Jeffries
SQL Developer Team

SQL Developer - Cannot see list of tables in my connection

Hi - when I downloaded and started to use the SQL developer tool, once I connected, I could see all of the tables/columns in my connection on the left side of the tool, and I had my query panel, results panel, and SQL history stacked on the right. Suddenly something has changed, and I cannot see the list of tables, etc. in my connection anymore, so I have to rely on memory and SQL history to remember the table and column names. It has to be "hidden" somehow, but view-connections does not help, and trying to click and drag windows doesn't uncover it either.
Any suggestions?
Thanks!

Probably better to ask in the SQL Developer forum here: SQL Developer
I've been trying the version 2 beta though and it has quite a few bugs in. Table browsing is working fine for me, but all my functions and procedures have disappeared from the tree view. It does odd things with code formatting too.
I don't think it will be supplanting trusty old command line SQL Plus for me yet any time soon...

Sql developer bug list

Similar Messages

Maybe you are looking for