IKM MSSQL Incremental Update fails on SQL Server 2000 - Collation Problem

Question

I am having a problem where the the incremental update isn't cabable of updating the table it creates.
In the Flag Rows to Update I get the following error message:
446 : HY000 : java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Cannot resolve collation conflict for equal to operation.
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Cannot resolve collation conflict for equal to operation.
Source Code is:
update     S
set     IND_UPDATE = 'U'
from     SQRoracleStage..I$_tblOracleStage      S,     
     SQRoracleStage..tblOracleStage      T
where     T.Occurance     = S.Occurance
and     T.PlanName     = S.PlanName
Oracle has suggested that the IKM be updated to include a COLLATE clause following the column name in the where clause.
update S
set IND_UPDATE = 'U'
from <%=snpRef.getTable("L", "INT_NAME", "A")%> S,
<%=snpRef.getTable("L", "TARG_NAME", "A")%> T
where <%=snpRef.getColList("", "T.[COL_NAME]\t= S.[COL_NAME] COLLATE replace_with_server_collation_string", "\nand\t", "", "UK")%>
However this code doesn't retrieve the collation string, but rather expects you to replace the replace_with_server_collation_sting with the value from the server.
Being unfamiliar with SQL Server I would have expected that the model should be capable of determining this value, and that the code should look something similar to:
update S
set IND_UPDATE = 'U'
from <%=snpRef.getTable("L", "INT_NAME", "A")%> S,
<%=snpRef.getTable("L", "TARG_NAME", "A")%> T
where <%=snpRef.getColList("", "T.[COL_NAME]\t= S.[COL_NAME] COLLATE <%=snpRef.getServerCollationString("L", "TARG_NAME", "A")%> ", "\nand\t", "", "UK")%>
It seems as though since ODI creates the table dynamically it should be capable of doing an update to it without intervention.
Has anyone found a work around for this issue?

Answer 1

I found the error :)
This is what happened:
I copied the tables from the MS SQL Server model to my Oracle model and then generated the DDL, so this gave me a quick set of tables in Oracle identical to the MS SQL database. But what I didn't know was that with the reverse engineer from MS SQL the ODI tool set the primary key columns to READ ONLY (and thus my copied tables also had read only primary key columns). Read only is OK for a source table but devastating for my tables I must load. So when I removed the read only indicator from the Oracle target table pk columns I was again a happy camper !
Thanks for being the one to talk to ! That really helped :)