import½Ã ¸ØÃá´Ù¸é (long typeÁ¸Àç½Ã-Imp-00020 ¿¡·¯)
ÀÛ¼ºÀÚ °ü¸®ÀÚ ÀÛ¼º½Ã°£ 2004-05-26 14:53:21
 

Imp-00020 ¿¡·¯

1. Imp-00020 Error when Oracle 7.3.4.5 --> 7.3.2.2

2. IMP-00020 Long column too large for column buffer size (1)

IMP-00020 when attempting to import in user mode (exported direct=y), from one schema to another. The problem seems similar to others posted, and I can recreate it consistently. It occurs on both our test and prod 8.1.7 instances (prod is an E10K domain, test is a 450, both same OS).

Two of the four tables listed below will error consistently, the other two may or may not error, depending on whether the import is by user only or by explicitly specifying tables (as below). Row counts are 19, 25, 18, and 0 for the four, respectively (prod counts much higher, up to 259K+ for the 1st and 3rd tables).

Export parms:

DIRECT=Y

FULL=N

TABLES=(BROWSERSTAGE,BROWSER_0_A,BROWSER_0_B,BROWSER_INS_0_B)

ROWS=Y

GRANTS=Y

COMPRESS=N

RECORDLENGTH=65536

BUFFER=20480000


Import parms:

FROMUSER=EPIMART

TOUSER=TESTMART

ROWS=Y

DESTROY=N

IGNORE=N

BUFFER=20480000

RECORDLENGTH=65536

Have tried buffer parms from below 2M up to 20M. When using a conventional export (direct=n), the problem does not occur. I have tried various combinations of buffer/recordlength parms with no success. My issue is that a conventional export is much slower (our direct exports already take 5 hours), so using conventional is not really an option for us.


The data in these tables (up to four have had the problem) may contain brackets, braces, other unusual chars in some columns, though I have had problems even with the 0 row table. I don't think any corruption is occurring in the dmp file.

Is there a fix or workaround for this problem that allows direct export?


¸ñ·Ï | ÀÔ·Â | ¼öÁ¤ | ´äº¯ | »èÁ¦