We have revamped the migration reports in SQL Developer 3.0 to provide significantly more information about your migration. Instead of "hiding" this information under the Migration Report navigator , now the reports can be viewed by double clicking on any of the folder nodes in the Migration navigator. The reports are smart enough to tailor the information depending on where in the Migration Navigator you click.
Status
SQL Developer 2.1.1 (and 3.0) supports browsing of IBM DB2 LUW 7, 8, 9 databases.
IBM DB2 iSeries and ZSeries Z/OS are not supported at this time.
To connect to DB2 LUW, SQL Developer first needs the correct JDBC driver.
Only one specific JDBC driver is supported.
db2jcc.jar with db2jcc_license_cu.jar
All other IBM drivers are not supported and may cause problems even if the above two drivers are specified. So best to only add the above two.
These drivers are usually found in your own DB2 database install or DB2 client install.
Barry McGillin has a breakdown of the new migration features of SQL Developer 3.0
http://barrymcgillin.blogspot.com/2010/10/migration-features-in-sql-developer-30.html
And an article on the new Estimation Report
http://barrymcgillin.blogspot.com/2010/10/migration-estimation-from-sql-developer.html
SQL Developer 3.0 EA1 introduces the Copy to Oracle feature.
Copy to Oracle copies a table from a non Oracle database, like SQL Server, Sybase and MS Access to Oracle. The action can be found by right clicking one or more selected non Oracle tables and choosing "Copy To Oracle".
Oracle allows you to query separate databases using Database Links.
You can even setup a Database Link in an Oracle database with a non Oracle database such as SQL Server or Sybase.
Creating these types of Database Links can take some time, and sometimes you just want to reference a small bit of data on another Database and use it in your query.
When you run a query in the SQL Worksheet using "Run Statement" a Data Grid is used to display the results.
If you then want to export these results youll find that the query is run again.
This can be a pain if it is a long running query.
The following may help.
1) The Data Grid is only populated with 50 rows (by default) at a time. This is for performance reasons, but if you want to use CTRL C, to copy the results it will only copy the results which are currently present.
So click on the data grid and do
CTRL END