Snowflake Operation Error Codes
Once you’ve run the SQL for the desired Snowflake identity operation (either identity resolution or RampID translation), if you do not receive a success message, you might receive one of the error messages shown in the table below. In some cases, the error message contains information that can help you correct the issue. In other cases, you can try running the operation again or contacting LiveRamp Support.
Note
Not all error messages apply to both operation types.
Each error code is prefixed with "100132 (P0000):".
Error Code | Error Text |
|---|---|
val__embedded-identity__metrics-table-needs-permissions | Error: LiveRamp does not have the correct permissions for the metrics table. Perform the procedure in the "Perform Initial Application Setup" section of the native app help documentation to grant select, insert, and update on the metrics table. |
val__embedded-identity__input-table-missing-target-column | Error: Input table does not contain the target column specified in the metadata table |
val__embedded-identity__input-table-column-name-contains-invalid-characters | Error: One or more input table column names contain spaces, tabs, or embedded newlines |
val__embedded-identity__input-table-target-column-has-collation | Error: One or more target columns has collations defined |
val__embedded-identity__input-table-rowcount-below-minimum | Error: Input table does not contain at least 100 unique rows |
Val__embedded-identity__input-table- needs-permissions | Error: LiveRamp does not have the appropriate permissions for the input table. Perform the procedure in the "Set Up Permissions" section of the help documentation to grant select on the input table. |
val__embedded-identity__input-table-empty | Error: Input table does not contain any data |
val__embedded-identity__meta-table-missing-config-column | Error: Metadata table does not contain a "config" column or that column is empty |
val__embedded-identity__meta-table-missing-limit-column | Error: Metadata table does not contain a "limit" column |
val__embedded-identity__meta-table-invalid-limit-column-value | Error: Metadata table "limit" column" does not contain an integer between 1 and 10 (inclusive) |
val__embedded-identity__meta-table-missing-target-column | Error: Metadata table does not contain a "target_column" column or the column is empty |
val__embedded-identity__meta-table-missing-target-columns | Error: Metadata table does not contain a "target_columns" column or the column is empty |
val__embedded-identity__meta-table-missing-execution-columns | Error: Metadata table does not contain an "execution_mode" column or an "execution_type" column, or one or both of those columns are empty |
val__embedded-identity__meta-table-missing-credentials | Error: Metadata table does not contain a "client_id" column or a "client_secret" column, or one or both of those columns are empty |
val__embedded-identity__meta-table-missing-target-domain-column | Error: Metadata table does not contain a "target_domain_column" column or that column is empty |
val__embedded-identity__meta-table-missing-target-type-column | Error: Metadata table does not contain a "target_type_column" column or that column is empty |
val__embedded-identity__meta-table-missing-target-columns-value | Error: Metadata table "target_columns" parameter is missing a column name value for "<TARGET_COLUMN_KEY>" |
val__embedded-identity__meta-table-config-has-mixed-types | Error: Metadata table "target_columns" parameter contains more than one type of identifier (PII, hashed emails, or MAIDs) |
val__embedded-identity__meta-table-missing-name-or-address | Error: Metadata table "target_columns" parameter does not contain either name or streetAddress (required when zipCode is provided) |
val__embedded-identity__meta-table-missing-zip | Error: Metadata table "target_columns" parameter does not contain a zipCode column (required when streetAddress is provided) |
val__embedded-identity__meta-table-missing-touchpoint | Error: Metadata table "target_columns" parameter does not contain at least one of zipCode, phone, or email |
val__embedded-identity__meta-table-target-columns-have-mixed-granularity | Error: Metadata table "target_columns" parameter cannot contain both a "name" column and individual name element columns, such as "firstName", "middleName", "lastName", or "generationalSuffix" |
val__embedded-identity__meta-table-target-columns-have-mixed-granularity | Error: Metadata table "target_columns" parameter cannot contain both a "streetAddress" column and individual street address element columns, such as "primaryNumber", "preDirectional", "street", "streetSuffix", "postDirectional", "unitDesignator", or "secondaryNumber" |
val__embedded-identity__meta-table-too-many-columns-for-parameter | Error: Metadata table "target_columns" parameter for "<FULL_PARAMETER_NAME>" has more than <SUB_PARAMETER_NAMES_SIZE> element(s) |
val__embedded-identity__meta-table-column-invalid-column-name | Error: Metadata table "target_columns" parameter cannot contain an invalid column name (such as a name containing special characters or longer than 254 characters) |
val__embedded-identity__meta-table-invalid-execution-type | Error: Metadata table "execution_type" provided is not a valid execution type |
val__embedded-identity__meta-table-config-invalid-column-type | Error: Metadata table "config" column data type is not "object" |
val__embedded-identity__meta-table-missing-deconfliction-config | Error: Metadata table "config" column does not contain a "deconflictionConfig" property |
val__embedded-identity__meta-table-invalid-deconfliction-config | Error: Metadata table "deconflictionConfig" parameter does not contain a valid value (such as "standard" or "maximized_1p_fidellity") |
val__embedded-identity__meta-table-only-config-column-allowed | Error: Metadata table should only contain a “config” column |
val__embedded-identity__meta-table-invalid-target-column-type | Error: Metadata table "target_column" value is not a string |
val__embedded-identity__meta-table-invalid-target-domain-type | Error: Metadata table "target_domain" value is not a string |
val__embedded-identity__meta-table-invalid-credentials | Error: Metadata table contains invalid "client_id" and "client_secret" credentials |
val__embedded-identity__logging-table-needs-permissions | Error: LiveRamp does not have the correct permissions for the logging table. Perform the procedure in the "Perform Initial Application Setup" section of the native app help documentation to grant select, insert, and update on the logging table. |
val__embedded-identity__logging-table-missing | Error: Either the logging table was not created or LiveRamp does not have the correct permissions for the logging table. Perform the procedure in the "Perform Initial Application Setup" section of the native app help documentation to grant select, insert, and update on the logging table. |
val__embedded-identity__logging-table-column-mismatch | Error: The logging table provided in application call contains columns that do not match the schema |
val__embedded-identity__event-logging-disabled | Error: Event sharing is disabled. Perform the procedure in the “Set Up the Logging Events Table” section of the native app help documentation to enable the sharing of events. |
val__embedded-identity__invalid-cid-column-name | Error: CID column names should match across all sub-jobs. Expected: xyz_cid_col_name Found: abc_cid_col_name |
val__embedded-identity__missing-permissions | Error: Your permissions were not found. Contact LiveRamp Support. |
val__embedded-identity__invalid-permissions | Error: You do not have permission for the requested workflow |
val__embedded-identity__pii-input-table-requires-non-identifer-column | Error: Input table does not have at least one non-identifier (attribute) column (required for PII workflows) |
val__embedded-identity__email-input-table-requires-non-identifer-column | Error: Input table does not have at least one non-identifier (attribute) column (required for hashed email workflows) |
val__embedded-identity__enable-auth-api-call-needed | Error: Auth API is not enabled. Perform the procedure in the "Perform Initial Application Setup" section of the native app help documentation to execute the "lr_app_schema.enable_auth_api_call" procedure. |
val__embedded-identity__invalid-billing-integration | Error: Billing api integration name does not exist or is not authorized for native app use. Check if the integration exists or run show grants to application to check if permissions have been provided. |
val__embedded-identity__invalid-billing-endpoint | Error:Endpoint has not been added to the billing api integration. Update the integration to include the endpoint as per documentation. |
val__embedded-identity__billing-integration-not-enabled | Error:Billing integration is not enabled. Follow the steps in the documentation to enable billing integration. |
dep__auth__failed-authentication | Error: Operation failed during authentication. Contact LiveRamp Support. |
bus__embedded-identity__failed-privacy-check | Error: Input table cannot contain an attribute column with a unique value |
bus__embedded-identity__too-many-unique-rows | Error: More than 5% of input rows contain columns that do not each contain at least three instances of each value so resolution cannot be executed. Remove any columns that do not have at least three instances of each value and try running the operation again. |
bus__embedded-identity__failed-input-row-count-check | Error: Operation failed to check row count for the input table. Contact LiveRamp Support. |
bus__embedded-identity__failed-collation-status-check | Error: Operation failed to check the collation status of target column on the input table. Contact LiveRamp Support. |
bus__embedded-identity__failed-attribute-append | Error: Operation failed to append attribute columns. Contact LiveRamp Support. |
Retry Failed Metrics
If the billing call failed, that means the job completed but was unable to report metrics to LiveRamp. The output table will not be made available until the metrics are successfully reported. After fixing the issue with the billing endpoint (see setup for the billing endpoint), call the retry_failed_metrics procedure (shown below) to retry reporting the metrics:
call lr_resolution_and_transcoding.lr_app_schema.retry_failed_metrics();
If the call to retry_failed_metrics successfully posted the metrics for the job, the output table name for that job will be included in the message, and the output table will be accessible inside lr_resolution_and_transcoding.lr_job_schema.
If retry_failed_metrics returns an error message, re-check the billing integration setup steps and try again. If it continues to fail, contact your LiveRamp representative.