Re: Import from compressed dump failing because of long columns

"James Keane" <jim_keane_at_yahoo.com> wrote in message news:b16d7020.0212021046.18b14db2_at_posting.google.com...
> I am trying to restore from backup after a severe database disk crash,
> but am failing on the largest table (& most important, of course) in
> the backup. The error is
>
> IMP-00020: long column too large for column buffer size (100)
>
> Per the newsgroups I have already upped the buffer size and record
> size, but to no avail. I cannot go back and create another backup as
> the old database is now toast.
>
> This backup was created using a "pipe" through gzip. I am using the
> reverse to import it, and have been able to partial restores before,
> but never full restores.
>
> The syntax I'm using to import this table is :
>
> mknod PIPE.dmp p
> gunzip -c < PRD2ORA_11242002.dmp.gz > PIPE.dmp &
> imp userid=system/manager TABLES=(DM_LU_SITEMAP_T) BUFFER=1024000
> RECORDLENGTH=64000 file=PIPE.dmp log=PIPE.log
>
> FYI, the original full backup was created using the syntax:
>
> gzip < PIPE.dmp > PRD2ORA_$DUMP_DATE.dmp.gz &
> exp userid=system/manager direct=y full=y feedback=10000
> file=PIPE.dmp
>
> As this is a production database we are in quite a bind here. Anything
> you can suggest would be much appreciated.
>
> Cheers,
> James

A 1M buffer is definitely nothing. Use at least 8M Please do not crosspost to all groups you can spell.

--
Sybrand Bakker
Senior Oracle DBA

to reply remove '-verwijderdit' from my e-mail address