SQL Dataset Preview Error Troubleshooting

  • Last update:  2024-04-08
  • ORA Error

    Description

    Dataset preview failed, the error starting with ORA, for example, ORA-0911.

    Cause

    This error is an Oracle database error.

    Solution

    This error can be troubleshot by searching for the error information online.

    For example, a common error ORA-0911 indicates that the SQL statement contains invalid characters, and it is necessary to check whether there are invalid characters in the statement.

    62400001Duplicate Field Names Found

    Description

    When you add a SQL dataset and preview it, an error "62400001duplicate field names found: Store" is displayed, as shown in the following figure.

    Cause

    In the FineBI dataset, column names cannot be duplicated within the same table, otherwise an error will occur.

    Solution

    Check if there are duplicate column names when fetching data from the database.

    There are two ways to fetch two columns with the same data.

    1. Rename the duplicate column. For example, enter the statement select Store, Store as Store1 from new_salesdetail.

    2. Copy and paste the column through the Add Column function of the self-service dataset. For details, see Column Adding.

    Illegal Mix of Collations

    Description

    When you preview a SQL dataset, an error "Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT)" is displayed.

    Cause

    Encoding formats are inconsistent, or there are special characters in the SQL statement.

    Solution

    Change the encoding format to utf8_unicode_ci.

    For example, the SQL statement is select * from a where aa='aa', and its encoding format is utf8_general_ci.

    Change the encoding format to utf8_unicode_ci through the SQL statement select * from a where aa=CONVERT('aa' USING utf8) COLLATE utf8_unicode_ci.

    Failure to Save the Added SQL Dataset

    Description

    You cannot save successfully after connecting to the SQL Server database and adding the SQL dataset.

    Open %FineBI% fanruan.log, the log error is shown in the following figure.

    Cause

    During the execution of transactions in the SQL Server database, multiple transactions are executed simultaneously, causing a deadlock in the requests. Therefore, you cannot add tables normally.

    Solution

    Contact the database operation and maintenance administrator to handle deadlock or restart the database.



    附件列表


    主题: Data Center
    • Helpful
    • Not helpful
    • Only read

    滑鼠選中內容,快速回饋問題

    滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。

    不再提示

    10s後關閉

    Get
    Help
    Online Support
    Professional technical support is provided to quickly help you solve problems.
    Online support is available from 9:00-12:00 and 13:30-17:30 on weekdays.
    Page Feedback
    You can provide suggestions and feedback for the current web page.
    Pre-Sales Consultation
    Business Consultation
    Business: international@fanruan.com
    Support: support@fanruan.com
    Page Feedback
    *Problem Type
    Cannot be empty
    Problem Description
    0/1000
    Cannot be empty

    Submitted successfully

    Network busy