Contents

1. Known Issues
2. Accessibility Issues
3. Globalization
4. Other

2.  Known Issues

This list is not all-inclusive. It includes higher priority bugs and those reported by the community.

• General
• Worksheet
• Connections
• PL/SQL
• Query Builder
• Import/Export
• Oracle 8.1.7 (Not Certified)
• Vista
• Migration Workbench
• 64 Bit
• Linux

2.1  General

• Bug 5604542: You can't invoke SQL*Plus for tnsnames connections. (Workaround, use External Tools... menu option)
• Bug 5087402: NLS settings are not used for BINARY_FLOAT/BINARY_DOUBLE
• Bug 6319706: Can't CREATE USER, when using users other than SYSTEM or SYS, although they have the correct privileges.
• Bug 6087256: Cannot create user, if you have insufficient privileges. Menu should be disabled.
• Bug 6112948: Filter on Synonyms, Table_Type invalid.
• Bug 5598023: Not able to autotrace in sql worksheet - privilege error message incorrect.
• Bug 6047024: Database users not getting refreshed
• Bug 6189078: Problems using oci in some environments
• Bug 6160491: Creating table comments using parameters is not possible in sql dev through ddl
• Bug 6165283: Create table with clob and edit dialog will freeze on primary key selection
• Bug 6130145: Select PL in the edit table dialog for table with lob & product freezes
• Bug 6021260 - open a file > change file - the script name is not in italics

2.2  Worksheet

• Bug 6002713: Describe table@db_link gives an error that the object does not exist
• Bug 6156468: sys_context returns null for 'userenv'
• Bug 5680025: Script generated by export DDL fails with different NLS settings
• Bug 6040171: Describe not working if you do not select the word

2.3  Connections

• Bug 4923597:Cannot connect to remote database as externally authenticated accounts

2.4  PL/SQL

• Bug 5531646: Problem viewing cursor value in debug mode
• Bug 5713984: Save as not working properly for package spec and body with extensions pks & pkb
• Bug 6087125: Debug procedure results in an exception
• Bug 6165182: Can't terminate an executing pl/sql procedure once started

2.5  Query Builder

• Bug 5695262: The Where Clause context menus only display on Mouse Over, otherwise there is only the shadow border.
• Bug 6070139: Query Builder does not support duplicate tables
• Bug 5933202: Can't add an order by in the Query Builder
• Bug 5701783: Query Builder doesn't work for non-Oracle connections

2.6  Import / Export

• EXCEL import into table doesn't work if you don't complete all the tabs in order
• Bug 5968147: Cannot create correct SQL*Loader file for spatial data
• Bug 6078557: Incorrect decimal separator when importing data from xls

2.7  Oracle 8.1.7

SQL Developer is only certified for Oracle database 9.2.0.1 and above. There is limited 8.1.7 functionality, including browsing and editing data, running DML and DDL and general SQL Worksheet functionality. You can edit, compile and debug PL/SQL.

• Bug 6086772:SQL tab and Export from 8.1.7 does not work

2.8  Vista

• Bug 6040193: Debug fails in Vista
• Bug 6046813: Check for updates hangs when stop button clicked.
• Bug 6043231: Import connections fails

2.9  Migration Workbench

• Bug 6085105: Filtering not working correctly during language translation
• Bug 6087351: Problem with running the generated ddl
• Bug 6087352: The Scratch Editor for MySQL does not support statement level translations.
• Bug 6137655: Create link tables in mdb for oracle database broken
• Bug 6145280: Return query not translated correctly
• Bug 6195689: Clicking move date under actions for a converted model displays messages
• Bug 6199952: Does not migrate MA Access default values correctly
• Bug 6033625: Unable to connect to mysql, driver issues
• Bug 6057439: New connection > sqlserver host name does not allow trailing space
• Bug 6030751 - create new connection for access db does not have label for file selection field

2.10  64 Bit

• Bug 6273949: Sqldeveloper.exe does not work with jdk installed in win64 oracle_home

2.11  Linux

• Bug 6110527: Create a connection with type tns - get error loading native jdbc driver

3.  Accessibility Issues

The following is a list of known issues regarding accessibility using JAWS. The testing was done using JAWS version 5.10.

• Connections > New Connection - dialog box not read
• Connections - tree structure not read
• Tables > Create Table - buttons not read
• Data > Edit - buttons not read in edit value dialogue box
• Other User > Create User - not all items read
• Other User > Drop User - SQL statement under sql tab not read
• Any Object > right click - context menu not read
• Any Object - many tabs and details not read
• SQL Worksheet > right click table name > describe - contents of dialog box not read
• SQL Worksheet - query results not read
• SQL Worksheet > Query Builder - dialog box not read
• SQL Worksheet > right click - context menu not read
• View > Snippets - snippet details not read
• Tools > Export DDL > Options - checked options not read
• Help > Check for Update - dialog box not read
• Help - dialog and text not read
• General - menus not read
• General - toolbars not read
• General - main window title not read
  

4.  Globalization

4.1  Character Set Support

SQL Developer can connect to an Oracle Database irrespective of the database character set and the database national (NCHAR) character set. All functionality which does not involve entering or displaying characters outside of the ASCII character set is expected to work correctly with any such database.

Due to bug #5088284 in the JDBC 10.2 driver, the database character set ZHT16HKSCS31 is currently not supported.

Support for displaying and entering characters in scripts outside of the ASCII repertoire is limited to those fulfilling the following conditions:

• The character belongs to the database or to the national character set, depending on the data type of the value containing the character, and
• The script to which the character belongs is supported by the JRE installation on which SQL Developer is running, for example, appropriate fonts are available, and
• The script does not require complex rendering, e.g. it is written left-to-right with no ligatures or character reordering.

Complex scripts, like Arabic, Hebrew, or Devanagari may work in many places, but they have not been tested and they are not guaranteed to work reliably. For bidirectional scripts, e.g. Arabic and Hebrew, no functionality is provided to right-align displayed columns, nor to set directionality. Full support for those languages is planned for a future release.

SQL Developer version 1.2 is available with English user interface only. If the locale of the operating system is not English, a few UI elements, like default wizard buttons and Oracle error messages, may show up in the language of this locale. If the locale of the operating system is Japanese, part of the user interface will appear in Japanese. These translations come from the framework on which SQL Developer is built. Full translation into selected languages is planned for a future release.

This version of SQL Developer has the following globalization issues:

5.  Other


To turn on debug messages:

Edit ide/sqldeveloper/bin/sqldeveloper.conf and comment out the line:

IncludeConfFile sqldeveloper-nondebug.conf and add this line:

IncludeConfFile sqldeveloper-debug.conf