| Bug #27740 | mtk has problems with exporting blobs larger than 4 mb from oracle | ||
|---|---|---|---|
| Submitted: | 10 Apr 2007 21:56 | Modified: | 8 Jun 2007 6:47 |
| Reporter: | Oli Sennhauser | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Migration Toolkit | Severity: | S2 (Serious) |
| Version: | 1.1.8rc | OS: | Linux (for rh-64 bit) |
| Assigned to: | CPU Architecture: | Any | |
[11 Apr 2007 4:08]
Valeriy Kravchuk
Thank you for a bug report. Please, try to repeat with a newer version, 1.1.11, and inform about the results. This problem was solved long time ago in Windows version, so I want to check if the fix is already included in newer Linux one.
[23 Apr 2007 9:50]
Oli Sennhauser
We were not able to make the linux version run in a reasonable amount of time. So we worked around the problem.
[8 May 2007 6:47]
Valeriy Kravchuk
Please, check with 1.1.11 when you'll have time for that.
[8 Jun 2007 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[22 Nov 2007 12:15]
saurabh sharma
I am getting the same error msg On windows xp with mtk 1.1.12 version. ERROR: The following error occured while transfering binary data from ATTACH_DATA, column THEDATA BLOB is larger than 4MB.
Description: When migrating from oracle to mysql we got the following errors: Getting the number of rows of table DATA_OBJECT SELECT count(*) AS total_num FROM "FBV1"."DATA_OBJECT" Transfering data from table DATA_OBJECT (2486/2486 rows) SELECT "ID", "CID", "DAT_", "CONTENT_OBJECT_OID", "CONTENT_OBJECT_CID", "IMAGE_CONTENT_OBJECT_OID", "IMAGE_CONTENT_OBJECT_CID", "LOCKID" FROM "FBV1"."DATA_OBJECT" Open source resultset. Started row transfer 100 rows transfered. ERROR: The following error occured while transfering binary data from DATA_OBJECT, column DAT_ BLOB is larger than 4MB. 200 rows transfered. this error occured several times (6 times) at the end possibly 500 rows were missing on this table. How to repeat: is reproducible with our data Suggested fix: should be configurable or accept more than 4 mb of blob. should list exactly which and how many rows are missing.