This content has been marked as final. Show 1 reply
*## After running csscan and csalter*
Did you really run csalter.plb? csalter.plb should not be run before a full-export A-to-B type of migration. On the other hand, if there were convertible data in the database, csalter.plb should have just reported an error and terminate without changing anything.
*## "[Oracle][ODBC]Syntax error or access violation"*
This error does not say much. Why do you think ODBC does no conversion?
The conversion for the ODBC driver is performed by OCI to/from UTF-16 and it is independent of the NLS_LANG character set. If the C++ application is written in the ANSI mode (does not use wide character data types), Microsoft ODBC Manager will convert between the application and the Oracle ODBC driver, between system code page (Cp 1252) and UTF-16.