Forum Discussion
Hello,
Here is what I try :
1/ With the “Create table if not present” option
Here is what I get :
Unable to create table: “yyy”.“xxx”
Resolution:
Please make sure the connection, table name, and schema are correct
Reason:
SQL [CREATE TABLE …
“CREATED_DTTM” TIMESTAMP DEFAULT SYSTIMESTAMP NOT NULL,
)
]; The name “SYSTIMESTAMP” is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) variables. Column names are not permitted.
So, the “Create table if not present” option does not work properly.
2/ Without the “Create table if not present” option
It works.
But as my select is not simple as “select * from Table”, I can not use “Oracle - Select” but “Oracle - Execute”.
I had “Oracle - Execute” => “Mapper” => “Generic JDBC - Insert” and I get the error “The conversion from UNKNOWN to UNKNOWN is unsupported.”
I change to “Oracle - Execute” => “Mapper” => “SQL Server - Insert” and it is … OK. :+1:
- mina5 years agoEmployee
Awesome. For the Timestamp issue, I found the answer in SQLServer Insert snap doc. It called out:
TIMESTAMP datatype in SQL Server is not supported. According to the Microsoft official document, "The timestamp syntax is deprecated.- Christophe5 years agoNew Contributor II
Yes. So in SnapLogic we should have “if source field type = Timestamp then SQL Server field type = DateTime”
(but I can manage it)
Thanks.- mina5 years agoEmployee
Good idea! Replace the Timestamp in the ddl returned to DateTime on a mapper.