By default, SQL Developer will migrate a Sybase, SQL Server ,... database to a brand new target user in Oracle. This new user is defined (CREATE USER ... ) at the start of the the generation script.
SQL Developer can move data online and offline.
During Oracle OpenWorld a customer asked how to turn off the autogenerate of GROUP BY clause when using JDeveloper.
Most of the time SQL Developer does a good job of migrating a database from SQL Server, Sybase ,... To Oracle. But there are some tricks to help make very large migrations perform smoother.
Empty Space strings, that is Strings with no text whats so ever '', are treated differently by different databases.
Oracle treats an empty string '' as NULL
Sybase treats an empty string '' as a single spaced string ' '
Some other database support empty strings
In the migration preferences you can decide how to handle empty strings.
You can either migrate them to
1) ' ' A single space.
2) NULL (which is how Oracle would interpret an empty string anyway)
There is one other thing to note.
Sybase FLOAT is generally used to save non integer numbers like fractions where no number of precision can hold the exact value. Sybase FLOATs do not store an exact value
"It stores slightly imprecise representations of real numbers as binary fractions at the hardware level"
Oracle has two data types, FLOAT and BINARY_FLOAT.
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.
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
And an article on the new Estimation Report