Home » RDBMS Server » Server Utilities » export dump (10.2.0.3, windows)
export dump [message #572117] Thu, 06 December 2012 03:47 Go to next message
ishika_20
Messages: 339
Registered: December 2006
Location: delhi
Senior Member
Dear All,

When i do run export command through command prompt, its shows below error.


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>Exp disdeva/disa123@distesta file=D:\DAI
LY_BACKUP\distesta.dmp log=D:\DAILY_BACKUP\distesta.log statistics=none buffer=5
000000 owner=distesta

Export: Release 10.2.0.3.0 - Production on Thu Dec 6 15:06:21 2012

Copyright (c) 1982, 2005, Oracle.  All rights reserved.


Connected to: Oracle Database 10g Release 10.2.0.3.0 - Production
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)

About to export specified users ...
EXP-00010: DISTESTA is not a valid username
Export terminated successfully with warnings.

C:\Documents and Settings\Administrator>



When i connect from sqlplus, it doesn't give any erro. What could be the reason?

SQL> conn disdeva/disa123@distesta
Connected.
SQL> 


Regards,
Ishika

Re: export dump [message #572119 is a reply to message #572117] Thu, 06 December 2012 03:52 Go to previous messageGo to next message
Littlefoot
Messages: 19636
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
EXP's "OWNER" parameter shouldn't be DISTESTA (it seems to be your database alias), I suppose, but ... I don't know, DISDEVA?
Re: export dump [message #572125 is a reply to message #572119] Thu, 06 December 2012 04:40 Go to previous messageGo to next message
ishika_20
Messages: 339
Registered: December 2006
Location: delhi
Senior Member
Thank you littlefoot.

you are correct.... Smile
Re: export dump [message #573013 is a reply to message #572125] Wed, 19 December 2012 16:30 Go to previous messageGo to next message
alan.kendall@nfl.com
Messages: 163
Registered: June 2012
Location: Culver City, California
Senior Member
Delhi,
In Unix run:
export NLS_LANG=AMERICAN_AMERICA.AL32UTF8
In MSDOS run:
set NLS_LANG=AMERICAN_AMERICA.AL32UTF8
to set the nls_lang prior to the export.
Re: export dump [message #573030 is a reply to message #573013] Thu, 20 December 2012 01:27 Go to previous messageGo to next message
Michel Cadot
Messages: 59170
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Question

What does this have to do with:

Quote:
EXP-00010: DISTESTA is not a valid username


Regards
Michel
Re: export dump [message #573094 is a reply to message #573030] Thu, 20 December 2012 13:18 Go to previous messageGo to next message
alan.kendall@nfl.com
Messages: 163
Registered: June 2012
Location: Culver City, California
Senior Member
I was responding to the following error which can change rows.
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)

Re: export dump [message #573096 is a reply to message #573094] Thu, 20 December 2012 13:58 Go to previous messageGo to next message
Michel Cadot
Messages: 59170
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Not an error, just an information, setting NLS_LANG to UTF8 just hide the "error".

Regards
Michel
Re: export dump [message #573103 is a reply to message #573096] Thu, 20 December 2012 15:35 Go to previous messageGo to next message
alan.kendall@nfl.com
Messages: 163
Registered: June 2012
Location: Culver City, California
Senior Member
On one database if I do not set NLS_LANG, the export Modified the rows and the rows were corrupted. The import worked but the rows had been modified and had to be re-exported and re-imported.
Re: export dump [message #573123 is a reply to message #573103] Fri, 21 December 2012 02:29 Go to previous message
Michel Cadot
Messages: 59170
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
the export Modified the rows and the rows were corrupted.


Not if you are in the character set your database which is ('or should be) most often the case.

Let's see what is said:

Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set

So you exported with an NLS_CHARACTERSET of WE8MSWIN1252 which is fine if your database is also in this character.

server uses AL32UTF8 character set (possible charset conversion)


And so, why do you care about code points? The only problem is if you (wrongly) let NLS_LENGTH_SEMANTICS to BYTE or create your VARCHAR2 field specifying the length is in BYTE.

Regards
Michel

Previous Topic: How to compare column name of a schema with other schema's column name
Next Topic: EXPDP on NFS error
Goto Forum:
  


Current Time: Tue Sep 23 01:23:05 CDT 2014

Total time taken to generate the page: 0.09801 seconds