Use this section to troubleshoot publishing errors.
To troubleshoot issues when publishing an Automation script, see Troubleshoot Scripts on Intelligence Central.
|Issue or Error Message||Solution or Workaround|
|Google Analytics or Salesforce - expired access/refresh token||
Error Msg: "Invalid data source definition: 400 Bad Request: Invalid_grant (expired access/refresh token)"
This error may occur if the connection's authentication token is expired.
Solution: In the Publishing dialog, click the Authentication link, then click Reauthorize to re-enter your credentials and grant access to Toad.
"Data source name not found" error msg when using ODBC connectivity
Error Msg: "Invalid data source definition: Data source name not found and no default driver specified"
Solution 1: TIC uses only System DSNs. Make sure that you have specified a System DSN and not a User DSN.
Solution 2: The DSN on the TIC server must match the DSN you are using. Ensure that the DSN installed on the TIC server is the same as the one you are using to publish.
Note: This only applies when the connection you are publishing from uses ODBC connectivity.
|missing MySQL ODBC driver on TIC||
You are missing the MySQL ODBC driver. You can download the driver from the following site: http://dev.mysql.com/downloads.
Use MySQL ODBC driver versions 3.51 or 5.0.
|missing Teradata ODBC driver on TIC||
You are missing the Teradata ODBC driver. You can download the driver from the following site: http://www.teradata.com.
In addition to the Teradata ODBC driver, you must also install the Teradata .Net Provider.
|missing driver on TIC||
The Intelligence Central server you are publishing to is missing the matching ODBC driver. Install the required ODBC driver listed in the error message, or contact the administrator responsible for the Intelligence Central server.
You might also want to specify an ODBC driver to use when publishing from this database type to this particular TIC server.
To specify an ODBC driver
Note: Specify an ODBC driver to use only if you are having difficulty publishing from that particular database to the TIC instance.
|General problems publishing from an Oracle connection||
General issue: The Microsoft-supplied ODBC driver for Oracle is included in a standard Windows install and has limited functionality. To insure that the TIC server is using the Oracle ODBC driver instead of the Microsoft-supplied driver, you can specify a driver to use when publishing to that TIC instance.
Suggestion: Specify driver to use when publishing.
General issue: The TIC TNS names file may have a data service name that does not match the name in the TNS names file on the publishing workstation.
Suggestion: Modify one of the files to ensure the names match.
|"The ODBC driver does not support the data type."||
The Oracle ODBC driver does not support subtracting from TIMESTAMP. This is a known Oracle ODBC issue. If attempting to publish SQL such as the following:
Select Date_Col, Timestamp_Col - sysdate from Table
remove "Timestamp_Col - sysdate."
|"Out of sort memory" error||
Error Msg: "Out of sort memory, consider increasing server sort buffer size."
This error might be encountered when attempting to publish a query or when querying a published snapshot/view containing a GROUP BY or ORDER BY clause.
Solution 1: Add “ORDER BY NULL” to the end of the query.
Solution 2: Increase the value of the sort_buffer_size variable by adding "sort_buffer_size=2M" to the Intelligence Central configuration file found here:
C:\Program Files\Quest Software\Toad Intelligence Central\datahub.cnf
|Columns with the same name||
Error Msg: "Duplicate column name '<column name>'. Add a differentiating column alias."
Your query includes two columns with the same name and the columns do not have unique aliases.
Solution: Add unique alias names for the columns.
|"Incorrect key file" error msg||
Error Msg: "Incorrect key file for table 'C:\WINDOWS\TEMP\<myi file name>'; try to repair it."
Solution: The server is low on disk space. Increase available disk space.
|Specified key was too long||
Error Msg: "Specified key was too long; max key length is 1000 bytes"
This error may occur if you selected columns to index on the Indexing Options tab (applies to snapshots and datasets only). There is a limitation in the TIC database: The maximum index size (key length) is 1000 bytes.
© 2020 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad