|
-
 Originally Posted by PAVB
You might want to check Metalink Note:119119.1
A workaround -if permitted by application, is to pre-create affected tables in Target database giving offending columns a larger size. In this case don't forget to use skip=y during Import.
Thanks PAVB.
That will help.
-D
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|