This content has been marked as final. Show 3 replies
933746 wrote:It's the "WRH$_SQLTEXT" table who has 3 CLOB's that I can't convert.
We're migrating databases from HP-UX to a new server and we're at the same time changing the character set of databases not running UTF8.
I executed csscan to check conversion from our existing database 10.2.0.5 with ISO character set to new database on a new server with 18.104.22.168 and UTF8.
In the csscan report I get information about 3 lossy CLOB characters in the data dictionary.
My question is this:
Could the lossy in my data dictionary create any problems when migrating as described above and using schema import into new database with datapump?
I did find a "solution" for it by dropping dropping tuning sets/baselines/snapshots
Solving Convertible or Lossy data in Data Dictionary objects reported by Csscan when changing the NLS_CHARACTERSET [ID 258904.1]
I would guess that this is not something I have to do as I'm not exporting these data?