Beruflich Dokumente
Kultur Dokumente
40
Release Notes
1. Known Issues
1.1 General
- Print prints only one page that is a truncation of the current tab.
- Can't invoke SQL*Plus on Windows 2003.
- The menu item, and right-click off a Connection node, for invoking SQL*Plus do
es not work with connections whose passwords are not persisted.
1.2 Connections
- Cannot connect to remote database as OPS$ account.
1.3 Browse
- If connected as sys with sysdba role, Types node displays built in data-types
(e.g. BLOB, DATE, DECIMAL, etc.) If clicked on, will only see "create or replac
e".
1.4 Creating and Modifying Objects
- Editing Triggers - If you have comments before the 'BEGIN' they will be lost i
f you edit. You will see when you click edit that they will not be there. To p
reserve them, they need to be below the BEGIN or you will need to edit via the S
QL Worksheet.
1.5 Table > Data
- Tables > Your_Table > Data - PageUp and PageDown buttons not working correctly
if cursor is in the rownum column.
1.6 Export
- Cannot export if result set contains duplicate column names.
2. Workarounds
2.1 To disable Code Insight
Run SQL Developer from a command line using the following statement:
Windows : sqldeveloper -J-Dsdev.insight=false
Linux or Mac: Run sh sqldeveloper -J-Dsdev.insight=false
or edit sqldeveloper.conf and add "AddVMOption -J-Dsdev.insight=false"
2.2 If DDL tab is null for all objects in a Connection
Your dbms_metadata might be loaded incorrectly.
If this statement fails when executed in a SQL Worksheet against the Connection
select dbms_metadata.get_ddl('TABLE',table_name , user ) from user_tables;
You need to reload $ORACLE_HOME/rdbms/admin/catmeta.sql
2.3 If Snippets are not accessible
You may have not done a clean install. SQL Developer needs to be installed into
a clean directory, not over a previous release.
3. Accessibility Issues
The following is a list of known issues regarding accessibility using JAWS.
- Connection dialog - success or failure of connection not read
- Connection Delete Confirmation Window - message not read
- Connections > right-click Export - not read
- Connections > Tables > right-click - not reading clear filter
- Connections > Database Link - context menu and labels not read
- SQL Worksheet > tab names not read
- SQL Worksheet > Results - not read
- SQL Worksheet > Results > Export - reads incorrectly
- Messages Log - not reading the contents
- Key board navigation from Connections to Reports not possible
- New Gallery - not reading the contents, reads only dialog's title
4. Globalization
4.1 Character Set Support
SQL Developer can connect to an Oracle Database irrespective of the database cha
racter set and the database national (NCHAR) character set. All functionality w
hich does not involve entering or displaying characters outside of the ASCII cha
racter set is expected to work correctly with any such database.
Due to bug #5088284 in the JDBC 10.2 driver, the database character set ZHT16HKS
CS31 is currently not supported.
Support for displaying and entering characters in scripts outside of the ASCII r
epertoire is limited to those fulfilling the following conditions:
- The character belongs to the database or to the national character set, depe
nding on the datatype of the value containing the character, and
- The script to which the character belongs is supported by the JRE installati
on on which SQL Developer is running � for example, appropriate fonts are available � a
d
- The script does not require complex rendering, e.g. it is written left-to-ri
ght 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 bi
directional scripts, e.g. Arabic and Hebrew, no functionality is provided to rig
ht-align displayed columns, nor to set directionality. Full support for those l
anguages is planned for a future release.