Troubleshooting the Accelerator Installation

Q. I ran the sample code and the output tables were not created in my user schema. What now?
A. The stored procedures can fail if one or more of the following conditions are true:
  • The request specifies an output location to which the user does not have Write permission. Verify that you have access to the database that is specified in the output_table parameters.
  • The data quality stored procedures are not installed correctly. Verify that the stored procedures are in the SAS_SYSFNLIB database by executing the following command in BTEQ:
    select TableName from dbc.tables where databasename='SAS_SYSFNLIB' 
    and tablename like 'dq_%';
    The command should return a list similar to the following list (This is not a complete list.):
    TableName
    ------------------------------
    dq_set_qkb
    dq_match_parsed
    dqi_drop_view_if_exists
    dqi_get_option_default
    dq_debug
    dq_propercase
    dqi_tbl_dbname
    dqi_drop_tbl_if_exists
    dq_set_option
    dqt_error
    dq_standardize
    dq_standardize_parsed
    dq_debug2
    dqi_invoke_table
    dq_lowercase
    dq_set_locale
    dq_extract
    dq_uppercase
    dq_list_bindings
    dqi_replace_tags
    dq_list_defns
    dqi_call_ep
    dqi_get_bool_option
    dqi_gen_toktxt
    dqt_codegen
    dq_match
    dq_parse
    dqt_trace
    dq_pattern
    dqi_clear_tok_tbls
    dqt_tokname_tmp
    dq_format
    dq_list_locales
    dqi_invoke_scalar
    dqi_invoke_preparsed
    dq_bind_token
    dq_gender
    
    If the procedures are absent, run the dq_install.sh script again, making sure that you are logged in as Teradata system administrator.
  • Permission to the data quality stored procedures is not granted correctly. Verify that the target user name submitted to the dq_grant.sh script is a valid user account in the Teradata database. Verify that the database server and granter information in the dq_grant.sh shell script is correct.
  • The QKB is not in the correct location. Look for subdirectories similar to the following in the /opt/qkb/default directory on the Teradata nodes: chopinfo, grammar, locale, phonetx, regexlib, scheme, and vocab.
  • Your SQL request does not use the Teradata dialect. The stored procedures are invoked with the CALL keyword from any product that supports the Teradata SQL dialect. When you submit the data quality stored procedures in the SAS SQL procedure using explicit pass-through, the database connection is made in ANSI mode by default. You must specify the MODE= option to switch to Teradata mode. Consult the SAS/ACCESS Interface to Teradata documentation for more information about the MODE= option. Consult appropriate documentation for how to set Teradata mode in other client programs.
Last updated: February 9, 2017