MetaData Mismatch - NLS problem?
Posted: Fri Mar 21, 2008 12:03 pm
We have an Oracle database that was recently moved from AIX/Oracle to RedHat/Oracle. The DataStage server jobs that connect to it via ODBC are now producing warnings on some fields:
Message: ThisIsMyJobName..ODBCTables.InsJobRunLog: DSD.BCIOpenW results of SQLColAttributes(USERID) gave MetaData mismatch
COLUMN.TYPE Expected = Char Actual =
When I use DataStage Manager to import the new database's metadata, I noticed that the offending fields are SQL type "NCHAR". On the old database, they came up as "CHAR".
I talked to my DBA and he said that the only difference is that on the old (working) database had NLS_CHARACTERSET = US7ASCII and the new one had NLS_CHARACTERSET = AL32UTF8.
Could this be the problem? The DBA is trying to figure out how to switch back to US7ASCII on the new database so we can test this theory. (Side note: We do not have NLS installed in DataStage.)
Message: ThisIsMyJobName..ODBCTables.InsJobRunLog: DSD.BCIOpenW results of SQLColAttributes(USERID) gave MetaData mismatch
COLUMN.TYPE Expected = Char Actual =
When I use DataStage Manager to import the new database's metadata, I noticed that the offending fields are SQL type "NCHAR". On the old database, they came up as "CHAR".
I talked to my DBA and he said that the only difference is that on the old (working) database had NLS_CHARACTERSET = US7ASCII and the new one had NLS_CHARACTERSET = AL32UTF8.
Could this be the problem? The DBA is trying to figure out how to switch back to US7ASCII on the new database so we can test this theory. (Side note: We do not have NLS installed in DataStage.)