Solving Convertible Data [message #397686] |
Mon, 13 April 2009 06:47 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
rtnataraj
Messages: 102 Registered: December 2008
|
Senior Member |
![rtnataraj@gmail.com](/forum/theme/orafaq/images/google.png)
|
|
ROWID Exception Type Size Cell Data(first 30 bytes)
------------------ ------------------ ----- ------------------------------
AAAMwvAAFAAAq5EAA0 convertible FLATTS
AAAMwvAAFAAAq5EAA2 convertible KADOWAKI
AAAMwvAAFAAAq5EAA3 convertible LADOUCEC
AAAMwvAAFAAAq5EAA9 convertible PEARCETH
AAAMwvAAFAAAq5EAAy convertible DEBLOIS
AAAMwvAAFAAAq5EABA convertible RAWJI
------------------ ------------------ ----- ------------------------------
This is the CSScan output of my database instance.
I want the above six datas to be converted from WE8ISO8859P1 to UTF8 charecterset.
All the above 6 datas have a space ' ' like charecter (i'm not sure) at the end,
kindly help me.
[Updated on: Mon, 13 April 2009 07:21] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Solving Convertible Data [message #397725 is a reply to message #397720] |
Mon, 13 April 2009 09:37 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
![](/forum/images/custom_avatars/102589.gif) |
Michel Cadot
Messages: 68734 Registered: March 2007 Location: Saint-Maur, France, https...
|
Senior Member Account Moderator |
|
|
Quote: | what will happen to the above six datas which were not able to convert to the destination charecterset
|
This is NOT what csscan says. It says "convertible".
Quote: | can you give me the command to export specific rows from a table?
|
C:\>exp help=y
Export: Release 10.2.0.4.0 - Production on Lun. Avr. 13 16:35:38 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
You can let Export prompt you for parameters by entering the EXP
command followed by your username/password:
Example: EXP SCOTT/TIGER
Or, you can control how Export runs by entering the EXP command followed
by various arguments. To specify parameters, you use keywords:
Format: EXP KEYWORD=value or KEYWORD=(value1,value2,...,valueN)
Example: EXP SCOTT/TIGER GRANTS=Y TABLES=(EMP,DEPT,MGR)
or TABLES=(T1:P1,T1:P2), if T1 is partitioned table
USERID must be the first parameter on the command line.
Keyword Description (Default) Keyword Description (Default)
--------------------------------------------------------------------------
USERID username/password FULL export entire file (N)
BUFFER size of data buffer OWNER list of owner usernames
FILE output files (EXPDAT.DMP) TABLES list of table names
COMPRESS import into one extent (Y) RECORDLENGTH length of IO record
GRANTS export grants (Y) INCTYPE incremental export type
INDEXES export indexes (Y) RECORD track incr. export (Y)
DIRECT direct path (N) TRIGGERS export triggers (Y)
LOG log file of screen output STATISTICS analyze objects (ESTIMATE)
ROWS export data rows (Y) PARFILE parameter filename
CONSISTENT cross-table consistency(N) CONSTRAINTS export constraints (Y)
OBJECT_CONSISTENT transaction set to read only during object export (N)
FEEDBACK display progress every x rows (0)
FILESIZE maximum size of each dump file
FLASHBACK_SCN SCN used to set session snapshot back to
FLASHBACK_TIME time used to get the SCN closest to the specified time
QUERY select clause used to export a subset of a table
RESUMABLE suspend when a space related error is encountered(N)
RESUMABLE_NAME text string used to identify resumable statement
RESUMABLE_TIMEOUT wait time for RESUMABLE
TTS_FULL_CHECK perform full or partial dependency check for TTS
TABLESPACES list of tablespaces to export
TRANSPORT_TABLESPACE export transportable tablespace metadata (N)
TEMPLATE template name which invokes iAS mode export
Export terminated successfully without warnings.
See QUERY parameter.
Regards
Michel
|
|
|
|
|
|
|
|
Re: Solving Convertible Data [message #397824 is a reply to message #397820] |
Tue, 14 April 2009 01:23 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
babuknb
Messages: 1736 Registered: December 2005 Location: NJ
|
Senior Member |
![babu.knb@gmail.com](/forum/theme/orafaq/images/google.png) ![babudba](/forum/theme/orafaq/images/skype.png)
|
|
Hello,
If you have any problem with your data. First you need to fix later use export/import. Othrewise you will get error.
Try to post your source database characterset.
Try to post your csscan logfile (with your command.)
Post your DDL Tables
Post few records (sample records)
Babu
[Updated on: Tue, 14 April 2009 01:25] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Solving Convertible Data [message #397887 is a reply to message #397882] |
Tue, 14 April 2009 07:38 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
rtnataraj
Messages: 102 Registered: December 2008
|
Senior Member |
![rtnataraj@gmail.com](/forum/theme/orafaq/images/google.png)
|
|
Babu,
The scope of my conversion is limited to the tables and columns datas given in the output file.
Quote: | But sometime your data type length diff.
|
"exceed column size" will be the exception when we have data that needs length to be extended.
But the output file has all of the CONVERTIBLE datas, mostly from System objects and some from Application object.
We can use export for only few tables but what about the rest?
Do you have any suggestions on how to solve these CONVERTIBLE datas of Data Dictionary from the DB?
[Updated on: Tue, 14 April 2009 08:00] Report message to a moderator
|
|
|
|
|
Re: Solving Convertible Data [message #397958 is a reply to message #397937] |
Tue, 14 April 2009 12:32 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
andrew again
Messages: 2577 Registered: March 2000
|
Senior Member |
|
|
1) Oracle characterset WE8ISO8859P1 means Western European 8 bit ISO 8859 point 1. (ISO 8859-1) also commonly called ISO-1.
2) UTF-8 is an encoding scheme for Unicode, there are several others.
3) In the days of Oracle 8 (from what I recall), there was an Oracle characterset called UTF8. This characterset had an error (from what I recall) so it was superceded by AL32UTF8. You should probably be looking at AL32UTF8 for a database characterset rather than UTF8.
Unicode is a superset of all other charactersets, so that means that any (valid) character in WE8ISO8859P1 can be converted to AL32UTF8. Having incorrect NLS_LANG client settings is a common cause of invalid characters being stored into databases.
|
|
|
|
|
|
|
|
|