SYS.SOURCE$ marked as having Convertible or Lossy data in Csscan output
(Doc ID 291858.1)
Last updated on FEBRUARY 02, 2022
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Purpose
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample or bulit-in schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
To document on how to handle "Convertible" or "Lossy" in the SOURCE column of SYS.SOURCE$ listed in Csscan output
Scope
You are planning to convert the database character set from one character set to an other (for example to UTF8 or AL32UTF8). If you use csscan you might find that the column SOURCE in the table SYS.SOURCE$ is marked as containing CONVERTIBLE or LOSSY data.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Scope |
| Details |
| 1) An Example: |
| 2) Full steps to get the affected objects and it's source |
| 3) Solving the Convertible or Lossy |
| 4) After going to the new characterset |
| References |