Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Sqoop, mail # user - import-all-tables fails with exception 'Invalid object name' on non dbo schemas


Copy link to this message
-
Re: import-all-tables fails with exception 'Invalid object name' on non dbo schemas
Jarek Jarcec Cecho 2013-10-31, 16:42
Hi Christos,
this is the log I was looking for :-)

> 13/10/31 16:47:48 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.

Would you mind trying the command without --driver option as the WARNING is suggesting? You might find more background why using --driver option is not desirable in most cases in our blog post [1].

Jarcec

Links:
1: https://blogs.apache.org/sqoop/entry/connectors_and_drivers_in_the

On Thu, Oct 31, 2013 at 03:54:21PM +0000, Kallinteris, Christos wrote:
> Hello Jarcec,
>
> Here is the command and the response I get on the console. Where would I find the log for sqoop? There is no corresponding directory under /var/log.
>
> Thank you very much!
>
> Christos
>
> --
> ck@SVR-HDP01:~$ sqoop import-all-tables --connect "jdbc:sqlserver://192.168.207.194\\SQL2008R2;user=sqoop;password=password;databasename=DWH_BSP;" --driver com.microsoft.sqlserver.jdbc.SQLServerDriver --username sqoop --password password  --hive-import --verbose
> Warning: /usr/lib/hcatalog does not exist! HCatalog jobs will fail.
> Please set $HCAT_HOME to the root of your HCatalog installation.
> 13/10/31 16:47:48 DEBUG tool.BaseSqoopTool: Enabled debug logging.
> 13/10/31 16:47:48 WARN tool.BaseSqoopTool: Setting your password on the command-line is insecure. Consider using -P instead.
> 13/10/31 16:47:48 INFO tool.BaseSqoopTool: Using Hive-specific delimiters for output. You can override
> 13/10/31 16:47:48 INFO tool.BaseSqoopTool: delimiters with --fields-terminated-by, etc.
> 13/10/31 16:47:48 DEBUG sqoop.ConnFactory: Loaded manager factory: com.cloudera.sqoop.manager.DefaultManagerFactory
> 13/10/31 16:47:48 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.
> 13/10/31 16:47:48 INFO manager.SqlManager: Using default fetchSize of 1000
> 13/10/31 16:47:49 DEBUG manager.SqlManager: No connection paramenters specified. Using regular API for making connection.
> 13/10/31 16:47:50 INFO tool.CodeGenTool: Beginning code generation
> 13/10/31 16:47:50 DEBUG manager.SqlManager: Execute getColumnTypesRawQuery : SELECT t.* FROM tblAdresse AS t WHERE 1=0
> 13/10/31 16:47:50 DEBUG manager.SqlManager: Using fetchSize for next query: 1000
> 13/10/31 16:47:50 INFO manager.SqlManager: Executing SQL statement: SELECT t.* FROM tblAdresse AS t WHERE 1=0
> 13/10/31 16:47:50 ERROR manager.SqlManager: Error executing statement: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'tblAdresse'.
> com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'tblAdresse'.
>         at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
>         at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)
>         at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:404)
>         at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
>         at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
>         at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
>         at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
>         at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
>         at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)