Hi Rick, What happens if you add the –connection-manager as well? Regards, Robert ...
What happens if you add the –connection-manager as well?
In the 2.0 Sandbox, we are getting an error attempting to execute a sqoop incremental import using the lastmodified parameter when pulling data from SQL Server. The same command works fine using the append parameter.
13/10/02 11:56:55 WARN manager.SqlManager: SQL exception accessing current timestamp: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near ‘)’.
13/10/02 11:56:55 ERROR tool.ImportTool: Encountered IOException running import job: java.io.IOException: Could not get current time from database
Here is the command which was issued:
[root@sandbox ~]# sqoop import –connect “jdbc:sqlserver://00.00.00.00:14433;database=xxxxxx” –username xxxxx –password xxxxxx –driver com.microsoft.sqlserver.jdbc.SQLServerDriver –table “dbo.xxxxxx” –target-dir “xxxxxxx” –incremental “lastmodified” –check-column “LAST_UPD” –last-value “2013-09-20 04:02:03″ –split-by ROW_ID –m 1
Log also included this statement:
13/10/02 11:56:46 WARN sqoop.ConnFactory: Parameter –driver is set to an explicit driver however appropriate connection manager is not being set (via –connection-manager). Sqoop is going to fall back to org.apache.sqoop.manager.GenericJdbcManager. Please specify explicitly which connection manager should be used next time.
Is there a way around this error?
The topic ‘Sqoop Incremental import failing pulling data from SQL Server’ is closed to new replies.