By the way is your ARCHIVE_LOG problem solved ?
I'm interested in the solution you find
Frederic DEBRUS <frederic.debrus_at_ces-cdr.be> wrote in article
<01bf0447$97b25860$3e35a99e_at_gal159a>...
> # oerr imp 37
> 00037, 00000, "Character set marker unknown"
> // *Cause: export file is corrupted.
> // *Action:
>
> Your export file is corrupted
> I guess you have used ftp to transfer the file, in this case remember to
> set transfer mode to binary
>
>
>
> Brian Howard <bh_at_creditwatch-inc.com> wrote in article
> <37E79ACE.FA09D35F_at_creditwatch-inc.com>...
> > I had done a full export from oracle 7.0 A/UX into a file named
> > 'gte.exp'. I then moved the file to different server with an identical
> > database on it and attempted to import it. When I do a:
> > imp quanaya/qt1234 file=/users/oracle/exports/gte.exp full=Y commit=Y
> > buffer=64000
> > I get the following:
> >
> > IMP-00037: Character set marker unknown
> > IMP-00021: operating system error - error code (dec 2, hex 0x2)
> > IMP-00000: Import terminated unsuccessfully
> >
> > Does anyone know how I can fix this to import this file? I have no clue
> > what the problem is and can't find any documentation. If I do a unix
> > file command on a known working export file I get the following:
> > ascii text
> > but if I do the same on this file I get
> > Apple-single format resource file
> >
> > Could this be the problem? If so, how do I fix?
> >
> >
> >
>
Received on Tue Sep 21 1999 - 10:53:01 CDT
