| Classification | Blocking Level | Processing Method | Detection Content | Interface Prompts | Excel Prompt |
1 | Configuration | SUGGEST | Detection tool processing | 1. Whether an external database is configured. 2. Whether the value of hibernate.hbm2ddl.auto in WEB-INF/config/db.properties is set to update. | No prompt. | The value of hibernate.hbm2ddl.auto is not update. Modify the value to update; otherwise, the compatible update cannot be configured during the upgrade. |
2 | Configuration | WARN | Manual processing | 1. If the MySQL parameter max_allowed_packet needs to be configured less than 1073741824, mark it as a warning. 2. If the parameter of MySQL, max_allowed_packet, cannot be detected, mark it as a warning. | WARN: When the configured external database is MySQL and the parameter max_allowed_packet is less than 1073741824, it wll affect configuration compatibility execution. WARN: Users currently connected to the external database have no access to query the parameter of MySQL, max_allowed_packet. It is required that the parameter value should be at least 1073741824. Check by yourself. | It is detected that the external database is MySQL, and the parameter max_allowed_packet is less than 1073741824. The upgrade process requires compatible adjustments to the configuration. If the parameters are too small, the configuration cannot be written to the database. To ensure that the upgrade runs smoothly, you should firstly modify the parameter, max_allowed_packet. The adjustment method is as follows. Method one: In the file of my.ini of the MySQL installation directory, modify the value of max_allowed_packet in the field of mysqld from 1 M to 1024 M. Then restart MySQL. Method two: 1. Use the statement set global max_allowed_packet = 1073741824; to set the value of max_allowed_packet to 1024M without rebooting. 2. Use the statement show VARIABLES like '%max_allowed_packet%'; to check whether the modification is successful. |
3 | Configuration | SUGGEST | Detection tool processing | Check whether the value of UpdatePushConfig.open" is false, and mark it as a prompt. | Export file prompt |
|
4 | Configuration | BLOCK | Manual processing | Get the path corresponding to spider_local_root_path and check if a file can be created in the corresponding path. | It is detected that there is no file creation permission under the {directory} path. This path is the data update path and must have file read and write permissions. | It is detected that there is no file creation permission under the {directory} path. This path is a data update path and must have file read and write permissions. Use chmod path to authorize this path. The command format is as follows: chmod -R 777 {directory} path. |
5 | Configuration | BLOCK/ WARN | Manual processing | 1. JDK version is Oracle's 1.8.0.102. You need to upgrade JDK first and mark it as a block. 2. If JDK version information cannot be detected, mark it as a warning. | BLOCK: If JDK version is lower than 1.8.0.102, after upgrading, it will cause abnormal startup due to JDK vulnerabilities. Upgrade JDK version first before upgrading FineBI. WARN: JDK version is unavailable currently. Confirm that JDK version is greater than 1.8.0.102. | It is detected that JDK version is lower than 1.8.0.102. There are vulnerabilities in the older version of JDK. After upgrading, there will be startup crash. It needs to be updated to at least version 1.8.0.102 before upgrading. Cipher suite will be installed in JDK after upgrading, which may cause data connection loss. For details about solving this problem, see JDK Upgrade and Notes. |
6 | Configuration | WARN | Manual processing | Check whether fineclusterConfig.params.cluster is false, and whether SystemOptimizationConfig.biClusterMasterNodeHostName is not null, whether hotBackConf.master is not null, whether SystemOptimizationConfig.ClientMasterld is not null, whether hotBackConf.slave is not null. StateServerConfig.type != standone StateServerConfig.clusterMode != false | WARN: It is detected that the current environment is a standalone environment, but the clustered configuration remains. You need to delete remaining parameters. | It is detected that the current environment is a standalone environment. But the clustered configuration remains, and you need to delete remaining parameters. The following hot backup parameters need to be deleted. You should connect the configuration library to modify the corresponding parameters in the fine_conf_entity table. Not Null means you should delete ID: SystemOptimizationConfig.biClusterMasterNodeHostName. Not Null means you should delete ID: hotBackConf.master. Not Null means you should delete ID: SystemOptimizationConfig.ClientMasterld. Not Null means you should delete ID: hotBackConf.slave. The following are the redis configuration parameters. Please confirm whether the redis configuration is still in use. If it has been stopped, log in to the administrator and close the state server in Intelligent Operation and Maintenance > Cluster Configuration. |
7 | Configuration | WARN | Manual processing | Detect whether there are backup files for the day. | WARN: No successful backups detected in the system within the past day. Confirm that the system is configured for backups. | No backups detected in the system within the past day. It is recommended that you back up data before upgrading. For details, see Backup and Restore. |
8 | Driver | WARN | Manual processing | Detect whether the external database is Oracle 11g or above version and ojdbc8 is not found in the lib directory. | WARN: It is detected that the external database is Oracle11g or above version. It is recommended that you use the matching driver ojdbc8. | It is detected that the external database currently used by the system is Oracle11g or above version. It is recommended that you update the driver to ojdbc8 and then upgrade. You need to change the ojdbc14.jar file to ojdbc8.jar and orai18n.jar. |
9 | Driver | BLOCK | Manual processing | Install driver isolation plugins for hive, phoenix, spark, impala, TRANSWARP, and INCEPTOR. | BLOCK: Drive collision blocking. | It is detected that the system uses data platforms such as hive, phoenix, spark, impala, TRANSWARP, INCEPTOR. The drivers they use are easy to conflict with BI codes. It is strongly recommended that you configure driver isolation to ensure the stable operation of the system. For details about configuration mode, see Driver Isolation Plugin for version 5.1.2 or above. |
10 | Abnormal lib file | BLOCK | Manual processing | Prompt to delete commons and other jar files after detection. | BLOCK: Abnormal lib file conflict blocking | It is detected that this file is likely to conflict with the BI codes. You need to restart BI after deleting it, and then upgrade. |
11 | Abnormal lib file | BLOCK | Manual processing | Prompt to delete folders under lib, zip files and files with the same name after detection. | BLOCK: Abnormal lib file conflict blocking | It is detected that there are folders, zip files, and files with the same name in the lib file. This type of file can easily cause instability in BI system. You need to restart BI after deleting them and then upgrade. |
12 | Abnormal lib file | WARN | Manual processing | Non-txt and jar files under lib folder are illegal. Prompt to delete them after detection. | WARNING: Abnormal lib file detected. It is recommended to delete it. | It is detected that there are non-jar and non-txt files in the lib file, which may affect the project. Delete them before upgrading. |
13 | Abnormal lib file | BLOCK | Manual processing | Driver packages in hive, phoenix, spark, impala, TRANSWARP, INCEPTOR, hbase, maxcomputer, and kylin. hive: geronimo-jaspi, hadoop-common, hive-jdbc, xercesImpl spark: hadoop-core, hive-jdbc maxcomputer slf4j-log4j, odps-jdbc TRANSWARP -INCEPTOR TRANSWARP, INCEPTOR hbasep, hoenix phoenix impala impala kylin kylin | BLOCK: Abnormal lib file conflict blocking | It is detected that there are drivers of data platforms such as hive, phoenix, spark, impala, TRANSWARP, and INCEPTOR in the lib file. This kind of file is prone to conflict with BI codes. You need to delete them, restart BI, and then upgrade. |
14 | Abnormal lib file | BLOCK | Manual processing | Detect whether fr-{directory}-8.0, fr-{directory}-9.0, fr-{directory}-4.0, fr-{directory}-4.1, fr-slf4j-frlog4j exist. | BLOCK: Abnormal lib file conflict blocking | It is detected that there are jar files for version 8.0 and 9.0 in the lib file. This kind of file is prone to conflict with BI codes. You need to delete them and restart BI before upgrading. |
15 | Plugin | WARN | Manual processing | Detect whether the plugin name exists in second-developed plugins such as JSD, SLN. | WARN: It is detected that there are second-developed plugins in the plugin management. It is recommended that you contact technical support to confirm whether the new version of the plugin is compatible. | It is detected that there are second-developed plugins in the plugin management. It is recommended that you contact technical support to confirm whether the new version of the plugin is compatible. |
16 | Plugin | WARN | Manual processing | Plugin detects that the ZIP file name fr-plugin-platform-bridge, com.tptj.plugin.hg.platform and installation file name plugin-com.tptj.plugin.hg.platform.bridge exist in plugin name. The plugin needs to be upgraded. | WARN: A single sign-on plugin is detected in the plugin management. It is recommended that you contact technical support to obtain the plugin of a new version. | A single sign-on plugin is detected in the plugin management. It is recommended that you contact technical support to confirm whether the plugin of a new version is compatible |
17 | Plugin | SUGGEST | Detection tool processing | Delete plugin plugin-com.fr.plugin.decision.data.check, ZIP file plugin-com.fr.plugin.decision.data.check. | Export file prompt | An invalid plugin is detected in the plugin management. This will affect the upgrade and will be automatically deleted during the upgrade. |
18 | Plugin | SUGGEST | Detection tool processing | Delete switching table in plugin dataset bi-plugin-table-switcher-1.0.2-513.zip. | Export file prompt | An invalid plugin is detected in the plugin management. This will affect the upgrade and will be automatically deleted during the upgrade. |
19 | Plugin | SUGGEST | Detection tool processing | Delete default selection table in plugin dashboard fr-plugin-default-widget-type-1.0.0.zip. | Export file prompt | It is detected that there is a dashboard default selection table plugin in the plugin management. The new version already has this function and will automatically delete this plugin during the upgrade. |
20 | Plugin | SUGGEST | Detection tool processing | Delete com.fr.plugin.platform.safelogin. | Export file prompt | Version 9.0 plugin is detected in plugin management, and the current system is version 10.0. The plugin has hidden trouble to the stability of the system and has been deleted automatically. |
21 | Plugin | WARN | Manual processing | Detect whether the name multi-ldap login exists in the plugin name. ID is not: com.fr.plugin.decision.multi.ldap.passport. Prompt that you need to reconfigure after upgrading. | Export file prompt | Multi-domain LDAP authentication plugin is detected in the plugin management. The functional logic of this new version plugin has changed. You need to adjust it manually. For details, see Multi-domain LDAP Authentication. |
22 | Plugin | SUGGEST | Detection tool processing | Detect whether plugin-com.finebi.memory-1.0.5, plugin-com.finebi.memory-1.0.5 exist in the deletion plugin name. Detect whether plugin-com.finebi.memory-1.0.6, plugin-com.finebi.memory-1.0.6 exist in the deletion plugin name. | Export file prompt | The memory management plugin of an old version is detected in the plugin management. The current system is version 10.0. This plugin poses a risk to the system stability and has been automatically deleted. |
23 | Plugin | SUGGEST | Detection tool processing | ZIP file name: fr-plugin-bi-inspector. id: com.finebi.plugin.bi.inspector. Installation file name: plugin-com.finebi.plugin.bi.inspector. ZIP file name: fr-plugin-bi-cleaner. id: com.finebi.plugin.bi.cleaner. Installation file name: plugin-com.finebi.plugin.bi.cleaner. | Export file prompt | The old version tool plugin is detected in the plugin management. This plugin poses a risk to system stability and has been automatically deleted. |
24 | Plugin | WARN | Manual processing | Detect whether the current environment can be connected to the plugin store. Prompt to upgrade the plugin after upgrading. | WARN: If you can connect to the prompt, log in to the plugin management page to upgrade the corresponding plugin upgrade items after upgrading. If you cannot connect to the prompt, open the plugin store (https://market.fanruan.com/) to check whether there are new updates for installed plugins. | If you can connect to the external network, log in to the system, and open the plugin management page to upgrade the plugin that need to be upgraded after upgrading. Currently, you have installed multiple plugins. If you do not update the corresponding plugins, you cannot use some functions. Or If you cannot connect to the external network and it is detected that the current environment cannot be connected to the plugin store, open the store, check whether the installed plugin has been updated to the latest version, and download the corresponding plugin for local update. Currently, you have installed multiple plugins. If you do not update the corresponding plugins, you cannot use some functions. |
25 | Plugin | WARN | Manual processing | Missing plugin dependencies may cause plugin abnormalities. (If this item can be realized, there is no need for prompt in 13, 14, and 22.) |
|
|
26 | Plugin | suggest | Detection tool processing | Delete a plugin. File name: plugin-com.fr.plugin.operation ID: com.fr.plugin.operation |
|
|
27 | Plugin | BLOCK | Manual processing | Detect whether BI hot backup plugin is enabled. plugin-bi-hot-backup | BLOCK: Hot backup clusters do not support upgrade. | It is detected that the BI hot backup plugin is enabled in the plugin management. The current upgrade tool does not support the upgrade of the hot backup environment. |
28 | Plugin | WARN | Upgrade tool processing | Detect spider dataset plugin. plugin-report-spider-dataset | Export file prompt | Spider dataset is detected in the plugin management. This function is not supported in V6.0 and will be disabled during the upgrade. |
29 | Plugin | SUGGEST | Upgrade tool processing | Delete the driver isolation plugin. plugin-decision-driver-loader https://git.fanruan.com/fanruan/demo-driver-loader/src/master | Export file prompt | A certain plugin is detected in the plugin management. The new version already includes this function, and it will be automatically deleted during the upgrade. |
30 | Plugin | SUGGEST | Upgrade tool processing | Delete front-end classification processing analysis table plugin. bi-plugin-classify-table | Export file prompt | A certain plugin is detected in the plugin management. The new version no longer differentiates the analysis table, and it will be automatically deleted during the upgrade. |
31 | Plugin | SUGGEST | Upgrade tool processing | Delete socket visit plugin in BI template. plugin-bi-websocket-visit | Export file prompt | A certain plugin is detected in the plugin management. The new version already includes this function, and it will be automatically deleted during the upgrade. |
| Plugin | SUGGEST | Upgrade tool processing | HTTPS_SameSite_cross-domain com.fr.plugin.decision.cookie.check | Export file prompt | A certain plugin is detected in the plugin management. The new version already includes this function, and it will be automatically deleted during the upgrade. |
| Plugin | SUGGEST | Upgrade tool processing | SQL in the dataset can be displayed in full screen. com.fr.solution.plugin.better.sql.editor | Export file prompt | A certain plugin is detected in the plugin management. The new version already includes this function, and it will be automatically deleted during the upgrade. |
| Plugin | SUGGEST | Upgrade tool processing | Beginner's guide com.fr.plugin.user.guide | Export file prompt | The new version is already built-in. |
32 | Plugin | SUGGEST | Upgrade tool processing | BI field grouping plugin com.finebi.plugin.fieldgroup | Export file prompt | This plugin is no longer supported. |
33 | Plugin | SUGGEST | Manual processing | Delete BI template screen self-adaptation plugin: plugin-bi-screen-adaptive. After upgrading, it will automatically update to the plus version: plugin-bi-show-adaptive. | Export file prompt | A certain plugin is detected in plugin management, which is no longer supported in the new version and will be automatically deleted during the upgrade. If you need to use it, you can download the BI template screen self-adaptation plus plugin in the plugin store. |
34 | Data | WARN | Manual processing | Check the standardization of a custom function class. | WARN: Custom function cannot be serialized. | It is detected that there is a certain custom function in the system. The function cannot be serialized because it is written non-standard. Modify it for re-adaptation. |
35 | Data | WARN | Manual processing | It is detected that the Excel table in the user's self-made dataset uses self-separating columns and transposition of rows and columns. | WARN: After upgrading, the Excel table in the user's self-made dataset no longer support self-separating columns and transposition of rows and columns. | A column conversion/self-separating column is detected in a certain Excel table of the user's self-service dataset. It is recommended to move to public data. |
36 | Data | WARN | Manual processing | Detect whether the composite filter component parameters use filter components. | WARN: The composite filter components no longer support the use of reference control parameters. | It is detected that the certain composite filter component uses the parameter usage of the filter component. It is recommended to adjust the filtering method without the parameter of the filter component. |
37 | Environment | BLOCK/ WARN | Manual processing | If disk space is less than 1 GB, mark it as a block. If no disk space can be detected, mark it as a warning. |
| It is detected that the current remaining disk space is less than 1 GB. Ensure that the disk space is greater than 1 GB before upgrading. You can clean up the disk space first and then upgrade. |
38 | Environment | WARN | Manual processing | Detect whether there has been an upgrade rollback. |
| It is detected that the system do not roll back the configuration content according to the document during the upgrade. This operation may generate dirty data. It is strongly recommended that you test the environment to verify the upgrade first. |
39 | Environment | BLOCK/ WARN | Manual processing | If the external database does not have DDL permission, mark it as a block. |
| It is detected that your system uses an external database and that the current user does not have permission to add, delete, and modify (DDL) tables. It is recommended that you contact the database operator to modify the corresponding permissions before upgrading. |
40 | Environment | BLOCK/ WARN | Manual processing | Check the code of the external database. If the MySQL code is not utf8 or utf8mb4, mark it as a block. If the SQL Server code is not Chinese_PRC_CS_AS, mark as a block. If it is, mark it as a warning. |
| It is detected that the code of the external database is not the required one. |
41 | Environment | WARN | Manual processing | Detect whether the current environment is a cluster environment. If it is, prompt to update nginx. | WARN: It is detected that the current environment is a cluster environment. After upgrading, see Guidance for Upgrading NGINX Configuration to a New Version to update NGINX forwarding configuration. | WARN: It is detected that the current environment is a cluster environment. After upgrading, see Guidance for Upgrading NGINX Configuration to a New Version to update NGINX forwarding configuration. |
42 | Environment | SUGGEST | Manual processing |
|
| Clear your browser cache after upgrading. |
43 | Environment | BLOCK | Manual processing | Check whether msvcr120.dll exists in the operating environment. |
| The msvcr120.dll runtime library does not exist. You need to install the x64 version of Visual Studio 2010 (VC++ 10.0) before upgrading. For details, click to see Microsoft Help Document: Microsoft Visual C++ Redistributable latest supported downloads. |
