Re: Import /Export Errors Coredump with fatal error

Massa Batheli wrote:
> There are two large tables(88G and 44G) that need exported /imported .
> Direct exports did it but during imports oracle error IMP-00009 popped
> up .
> Metalink advice --Use a buffer to work around it and that is when all
> my issues started.
>
> : fatal error 0
> ********** Internal heap ERROR 17113 addr=0x0 *********
>
> even when there was no buffer parameter which means it was set to 4096
> because this eror could be caused by very large buffers .
> Has anyone had this error before and how did you go around it
>
> Thanks a million for your time..

I take it they were referencing metalink Note:186588.1and Note:235831.1 (which say make it bigger or smaller - riiiight), which are during the export. If you are getting it during the imp, that is probably a bug like 4186247.

Are you using the RECORDLENGTH parameter? I've found best results with DIRECT=Y recordlength=65535 on the export on my production systems (hp-ux). I have a vague memory that the docs state the maximum is 64K, overstated by one byte, or something like that.

Always remember to show exact versions of Oracle and OS, and your exact command. Bug 3579567, for example, is an export bug in 9.2.0.5 with compressed tables that is fixed in 9.2.0.6. The workaround is to _not_ use direct. Simply searching meatlink for imp-0009 can get you a lot of information.

You can also tail the export file, you should see a couple of EXIT at the end.

See http://www.dbaoracle.net/readme-cdos.htm

jg

-- 
@home.com is bogus.
http://www.wickedlasers.com/sonar.php