Issue with SQL Developer connect to SQL server

Question

I'm using "SQL Developer 2.1.1.64.45" to work on a migration project which needs to convert a SQL server database to a Oracle 11g database. But I got an issue when I setup the SQL server connection. The SQL Developer let me connect by selecting a SQL server database name (For example: Northwind), but once connected, it always connected to "master" database instead. The "SQL Developer" is running on Windows 7 Professional (x64) platform. My Oracle database is 11g, and SQL server database is SQL 2005. And my SQL server instance name is "SQL2005". Anyone have ever experienced this problem? Thanks in advance.
Edited by: user8276338 on Feb 8, 2011 1:05 PM

Answer 1

Hi Bob,
Thanks for the feedback, lets stick with SQL Developer 3.
Correct me if I'm wrong,
You attempted to migrate from SQL Server to Oracle including target generation and datamove in one go, by filling in each step of the migration wizard to the end.
During the datamove you got
ORA-01000:maximum open cursor exceeded
So it looks like SQL Developer during the migration is not closing cursors fast enough and hits the maximum number of open cursors in your Oracle database.
I think the default max open cursors is 300 in Oracle.
There are a few things we can do here.
You should be able to see the new migration project in your Migration Projects navigator.
By navigating down the project tree to "Converted Database Objects" we can attempt the data move again by right clicking and choosing "Data Move".
But first I would restart SQL Developer so as to free up any lingering open cursors.
That may allow you to complete the data move, as the only cursors being open are being used in the data move and not some cursors which may have been left open from previous steps in the migration.
Now from my perspective I would like to identify where are we leaving open the cursors, so I'm going to setup some testcases my end to see if I can replicate.
From your perspective Id presume you just want to move on with the migration.
So if the above (shutdown and attempt just the data move) doesnt workyou could
A) Increase the MAX OPEN CURSORs on your Oracle databases so it complete the data move
or
B) Use the offline data move technique.
A) Increase MAX OPEN CURSORs
This wiki explains how to do that, looks like 1000 is fairly common, but even a much larger number is not a problem
http://wiki.oracle.com/page/OPEN_CURSORS
ALTER SYSTEM SET OPEN_CURSORS = 10000;
OR
B) Offline Data Move
If you are moving large amounts of data (say > 1GB), then the standard data move (we call it online), which just uses JDBC to SELECT * FROM and INSERT INTO may not cut the mustard.
In this case you can try using our offline technique. SQL Developer will generate a set of scripts for you.
unload_script.bat will use SQL Servers BCP tool to dump out the table data into DAT files.
oracle_ctl.bat will load the data in the DAT files into Oracle.
As we know the names of all the tables, columns ,both SQL Server and Oracle, we can generate fairly good scripts.
The benefit of this technique is large amounts of data can be migrated and you get to use tools designed to dump data and load in data, so you have better error logging and tweaking.
To attempt this in the Migration Wizard , Data Move page, select offline.
If you can describe your database a bit (number of tables, number of procedures, amount of data to migrate) I may be able to define my testcase better so I can replicate the issue.
Thanks
Dermot
SQL Developer Team.