Messages and limitations of the Snowflake connector
Message code list of SNOWFLAKE category
The following message codes correspond to errors that occur in Snowflake Connector.
This message code is output when an undefined error occurs.
Cause |
Solution |
---|---|
An undefined error occurred. |
Check the error message or the help of the operation in which the error has occurred. |
Corresponding error
-
None
This message code corresponds to errors that occur during database processing.
Cause |
Solution |
---|---|
The cause differs according to each error message. |
Check the error message and perform the following:
|
Corresponding error
-
java.sql.SQLException
-
net.snowflake.client.jdbc.SnowflakeSQLException
Exception messages of SNOWFLAKE category
Exception name |
Cause |
Solution |
---|---|---|
net.snowflake.client.jdbc.SnowflakeSQLException: JDBC driver encountered communication error. Message: HTTP status=403. |
Can't connect to the database. |
Check the host name in the connection resource. |
net.snowflake.client.jdbc.SnowflakeSQLException: Incorrect username or password was specified. |
The user name or the password is incorrect. |
Check the user name and password for the connection resource. |
net.snowflake.client.jdbc.SnowflakeSQLException: SQL compilation error: syntax error at position unexpected "<table name>". |
Table name is incorrect. |
Check the table name specified in Table name. |
net.snowflake.client.jdbc.SnowflakeSQLException: SQL compilation error: Object "<table name>" does not exist or not authorized. |
The table doesn't exist. |
Specify an existing table in Table name. |
net.snowflake.client.jdbc.SnowflakeSQLException: SQL compilation error: Object "<table name>" does not exist or not authorized. |
The user has no permission to read the table. |
Check the read permission for the table specified in Table name. |
Limitations of SNOWFLAKE category
This connector supports the following types.
Type name |
Support |
---|---|
NUMBER |
Yes |
DECIMAL |
Yes |
NUMERIC |
Yes |
INT |
Yes |
INTEGER |
Yes |
BIGINT |
Yes |
SMALLINT |
Yes |
TINYINT |
Yes |
BYTEINT |
Yes |
FLOAT(n) |
Limited |
DOUBLE |
Limited |
DOUBLE PRECISIO |
Limited |
REAL |
Limited |
VARCHAR |
Yes |
CHAR |
Limited |
CHARACTER |
Limited |
STRING |
Yes |
TEXT |
Yes |
BINARY |
Limited |
VARBINARY |
Limited |
BOOLEAN |
Yes |
DATE |
Yes |
TIME |
Yes |
DATETIME |
Yes |
TIMESTAMP |
Yes |
TIMESTAMP_LTZ |
Yes |
TIMESTAMP_NTZ |
Yes |
TIMESTAMP_TZ |
Yes |
VARIANT |
No |
OBJECT |
No |
ARRAY |
No |
GEOGRAPHY |
No |
GEOMETRY |
No |
Yes |
: |
Supported. |
Limited |
: |
Supported with limitations. |
No |
: |
Not supported. |
Specification limits
-
FLOAT, FLOAT4, FLOAT8, REAL, DOUBLE, and DOUBLE PRECISION are displayed as FLOAT even if they're saved as DOUBLE.
-
When the table name is enclosed with quotation marks, it's case-sensitive.
-
When the table name includes multi-byte characters, it must be enclosed with quotation marks.
-
The default value for the fetch size is 500.
Specification limits
-
FLOAT, FLOAT4, FLOAT8, REAL, DOUBLE, and DOUBLE PRECISION are displayed as FLOAT even if they're saved as DOUBLE.
-
The default value for the fetch size is 500.
Specification limits
-
FLOAT, FLOAT4, FLOAT8, REAL, DOUBLE, and DOUBLE PRECISION are displayed as FLOAT even if they're saved as DOUBLE.
-
When the table name is enclosed with quotation marks, it's case-sensitive.
-
When the table name includes multi-byte characters, it must be enclosed with quotation marks.
Specification limits
-
FLOAT, FLOAT4, FLOAT8, REAL, DOUBLE, and DOUBLE PRECISION are displayed as FLOAT even if they're saved as DOUBLE.
Specification limits
-
Tables which include "." in the schema name or the table name on the database can't be used.
-
Test execution may be failed if the data amount is huge.
-
The maximum record count shown in the Execution result tab is 100.
-
SQL statements can be re-edited only if the tables in the SQL statement exist.
Specification limits
-
Tables which include "." in the schema name or the table name on the database can't be used.
-
SQL statements can be re-edited only if the tables in the SQL statement exist.