My Oracle Support Banner

Unable To Use SQL Developer To Migrate A MS Access Database To Oracle. (Doc ID 1970868.1)

Last updated on JUNE 08, 2023

Applies to:

Oracle SQL Developer - Version 3.2 to 3.2 [Release 3]
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.

Symptoms

Attempting to migrate a MS Access (Office 2010, Version 14.0.7143.5000 32-bit) database to Oracle 11.2.0.x using
SQL Developer Migration Workbench (in this case, version 3.2.20.09)


The following document is referenced for this migration:
http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/hol08/sqldev_migration/msaccess/migrate_microsoft_access_otn.htm#p

Completed the following steps:


Creating the REPOSITORY User – COMPLETED, NO ISSUES

Creating the Migration Repository – COMPLETED, NO ISSUES

While capturing the Microsoft Access Exported XML, can not get the XML created for the MS Access database.

In SQL Developer, Tools > Migration > Microsoft Access Exporter > Run Microsoft Access 2007 Exporter
There is NO Run Microsoft Access 2010 Exporter, so you chose Run Microsoft Access 2007 Exporter. (Release 3.2.0.00.13).
Choose “Export for Oracle SQL Developer” > NEXT
Select the name of MDB files to export (This is a MS Access 2010 database saved as a .mdb.) > EXPORT
Get the Warning that it may take some time > OK
Get a security notice > clock CANCEL
Microsoft Access dialog box “The RunSQL action was canceled. You used a method of the DoCmd object to carry out an action in Visual Basic, but then clicked Cancel in a dialog box. For example, you used the Close method to close a changed form, then clicked Cancel in the dialog box that asks if you want to save the changes you made to the form.”

In another Dialog box you get the error, Error #2501 – XML Exporter – The RunSQL action was canceled. …. Database Schema Export did not complete successfully.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.