Re: export problems

If none of the other suggestions works, try doing the export using the executable on the UNIX machine (I know that's not what you want to do) and the import on the NT machine. That will eliminate any incompatibilities, if there are any, between the two export versions on UNIX and NT. Going from ASCII7 to Western European should not be a problem - it just takes awhile. Also, I can't remember if 7.3.4 handles Unicode but if it does you might look into that instead of WE...

Van

"Howard J. Rogers" <howardjr_at_www.com> wrote in message news:3aaa9bcc$1_at_news.iprimus.com.au...
>
> "Rocr" <rolland.cright_at_pwgsc.gc.ca> wrote in message
> news:98djk5$qac1_at_shark.ncr.pwgsc.gc.ca...
> > Hi all,
> >
> > I am attempting to export an Oracle 7.3.4 database from a Unix
 environment
> > into a 734 database on a WINNT environment. I am trying to run the
 export
> > in a dos shell on the windows box.
> >
> > This is the error I get:
> >
> > Connected to: Oracle7 Server Release 7.3.4.1.0 - Production
> > With the distributed, replication and parallel query options
> >
> > PL/SQL Release 2.3.4.1.0 - Production
> > EXP-00023: must be a DBA to do Full Database export
> > (2)U(sers), or (3)T(ables): (2)U > 2
> > EXP-00041: Export done in server's US7ASCII, different from user's
 character
> > set
> > WE8ISO8859P1
> > EXP-00000: Export terminated unsuccessfully
> > D:\dumps>svrmgr23
> >
> > I can export the file succesfully from the unix box then ftp it to the
 winnt
> > box. The problem is that I am having problems with the import. I would
> > like to do a full import because the database has several schemas. The
> > problem with the full import is that the users will not be created and
> > therefore their objects will not as well. I have done this sort of
 thing
> > before as long as I run the export from the intended target. Any ideas
 how
> > to change the character set so that this(the error above) will not
 occur.
> >
> >
>
> The only time I've seen export fail with a character set issue, it was set
> to direct path exports (which require no character set conversions).
> Therefore, a quick fix might be to make sure that whatever it is that you
> are using to fire up export (which, unfortunately -and a bit unhelpfully-
> did not show us here) does not include the 'direct=y' parameter.
>
> Export should then gracefully convert between the two character sets
> mentioned, automatically.
>
> Your export will then, of course, take an age to complete. In which case
> you need to change your client's character set to be US7ASCII. That can
 be
> done, IIRC, with an alter session command, and is well-documented (which
 is
> code language for 'I can't remember it off the top of my head, but it's
> readily found at technet, for example').
>
> Regards
> HJR
>
>
>
>
>
>
>
Received on Sat Mar 10 2001 - 18:35:05 CST