11gR2 mappings to SQLServer via gateway

Question

Hi all,
we are evaluating the dataloading from SQLServer 2005 either via code template or via gateway (both cost a fortune in licences). The code template runs well but I don't know how to pass a dynamic filter criterion (e.g. a date) derived from the Oracle database. So there is a preference for the gateway but when validating a traditional mapping with a source table from a gateway module I'm getting the following message:
VLD-1151: Operator CALLDETAIL is bound to an object contained in native heterogeneous module SQLSERVER_LOCATION.
The detailed explanation (unfortunately it's not possible to copy it here) says that Oracle objects cannot directly access objects residing in native HS modules. I should use a template mapping. What does this mean? Does OWB enforce the use of code templates although there is a more efficient way which worked well until now? Or do I miss a configuration step?
I need a simple "insert into <locale table> select ... from <sqlserver table>@<gateway DB link>". How to achieve this via OWB.
regards
Thomas

Answer 1

Hi David,
the source tables are stored in a module under the Database/SQL-Server node which can have a location either of type "Native Database Connection" or "SQL Server Gateway". I created both types in order to test the CT implementation with the native location and the gateway implementation with the gateway location. Both cannot be accessed by Oracle. But the native location works for the CT implementation. But when using the tables from the gateway location (with whichever LCT) I get on validation:
VLD-1339: The source location of execution unit SQL_SERVER_GATEWAY_LOC_EU cannot be determined.
The source operator(s) in this execution unit may not have a valid location (such as a constant operator), or the source operator(s) are not bound to location(s) that can be accessed using JDBC (such as a table operator bound to a SAP system).
What do you mean with "+if you are building a traditional mapping that uses gateways, the module must be Oracle accessed/typed (Oracle or Oracle Database Gateway+"? This is an insolvable requirement for the source module as I described below.
1. We don't want to use a CT mapping for a gateway access. My client want to pay just one of the expensive licenses. And it worked in former releases without CT.
2. Effectively, I don't get it running neither in the traditional mapping nor in the CT mapping.
3. I want an ordinary INSERT statement generated. If OWB cannot do the job I must workaround it with a hardcoded procedure. It seems that OWB wants to force the users to implement CT's where it wasn't necessary until now.
some more ideas?
best regards
Thomas