Error during a full load while loading to snowflake from SQL server

[SaranyaK]

I get this error, I am not sure if this is space issue on the folder on the server or issues snowflake side. We made space on the server and rerunning but still same error.

replication task encountered the following error:

Handling new table 'Schema.'ORDER' failed Failed to create statement: 'SHOW SCHEMAS LIKE 'schema' IN DATABASE "LAKE_DEV" STARTS WITH 'schema' ;'

RetCode: SQL_ERROR  SqlState: HY000 NativeError: 4 Message: [Snowflake][Snowflake] (4)

      REST request for URL https://urldefense.com/v3/__https://xxxxx.xx-us-2.xxxx.snowflakecomputing.com:443/queries/v1/$  failed: CURLerror (curl_easy_perform() failed) - code=6 msg='Couldn't resolve host name' osCode=12 osMsg='Not enough space'.

[Steve_Nguyen]

@SaranyaK 

from the CURL error , something is strange :

https://urldefense.com/v3/

This section here, normally we do not see this URL , only the https:// then the snowflake url.

do you have proxy or something that need additional configuration ?

[SaranyaK]

Agreed, but this task data to many tables  just the few tables in the task fail every day with the above error, so I dont think the target snowflake url is entirely wrong,

[Steve_Nguyen]

thank you for additional information.

so if it working and fail on xx tables.

1. what is version of replicate? 

2. what is the version of Snowflake ODBC ?

3. how many table are in the task ? have to try to lower the number of tables to see if you still have issue ?

[Heinvandenheuvel]

>>> new table 'Schema.'ORDER' failed

1) Was that re-typed? There is a missing quote before the period in schema.table naming.

2) Is the schema name really 'Schema', or is that a way to disguise the real schema name. If it is real, then I'd urge you to pick a more unique name, more telling name, or even 'my_schema' just not the naked word schema as that will byte someone someday as a reserved word or in searches gone wild.  If it is a substitute then you might want to make that more clear using something like '<schema>'. Also, I'm not a big fan of mixed can object names preferring the database native convention (which you get by NOT using quotes.  For example from the Snowflake documentation "STARTS WITH 'name_string' Optionally filters the command output based on the characters that appear at the beginning of the object name. The string must be enclosed in single quotes and is case-sensitive. ". On the same page "LIKE 'pattern'Filters the command output by object name. The filter uses case-insensitive pattern matching," (https://docs.snowflake.com/en/sql-reference/sql/show-schemas.html)

I'm sure " https://urldefense.com" has its place in web access security but IMHO it has no place in server-to-server link. Its purpose is to protect human behavior, not servers, best I can tell.

Is that "REST request for " part of the "SqlState: HY000 NativeError: 4" message? The formatting in the topic is confusing.  

"Couldn't resolve host name" that sounds rather fundamental and network related.

fwiw,

Hein

[SaranyaK]

Thank you for these pointers. We upgraded the Snowlfake driver to latest version and that fixed the issue

[SaranyaK]

Thank you  Heinvandenheuvel, for your response!! The schema name was just to disguise the actual schema name.