Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Conversion problems with Memo field in Access database

307991Aug 2 2002
I have the latest version of Migration Workbench and the Access 2000 plug-in.
I am using an ODBC driver, and the SQL conversion requirements for converting
to a native driver seem too time and labor intensive to be feasable.

My problem is that I have some "Memo" columns in my Access database containing
over 200,000 rows that I need converted to Oracle. This is something I'm going
to need to do over-and-over again for different Access databases.

I gave up on mapping the Access "Memo" datatypes to Oracle "Clob" datatypes. It
was either taking forever or taking WAY too long.

Then I tried mapping the Access "Memo" datatypes to "Varchar2(4000)" and although
it completed it took longer than my customer will like (think 1/2 an hour just for
all the rows of one memo column in one table).

Finally I tried going into the original Access database and converting the "Memo"
column into a "Text" column. It wouldn't work, I kept getting the error:
=====
Microsoft Access can't change the data type.
There isn't enough disk space or memory.
=====
even though I had over 10GB of free disk space and only 1/3 of my memory was being
used. I assume this is a memory-max limitation in Access 2000.

Any suggestions for speeding the conversion? Could I stagger using Migration workbench
to create the tables. . .then use SQL*Loader to load the data. . .then use Migration
workbench again to put in the idexes, etc? Would this be faster even if it worked?

Thanks,

Aaron Chawla
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 30 2002
Added on Aug 2 2002
0 comments
360 views