978005 wrote:Pl detail how exactly you "changed varchar2 to Nvarchar and long to NCLOB on mismatched columns and load the data".
We were changed varchar2 to Nvarchar and long to NCLOB on mismatched columns and load the data. After the data load we have manually compared the data between source and target by csv comparision through beyond compare, there is no mismatch identified.
Here the actual requirment is we need some proper comparision method to proof the customer there is no mismatch on the mismatch tables between source and target.As far as I know, you cannot compare data between two datatypes, just like you cannot compare apples to oranges.
Now the source(VARCHAR2) and target (NVARCHAR2) has different datatype. We need a data comparision methods which will support different datatype and differen characterset. Please let me know if you have and idea on this.
We can't modified the character set to AL32UTF8, because the target is form database, we are import our schemas into the forms. If we change the character set it will affect other application schemas which is running in the same database.Pl detail out exactly why AL32UTF8 cannot be used - have you actually tried it ? What errors do you get ?