SQL Developer 1.5.4 MySQL migration bug

Trying to use SQL Developer 1.5.4 to "Capture" MySQL schema. Getting this Java exception:
java.lang.Exception: java.lang.NullPointerException
     at oracle.dbtools.migration.workbench.core.ui.AbstractMigrationProgressRunnable.start(AbstractMigrationProgressRunnable.java:141)
     at oracle.dbtools.migration.workbench.core.CaptureInitiator.launch(CaptureInitiator.java:94)
Caused by: java.lang.NullPointerException
     at oracle.dbtools.migration.workbench.plugin.MySQL5Capturer.captureColumnDetails(MySQL5Capturer.java:405)
     at oracle.dbtools.migration.workbench.plugin.MySQLCapturer.captureObjects(MySQLCapturer.java:195)
Please advise.

ok, here is one table that results in the Java exception:
CREATE TABLE user_locations (
user_id int unsigned NOT NULL,
location point not null,
location_source enum ("aaa", "bbb", "ccc") DEFAULT "aaa" NOT NULL,
address varchar(255),
last_update datetime,
UNIQUE (user_id, location(32)),
INDEX (user_id),
INDEX (last_update),
FOREIGN KEY (user_id) REFERENCES users (user_id) on delete cascade on update cascade
)ENGINE=InnoDB DEFAULT CHARSET=utf8;

Similar Messages

Problems using Quick Migrate in SQL Developer 1.5 for MySQL to Oracle 10g

Hi all,
I am trying to use SQL Developer 1.5 migration tools (Quick Migrate) to perform online capture and build source model to migrate from MySQL 5.x to Oracle 10g on Windows platform. I get these errors and the Quick Migrate process fails:
oracle.dbtools.metadata.persistence.PersistableObject.doInsert(PersistableObject.java:238)
I did a search and used the sqldeveloper.cmd script but still fails. Then I created a new database and truncated the repository. I now get the above error plus two new ones listed below:
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
Error loading nls:OALL8 is in an inconsistent state
Error occurred during capture: Protocol violation
It fails during the capture process for MySQL 5.1 database
when it begins to capture the tables from MySQL.
Does anyone know how to resolve these issues when migrating from MySQL to Oracle 10g using Quick Migrate with SQL Developer 1.5 release?
Regards,
Ben Prusinski
Message was edited by:
benprusinski
Message was edited by:
benprusinski

Hi all,
I put the following in my sqldeveloper.cmd file:
SET ORACLE_HOME=%CD%
What is very confusing is that with SQL Developer 1.5, there are several levels and several SQL Developer executables! I am really not sure which of these to use:
I created the SQLDeveloper 1.5 directory called SQLDeveloper1_5 on Windows:
1) cd C:\sqldeveloper1_5\sqldeveloper-5338
there exists a sqldeveloper.exe
2) cd c:\sqldeveloper1_5\sqldeveloper-5338\sqldeveloper\sqldeveloper.exe
3) cd c:\sqldeveloper1_5\sqldeveloper-5338\sqldeveloper\sqldeveloer\bin\sqldeveloper.exe
Which SQLDeveloper 1.5 executable should I be using and where should I place the
sqldeveloper.cmd file?
Also I did try to use a different database and schema for the repository with Quick Migrate but it appears a bug exists in SQL Developer 1.5 version that causes errors with Quick Migrate for MySQL to Oracle? Is this correct?
As an update, I ran the following commands:
cd to
c:\sqldeveloper1_5\sqldeveloper-5338\sqldeveloper\sqldeveloper\bin
sqldeveloper.cmd sqldeveloper.exe
Start sqldeveloper.exe
Perform standard capture for MySQL using the new mig2 schema as the new repository
It starts the capture but fails on the errors below:
Error loading nls:OALL8 is in an inconsistent state
UPDATE
============================
I tried this again and it worked with the exception of one error message listed below:
Here are the steps that I followed:
1. Create a Windows cmd script
Put the following entries in the script:
SET ORACLE_HOME=%CD%
save the command windows script as sqldeveloper.cmd
Copy this script to the base installation directory for SQLDeveloper
Example:
1. cd c:\SQLDeveloper1_5\sqldeveloper-5338\sqldeveloper
2. Start SQLDeveloper with the command script that you created earlier
Example:
Open a Windows shell prompt window and execute the following scripts:
a) sqldeveloper.cmd sqldeveloper.exe
b) sqldeveloper.exe
3) In SQL Developer 1.5
From the Migrate menu,
a) Delete current repository and create a new schema in Oracle target database call it mig2.
b) Then create a new repository in SQL Developer 1.5
c) Right mouse click on the MySQL 5.x database and choose capture
It worked with the exception of one error message:
o.jdbc.driver.OracleDriver
Error while registering Oracle JDBC Diagnosability MBean.
So it looks like something is screwed up with my JDBC drivers and configuration for MySQL. How do I diagnose the JDBC driver issue for MySQL?
Thanks!!!
Ben
Thanks
Ben

Can I use SQL developer for a Sybase IQ migration to Oracle?

Hello,
Can I use SQL developer for a Sybase IQ migration to Oracle?
Currently in the supported list appears only Sybase Adaptive Server 12 and 15.
Thanks,
Florin D.

Sorry, we don't support IQ migrations at this time.

How to get the exact sql developer which used for data migration?

Hi all,
Hope doing well,
Sir i seen a link for data migration that is : http://www.oracle.com/technetwork/developer-tools/sql-developer/sql-server-connection-viewlet-swf-089886.html
in this link when they are connecting to sql database so after clicking on new connection four tab is showing that is oracle, access, my sql, sql server.
i downloaded latest version of sql developer which version is: 3.02.09.30 when i opened this i am not getting those option.
and one more thing i am not getting miragation menu name in menu items.
please help me.
thanks and regards

Hi,
To connect to non-Oracle databases from SQL*Developer youneed to download the relevant JDBC driver.
This is detailed in the documentation in the User Guide -
http://docs.oracle.com/cd/E35137_01/appdev.32/e35117.pdf
in the section -
Database: Third Party JDBC Drivers
The Third Party JDBC Drivers pane specifies drivers to be used for connections to third-party (non-Oracle) databases, such as IBM DB2, MySQL, Microsoft SQL Server, or Sybase Adaptive Server. (You do not need to add a driver for connections to Microsoft Access databases.) To add a driver, click Add Entry and select the path for the driver:
■For IBM DB2: the db2jcc.jar and db2jcc_license_cu.jar files, which are available from IBM
■For MySQL: a file with a name similar to mysql-connector-java-5.0.4-bin.jar, in a directory under the one into which you unzipped the download for the MySQL driver
■For Microsoft SQL Server or Sybase Adaptive Server: jtds-1.2.jar, which is included in the jtds-1.2-dist.zip download
■For Teradata: tdgssconfig.jar and terajdbc4.jar, which are included (along with a readme.txt file) in the TeraJDBC__indep_indep.12.00.00.110.zip or TeraJDBC__indep_indep.12.00.00.110.tar download
To find a specific third-party JDBC driver, see the appropriate website (for example, http://www.mysql.com for the MySQL Connector/J JDBC driver for MySQL, http://jtds.sourceforge.net/ for the jTDS driver for Microsoft SQL Server and Sybase Adaptive Server, or search at http://www.teradata.com/ for the JDBC driver for Teradata). For MySQL, use the MySQL 5.0 driver, not 5.1 or later, with SQL Developer release 1.5.
You must specify a third-party JDBC driver or install a driver using the Check for Updates feature before you can create a database connection to a third-party database of that associated type. (See the tabs for creating connections to third-party databases in the Create/Edit/Select Database Connection dialog box.)
Regards,
Mike

Apex Listener 2.0.1 vs Sql Developer Administration 3.2.20.09 bugs

Apex Listener 2.0.1 / Sql Developer 3.2.20.09 / Apex 4.1.1
1. I'm using basic connection type with service name. Each time I connect to listener administration it is resetted to SID with default name as orcl.
2. Test Settings does not work in case hostname is localhost.
Database Settings apex:Cannot connect to APEX_PUBLIC_USER. Исключение ввода/вывода (input/output exception): The Network Adapter could not establish the connection>
At the same time it's working in defaults.xml:
<entry key="db.hostname">localhost</entry>I'm not sure why. Database and Apex Listener are installed on the same mashine. May be this can help:
<Warning> <Server> <x> <> <DynamicListenThread[Default]> <<WLS Kernel>> <> <> <> <BEA-002611> <Hostname "x", maps to multiple IP addresses: 10.110.x.x, 0:0:0:0:0:0:0:1> 3. I can see "Enable RESTful Services" action in (url http://docs.oracle.com/cd/E35137_01/appdev.32/e35117/intro.htm#autoId110)SQL Developer User's Guide. Still there is no such action in Sql Developer. Thus settings are always uploaded with enabled RESTful Services.
I see error
The pool named: apex_al does not existeach time I connect to Apex Listener Administration in case of RESTful Services is not configured during configuration of apex.war.
I can't find any restrictions for RESTful Services to be configured. So I think this error is unnecessary.
4. From sql developer User's Guide
Connect (context menu only): Connects to the Application Express Listener (see Connecting to Application Express Listener Server).Retrieve Settings, Upload Settings, and Launch URL are enabled when you connect to the Application Express Listener.>
administration settings are retrieved and displayed but still Retrieve Settings, Upload Settings, and Launch URL are disabled in context menu after connection.
I need to perform New Administration action to make them enabled.
Is this expected behavior ?
Is this all bugs or known features ?
Regards,
Igor

DB: V11.2
APEX V 4.2.3.00.08
APEX Listener: V2.0.5.287.04.27
SQLDeveloper: Version 3.2.20.09
OS WIndows 7 64 bit
I am trying to create a connection to a standalone Apex Listener installation via SQL Developer to manage the listener settings. I start a new connection and after entering the UN/PWD of the Listener Administrator I get the following error:
Authentication failed
"CANNOT CONNECT TO CONNECTION.
INVALID RESOURCE OWNER CREDENTIALS"
In the Standalone APEX Listener DOS window I'm getting the following error message:
SEVERE: The pool named: apex_al does not exist
So where do I even start to trouble shoot this???
I add a connection as follows:
Connection Name: Connection
Usename: adminlistener (pwd=adminlistener configured using command :java -jar apex.war user adminlistener "Listener Administrator")
HTTP radio button
Hostname: localhost
Port: 8080
Server Path: /apex
thanks in advance
Paul Platt

SQL Developer 3.1: Job Chains - 2 Bugs.

Hi.
Just having a play with defining job chains in SQL Developer 3.1 and I came across these bugs...
1) When you try to define a new chain using SQL Developer you get, "ORA-01741: illegal zero-length identifier"
If you look on the SQL tab you can see that it is messing up the double quotes, placing two sets of double quotes around the chain_name.
BEGIN
    sys.dbms_scheduler.create_chain(
        comments => '',
        chain_name => '"TEST".""test_chain_3""'
      sys.dbms_scheduler.enable(name=>'"TEST".""test_chain_3""');
END;If you remove the extra quotes and run the code it works fine.
2) The job chain diagram seems to be case sensitive as far as the rule definitions are concerned.
If you follow the chain setup in SQL*Plus described here (http://www.oracle-base.com/articles/10g/SchedulerEnhancements_10gR2.php#job_chains), then check the associated diagram in SQL Developer it is displayed properly.
Now repeat the chain definition from SQL*Plus, but this time define the conditions and actions of the rules in lower case (which is valid and functions as expected).
BEGIN
DBMS_SCHEDULER.define_chain_rule (
    chain_name => 'test_chain_1',
    condition => 'TRUE',
    action     => 'start chain_step_1',
    rule_name => 'chain_rule_1',
    comments   => 'First link in the chain.');
DBMS_SCHEDULER.define_chain_rule (
    chain_name => 'test_chain_1',
    condition => 'chain_step_1 completed',
    action     => 'start chain_step_2',
    rule_name => 'chain_rule_2',
    comments   => 'Second link in the chain.');
DBMS_SCHEDULER.define_chain_rule (
    chain_name => 'test_chain_1',
    condition => 'chain_step_2 completed',
    action     => 'start chain_step_3',
    rule_name => 'chain_rule_3',
    comments   => 'Third link in the chain.');
DBMS_SCHEDULER.define_chain_rule (
    chain_name => 'test_chain_1',
    condition => 'chain_step_3 completed',
    action     => 'END',
    rule_name => 'chain_rule_4',
    comments   => 'End of the chain.');
END;
/Now check the diagram again in SQL Developer and you will see that all the steps are present, but the links (rules) are not correctly displayed. Seems like it is case sensitive...
If you need any more info, please ask.
Cheers
Tim...
Edited by: TimHall on Feb 10, 2012 4:23 PM

I have confirmed your two test cases are indeed bugs and I have raised them. The first seems to be if you have a mixture of _ and lowercase characters in the name but we will look at other cases too. The second is that the parsing of the condition/action does not uppercase unquoted ids. The second can be cirumvented by using quotes etc.

30EA1 - SQL-Developer 3.0.02 Connection Folder Bug

hi,
there are several treads concerning the poor "connection folder" (no sub-folders, folder-structure not in connection export,...) functionality...
Today i found an new annoying "feature". If you rename a connection within a folder and restart SQL Developer, you will find the connection outside at the bottom of the folders. If you rename all connections within a folder, the folder disappears after restart.
Its essential to reimplement the connection pane. The storage of the folder-structure outside "connections.xml" in "product-preferences.xml" will always be unmanageable!

Bug 9734466: RENAME CONNECTION MOVES IT OUT OF THE CURRENT FOLDER
see also Rename Connection
I will add reference to this post in the bug.
Brian Jeffries
SQL Developer Team

30EA3 SQL Developer 3 error message while migrating SQL sever database

I was mirating a SQL sever 2005 database to Oracle 11g, and got the following error message during the process:
"Migration action have failed. Check the migration reports for Detail. :null".
After the error message, I could see the "Captured Database Objects" and "Converted Database objects" under the "Migration Projects". However, if I open the generated scripts, it only contains the fowlloing, nothing else:
"SET DEFINE OFF;
PROMPT Creating User Emulation ...
CREATE USER Emulation IDENTIFIED BY Emulation DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP;
GRANT CREATE SESSION, RESOURCE, CREATE VIEW, CREATE MATERIALIZED VIEW, CREATE SYNONYM,CREATE PUBLIC SYNONYM TO Emulation;"
What's the cause of this problem, please advice. Thanks.
Bob

Hi Bob,
The next thing in the generation script should have been the definition of the sqlserver_utilities package.
This package emulates some of the system functions found in SQL Server.
It gets placed into your converted model as the very last step of the conversion.
Building the generation script (where your failure happened) is straight forward and I wouldn't expect an error here.
I would guess something went wrong during the capture or conversion and is only surfacing during the generation phase when it tried to write the sqlserver_utilities package to the generation file.
I could be wrong, but I would manually check that conversion completed successfully first.
1) Browse you converted model under
Migration Projects "Nav" : Projects > YourProjectName > YourModelName(default a date)> Converted Database Objects > Procedures > YourProcName
a) Are there any red crosses on any of these nodes in your navigator ?
b) If you right click on a converted database name is "reconvert" grayed out or available?
c) run the following in the SQL Worksheet against the same connection you used for the migration repository
select * from md_packages;
Is there one row there with the definition of sqlserver_utilities in its package_header and native_sql columns?
Also do you have anything in the capture issues, conversion status or conversion issues reports (double click you project and the migration reports should pop up on the right hand side, each report a separate tab) ?
Just trying to pinpoint what happened here.
Thanks for your feedback,
Dermot
SQL Developer Team.
Edited by: Dermot ONeill on Feb 16, 2011 2:48 PM

SQL-Developer 4.0.0.13.80 Bug? No negative values for axis scale accepted

I reported this problem already for the versions EA1 and EA2 of SQL-Developer 4 (4.0EA1 No negative values for axis scales in diagrams) but it still exists in 4.0.0.13.80: Even if it is now possible to define the minimum and maximum values for the y-axis of a diagram, I found no way to enter negative values for the minimum value. Neither -100 nor (100) is accepted. The value always switches to 0. I have a report which shows values from -97 to 387. Automatic scaling sets the y-axis from -200 to 500 but I would prefer a scale from -100 to 400. How is this possible?
btw.: the German translation for "scale" in the diagram settings is bad. It is translated with "Nachkommastellen" but it should be "Skalierung".

In 4.0EA2 this topic is still not fixed.

SQL Developer migration tool

Does anyone have any experience migrating just one schema from MySQL to Oracle?
I've specified my database that I want the migration tool to use when I do the migration, but it goes ahead and tries to grab every single function, procedure, table for every single user in the database.
I'm basically trying to migrate a customers' mysql dataset to our oracle db.
Any thoughts?
Thanks in advance all!
---Patrick

Patrick,
did you already read the Oracle® Database SQL Developer Supplementary Information for MySQL Migrations manual, available at:
http://download.oracle.com/docs/cd/E12151_01/doc.150/e12155/toc.htm
The chapter 2.2 is dealing with schema migrations. Perhaps that is useful for you. If there is going something wrong for you and different as described in that manual then please let me know more details.
Best regards
Wolfgang

BUG: SQL Developer 1.5.3 CSV export column order broken

There's a bug in the 1.5.3 release of SQL Developer regarding data export. This bug re-orders the column order in the data export to be alphabetically sorted. This produces mangled CSV files if used on a table or a view.
This is a critical bug to me since I need to produce lots of ad-hoc data CSV export files. I'm staying with SQL Developer 1.5.0.53 (53.38) for now as it doesn't have this problem.
This is the same bug as present in Jdeveloper 11.1 as described in my post here: BUG: Jdev 11.1.1.0.0 -- DB table data export column order is not preserved
Quoted from that post:
When I connect to Oracle database, get the table list, right click on the table and select 'Export Data'->csv. The dialog box opens with three tabs: Format, Columns, Where. The column order displayed in both tabs Columns and Where is alphabetic. Because alphabetic ordering re-arranges columns from their initial ordering in the table, this screws up CSV export because columns are not in their intended order. This same problem occurs when I try to export data from views to generate a CSV file with a particular column order.
Please open/check bug report if it's already open.
Thanks!

This happens with all of the export options for tables or views if you right click from the connections tab table list. If I pull it up in the main window and go to the data tab, I can then right click and it will keep the column id order for some of the views and tables. But not all.
I am running 1.5.3 Build Main 5783 on a Windows XP Professional Service Pack 3 platform

Error in SQL Developer: Database Connections has no JNDI context so cannot

Hello,
I have installed SQL Developer 3.1.07 version on Linux. Previously I was able to create a connection and browse the existing tables, add tables, etc.
Now when I launch SQL Developer, I see that no connections are displayed. Instead there are these three messages indicating an error. Can you please advice on how to resolve this?
Thanks,
Errors:
SEVERE     44     0     oracle.jdeveloper.db.DatabaseConnections     DatabaseConnections has no JNDI context so cannot list connections.
SEVERE     43     36     oracle.jdevimpl.db.adapter.DefaultContextWrapper     Failed to create naming Context for db connections at url: file:/home/user/.sqldeveloper/system3.1.07.42/o.jdeveloper.db.connection.11.1.1.4.37.59.48/connections.xml
SEVERE     42     0     oracle.jdevimpl.db.adapter.DefaultContextWrapper     Failed to create naming Context for db connections at url: file:/home/user/.sqldeveloper/system3.1.07.42/o.jdeveloper.db.connection.11.1.1.4.37.59.48/connections.xml

Hi uparthas,
Here is a similar thread (Windows 7) marked as answered, and may be applicable to a Linux environment if you are using jdk1.7 rather than jdk1.6:
Lost my connections.
If that does not solve the issue, you might also wish to ...
1. Exit SQL Developer
2. Delete or rename the /home/user/.sqldeveloper/system3.1.07.42 directory
3. Launch SQL Developer, perhaps without choosing to migrate settings from a prior install.
Hope this helps,
Gary
SQL Developer Team

Cannot debug procedure in 11g database using SQL Developer

Hi,
We have recently migrated our database from 10.2.0.4 to 11.2.0.2. We were able to debug procedures using PL/SQL Developer earlier but after 11g migration we are not able to debug the same procedure in 11g database.
Is it that we require 11g PL/SQL developer with 11g client installed to debug?

11g has a new privilege required to debug stored procedures, DEBUG CONNECT SESSION.
Does your user have this priv?
No client required to debug, but if you ARE using a client via OCI THICK preference, be sure that the client version matches the server version.

SQL Developer Migrate mySQL to 11g gets ORA-00972 due to 30 char name limit

I am running MySQL version 5.5.30 server, SQL Developer 3.0.04 Build MAIN-04.34, and Oracle Enterprise Server 11.2.0.1.0, and using Migrate option to move both data dictionary and data from mysql to Oracle
Most of the steps worked fine using OnLine option: used Capture just fine to generate the repositiory, and Convert generated DDL script just fine in the SQL Developer file folder.
It failed to create users due to privs, but I created them manually: emulation user and also the MYSQL data schema user, after which I took the generated DDL, connected to my Oracle data schema user, and ran the DDL to basically create all the objects. And found out that over 50 tables / column names from MYSQL are longer then 30 char, and thus the generated DDL fails to create objects..
Question - I can manually replace the names with shorter 30 char names, but if I do, my data migration step will not work.
i cannot find references to 'name too long' problem anywhere is SQL Server documentation..
here is the Oracle error example:
Error report:
SQL Error: ORA-00972: identifier is too long
00972. 00000 - "identifier is too long"
*Cause: An identifier with more than 30 characters was specified.
*Action: Specify at most 30 characters.
Creating Primary Key Constraint PRIMARY_1 on table bank_account ...

Hello,
have you tried the offline migration option? Then you can probably modify also the ctl file for the SQL*Loader to reflect your changes in the DDL script. I didn't yet try it out, it was just an idea that came to my mind.
Regards
Wolfgang

Migration mysql to Oracle thr SQL Developer 1.2

Customer using SQL Developer migrate MySQL4.1.22 database data to
Oracle 9206 database. Capture and Convert completed but it hang during
generate stage.
Customer follow steps published in otn.oracle.com.
1-2 steps
Create a schema and user, named "club" on oracle ,as same as the user in
mysql database, and with sufficient tablespace size.
Capture the Mysql DB, and get the Capture Model.
Convert to oracle model, and get the Converted Model.
Capture Mysql and Convert to oracle model are successful,
3rd steps
Generate failed, and no error logs, the new windows can't failed to continue.
Generating Oracle SQL
Object Type No of Objects Generated
User 1
Schema 1
Sequence 36
Table 1
Generation Failed.
mysql DB is linux as 4
oracle DB is linux as 4
Appreciated for any suggestion.
Thanks,
Michael.

Can you tell which version of SQL Developer are you using. Also it seems that generate is not hanging but fails at some stage. Hence you are getting the failure message. Please check if anything is displayed in Log window or console.
- Rakesh

SQL Developer 1.5.4 MySQL migration bug

Similar Messages

Maybe you are looking for