export dump [message #572117] |
Thu, 06 December 2012 03:47 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
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 #573123 is a reply to message #573103] |
Fri, 21 December 2012 02:29 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) |
![](http://www.orafaq.com/forum/images/custom_avatars/102589.gif) |
Michel Cadot
Messages: 68675 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
|
|
|