Successfully!

Error!

Inspection of FineDB Exception

  • Last update:  2023-05-12
  • Overview

    This article provides solutions for resolving the FineDB exception that occurs when using Designer environment detection.

    Testing Items and Solutions

    Whether FineDB is in Good Condition

    Problem description: The current Hsql database is locked by another thread.

    Log record: Error code: 11300111 finedb is locked, the current Hsql database has been locked by another thread.

    Cause analysis: When opening the designer, it was found that the built-in database for the report is HSQL database, which does not support multi-threaded access. Solutions:

    One:

    Close the java editor, such as idea, Eclipse process, and delete the db.lck file under the exported template project %FR_HOME%\webapps\webroot\WEB-INF\embed\finedb. Open the java editor again and run the code.

    Note: After running this method once, it will still report an error, and you need to repeatedly delete the db.lck file.

    Two:

    Since the built-in HSQL database in the report server cannot be accessed by multiple threads, you can migrate it to other databases. For how to migrate it, see Configuring the External Database.

    Whether FineDB Can be Accessed

    Problem description: unable to access FineDB

    Log record: Error code: 11300112 finedb permission, can't access finedb.

    Cause analysis:

    1. If the current logged-in users do not have FineDB permissions, contact the admin to enable the corresponding permissions. Here refers to users of the operating system, not server users.
    2. FineDB file permissions were not enabled, which prevented you from accessing FineDB. For this situation, you should ask the super administrator to enable folder permissions.

    Solution: You can contact the super admin to open the corresponding folder or enable user permissions.

    Whether FineDB Has Dirty Data

    Problem description: FineDB has dirty data, table exception.

    Log record: Error code: 11300113 fineDb dirty data, {} table exception.

    Cause analysis: FineDB has dirty data.

    Solution: It is recommended to reset FineDB, which will generate a backup and reset it in the embed folder, or you can contact technical support for assistance.

     


    Attachment List


    Theme: Decision-making Platform
    • Helpful
    • Not helpful
    • Only read

    Doc Feedback