Oracle SQL Developer Release 2.1 Patch 1 Release
Notes
Date: February 2010
SQL
Developer on OTN | Features
| Downloads
| Installation
Guide | User's
Guide | Exchange
| SQL
Developer Forum
These release notes contain
the following
- Issues addressed
in SQL Developer 2.1.1.
- Before You Start
- Key Product Features
- New Features in SQL Developer 2.1
- General comments
|
SQL Developer 2.1.1 is a patch release to SQL Developer
2.1. As such no new functionality has been added to the release, instead
the release focuses on key issues that were not addressed with the release
of SQL Developer 2.1. For a list of bugs fixed in this release, please
see the Bugs
Fixed list on OTN.
A number of lower priority bugs have been deferred
to the next major release. The following is a selection of known issues,
reported internally, through the OTN Forum or Metalink.
- Browser
- 8979917:Double-clicking objects in the navigator tree expands
the node
- 9043815: Delete package in recent objects but package body still
remains
- 9083514: Mixed case does not work for editions node
- 9215395: Package and its body has the same name in 'bookmark'
view
- Data
- 8898544: Data committed in another/same session, when updating
data
- 8992313: Grid should persist the previously applied sort
- 9104582: MAC: command copy no longer works in the data grid
- 9201318: Typing in text field of xml type cell does not set the
cell value
- 9217549: Timestamp type can not edit the time part in 'edit value'
dialog
- 9249033: Update the column data with character '@' will show ora-04054
- Database Diff:
- General Database Diff bugs have been reported and noted. These
are scheduled for the next release.
- Export
- 9022960: Export data is missing quote for varchar datatype
- 9146213: Sort the header in 'where' tab in export data, it is
not showing the arrow
- 9154559: Database copy: does not copy directories
- 9179058: Export of large query blocks access to other tables in
connection
- 9190964: Export data fixed format, the fixed length is always
30 bytes
- 9195913: Export data date type, will be exported like timestamp
- 9199991: Import data: source/target data columns mismatch
- 9201927: Import XLS looses line breaks
- 9214731: Import data under other user, it was not imported into
other schema
- 9307157: Export data rowid type will fail to export
- Formatting
- 9215563: SQL formatting: tables moved to new line incorrectly
- 9255625: Different procedure formatting before and after insert
- General
- 9186667: TNSping is hard coded to sid does not use service name
- 9062844 :DBMS_OUTPUT is not available for new session ('cloned'
connection)
- 9197939: Code Insight does not work on describe.
- Migrations
- A number of bugs raised in DB2 and Teradata migrations due to
ongoing and deeper testing of the new functionality introduced in
SQL Developer 2.1
- Preferences
- 9177120: Migrate setting 1.5.4 to 2.1, global ignore list is not
migrated
- PL/SQL
- 9203385: PL/SQ: Edit: wrap selection entry not enabled in worksheet
- Query Builder
- General Query Builder bugs have been deferred. The Query Builder
is scheduled for rewrite in the next release.
- Source Code Control
- 8890147: Dimension versioning: can not edit or check out multiple
files
- 9066753 SVN:'import files to subversion' can't continue if opened
file is not saved
- 9285693: SQL Developer removes the stored password in SVN application
data
- Unit Testing
- 9161664: Commit overlap in unit testing: New updates to multi-user
access is scheduled for next release
- Worksheet
- 9084878: File | Save As for temp worksheet does not set the connection
on new worksheet
- 9179920: Closing SQL Worksheet tab without commit/rollback leaves
open cursors on db
- 9202102: DESC type gives types from all schema
- 9202042: Binds found since q'{ syntax does not get picked up.
- 9205563: Statement output tab needs the dancing icon and progress
bar
|
- Unit Testing
- If you created a unit test repository for
EA1, then you need to drop and create the repository using the production
release. Any unit test repositories created in EA2 or RC1 do not
need to be recreated.
- Platform Support
- Oracle SQL Developer 2.1 is available for
Windows XP , Vista (including 64-bit), Windows 7 (including 64-bit),
and Windows Server 2008, Linux or Mac OS X. (See Certification)
- JDK Support
- Oracle SQL Developer 2.1 release is shipped
with JDK 1.6_11. You can use the embedded JDK or connect to any
installed JDK 1.6_11 or above.
- 64-Bit Windows Support
- There is a separate download for the 64-bit
environment. Download the full 64-bit install and unzip into a new,
empty directory as described for other platforms. Execute the sqldeveloper.exe.
You need to download and install the 64-bit JDK for your platform.
- Installing or Upgrading
- The Check for Updates option to upgrade between releases of SQL
Developer is not supported. This utility is provided to install
third party extensions, this includes the third party drivers required
for migrations and to add additional version control extensions.
- All new releases of SQL Developer require a full installation.
Download and unzip the file into an empty folder. Ensure the "Use
folder names" checkbox is checked when unzipping the file.
- Migrating from Previous Releases
After you have installed the product you
are asked if you want to migrate from a previous release. This migrates
previously set preferences and connections created:
- By default the Confirm Import Preferences
dialog that is displayed selects the latest installation. Select
Yes to migrate the settings from that release or click the
Show All Installations button to browse to an earlier installation.
You can migrate settings from SQL Developer 1.2.1 and above.
- If you are using Oracle SQL Developer 1.1.3 as part of the Oracle
Database 11gR1 installation, navigate to [ORACLE_HOME] \product\11.1.0\db_1\sqldeveloper\sqldeveloper\system.
NOTE: If you install a release later than 1.1.3, this does not replace
the menu item in your Start Programs list. You can add your own
menu option here or a shortcut on the desktop.
- User Defined Reports, Snippets and
SQL History
- User-defined reports, SQL History and user-defined
snippets files are located in the \Documents and Settings\<your_user>\Application
Data\SQL Developer folder. These are also migrated.
- Folders
- If you created folders in release 1.5.1 or above, these are automatically
included in the migration. If you choose not to migrate your settings
between releases, then you can import your old connections. This
does not include folders.
- JDBC Drivers
- The JDBC drivers shipped are Oracle Database
11g Release 1. To connect to earlier version of the database using
the Thick Driver, you need to install an 11g client. i.e. not required
for the Basic Connection.
- Debug Log Window
- This is now set off by default. If you want to see the SQL Developer
debug log window information by default, then include the line IncludeConfFile
sqldeveloper-debug.conf in the sqldeveloper.conf file.
- To start up the debug log window in the product while you are
working, enter "setloglevel oracle.dbtools ALL" in the
SQL Worksheet. This will stay on while you are working, but won't
reopen the log window if you stop and restart the product.
- Third Party Databases
- This release supports IBM DB2 UDB LUW 7,
8 and 9 and Teradata 12, in addition to the current third party databases
supported.
- You will not see any third party tabs in
the connections dialog until you have installed the drivers. Read
this Getting
Started document to show you how.
- You can download and include the third-party
database drivers manually. See the existing
documentation for that on OTN. Alternatively you can use
Check for Updates to setup these drivers.
- Do not use the latest MySQL driver 5.1. Use the 5.0.x drivers
for MySQL.
- TimesTen and In-Memory Database Cache
- Before you can use SQL Developer to connect to TimesTen:
- Install TimesTen 7.0.5+ or 11.2.1.2+ of the server or client
on the same machine as SQL Developer.
- On Linux systems, source the shell script TimesTen_install_dir/bin/ttenv.csh
or TimesTen_install_dir/bin/ttenv.sh to set up the TimesTen environment
variables before launching SQL Developer. On Windows, use the
TimesTen_install_dir\bin\ttenv.bat script.
- Make sure the CLASSPATH environment variable is pointing to
the TimesTen JDBC driver (TimesTen_install_dir/lib/ttjdbc6.jar).
- Read these more detailed release
notes on TimesTen
- Table Filters
- The list of tables displayed includes generated tables, AQ's and
others not previously included in the list. By default
there is a filter on the Tables node to exclude objects from the
recycle bin.
- Code Templates
- Code templates and snippets are now included in the code insight
drop down list. To see the code for these, just start typing the
code, in each case, and the rest of the code entry displays in the
code insight. There is no longer a key sequence for Code Templates.
- Version Control
- Subversion is installed by default with SQL Developer 2.1. To
install CVS, Perforce and Serena Dimensions, please use
Help > Check for Updates.
- Subversion
- If you create a local Subversion repository, ensure there are
no spaces in the path.
- CVS
- If you use a local repository. You must use an external CVS client
and set the CVS versioning properties to point to the external client.
|
Oracle SQL Developer is a graphical user interface for the Oracle database
and provides comprehensive support for the following:
- SQL Worksheet: The SQL Worksheet for SQL, PL/SQL and SQL*Plus commands.
The worksheet supports code insight and completion, code snippets and
templates. Users can run scripts or individual statements. The worksheet
supports a wide variety of SQL *Plus commands.
- Database Connections: A wide variety of database connection for Oracle
and third-party databases. Support includes a basic connection using
a thin JDBC driver and TNSnames, LDAP and Kerberos authentication methods.
There is also support for OS Authentication and a proxy user. Connections
can be sorted into folders for ease of use.
- Connection Navigator: A Connections navigator allows for object browsing,
creation and updates.
- PL/SQL Editor: A PL/SQL editor allows users to create, compile and
debug code. Debugging support includes stepping into code and remote
debugging.
- Import/Export: A wide variety of export and import feature include
export to XML, XLS and INSERT. For importing you can import into an
existing table or create a new table
- Reporting: A selection of shipped SQL reports including data dictionary,
migrations and Oracle APEX reports.
- Migrations and Third Party Database support: Connections to MySQL,
Microsoft Access and SQL Server, Sybase, IBM DB2 and Teradata.
- Version Control: File navigation and version control includes support
for Subversion, CVS, Serena Dimensions and Perforce.
- Data Model Viewer: A data model viewer extension allows you to open
a model created in SQL Developer Data Modeler or visualize tables, views
and object types on Data Modeler diagrams.
- Unit Testing: Users can create step by step unit tests and add them
to unit test suites. Unit tests can be run from the command line
for batch execution.
For a comprehensive list of features, refer to the following pages on
OTN:
|
Oracle SQL Developer 2.1 is the vehicle for two main pieces of functionality,
Unit Testing and Data Modeling.
- Oracle SQL Developer Unit Testing provides a unit testing framework
that allows you to build a set of sequential steps to create test cases
for testing your PL/SQL code. These tests can optionally be collected
into test suites, which can then be run and rerun to verify required
functionality after any changes to your PL/SQL code. Command line access
for executing, exporting, and importing suites or tests is provided
for integration with your build and version control environment.
- SQL Developer 2.1 incorporates a Data Modeler viewer, integrated into
SQL Developer. The Data Modeler Viewer also supports visualizing tables,
views and object types on read-only Data Modeler diagrams. The SQL Developer
Data Modeler Viewer extension is a free extension to SQL Developer.
For a updateable data model, download and review the Oracle SQL Developer
Data Modeler, a stand alone product that supports logical, relational
and conceptual modeling. The tool supports forward and reverse engineering
and import and export from various sources. The Data Modeler supports
an additional standalone model viewer, which allows users to open models
built in the full Data Modeler.
- The SQL Worksheet has been redesigned for SQL Developer 2.1 to support
concurrent task processing for long running operations. Updates to the
worksheet include the support of multiple data grids off the F9 (Run
Statement) command and dockable OWA, DBMSOutput and SQL History windows.
For a comprehensive list of new features, refer to the New
Features 2.1 page on OTN
|
- You are supported by Oracle Support under your current
Oracle Database Support license. Log SQL Developer bugs and issues using
Metalink for the product Oracle SQL Developer.
- You can discuss issues on the Oracle
SQL Developer forum.
- Be sure to use clear subject lines to initiate
a thread
- Try to avoid using old, unrelated threads for
a new issue.
- A list of Bugs
Fixed is available for review. This list includes the higher priority
bugs fixed and some of the issues raised on the forum or through Metalink.
Not all bugs fixed are included in the bugs fixed list. For additional
bugs fixed or to request bugs are published contact Oracle Support.
- Features not yet supported in this release can be
added to the Feature Requests section on the Oracle
SQL Developer Exchange.
- Please review current certification
status for platform and database certification queries.
- TimesTen is part of the SQL Developer install. You will not see the
TimesTen Connection node unless you have TimesTen installed and configured
(see TimesTen section above).
- Support for TimesTen In-Memory Database includes
support for Oracle In-Memory Database Cache and TimesTen In-Memory Database
Release 7.0.3 and later.
- If you did not migrate your connections from a previous
release, you can import them afterwards. Invoke the earlier release
of SQL Developer, export the required connections and import them in
the new release.
- Expired password: When a password expires, an error message is raised
to alert the user. To reset the password, right-click the connection
and select Reset Password.
|