反馈已提交
网络繁忙
2）When the external database is migrated and "migrate data to the database to be enabled" is not checked, it will automatically detect whether the project versions corresponding to the new and old databases are consistent
Note: when the jar package version is lower than 2019-05-20, the user can only migrate data when configuring the external database, and cannot directly enable the new database.
After the BI system is configured with an external database, it can ensure the stability of the BI system in case of a cluster environment or a large amount of data.
The user can configure the external database in "initialization" or configure the external database of SQL server version in "platform".
Note: if an external database is configured, do not easily modify the user name and password of the external database, otherwise the project will fail to start.
For modification, please refer to：Modify the external database account password .
The types and versions supported by the external database are shown in the following table:
2000、2005、2008、2012、2014、2016
Note 1: the occupied space needs to be adjusted in combination with the usage. It can be configured according to the size of the webapps / Webroot / WEB-INF / embedded / finedb folder, and the future use size can be estimated according to the actual size, increasing by 1-2 times.
Note 2: the recommended memory is the memory reserved for the engineering configuration library.
Note 3: the external database shall be in the same network segment as the Bi project as much as possible to avoid network fluctuation and other problems.
Create a new database to store platform related data.
Standard database creation statement:CREATE DATABASE finedb COLLATE Chinese_PRC_CS_AS
Note: different finebi projects cannot share the same external database, otherwise the data may be disordered.
The sorting rule of SQL Server database can be Chinese_ PRC_ CS_ As (case sensitive) or Chinese_ PRC_ CI_ As (case insensitive), Chinese is recommended_ PRC_ CS_ As (case sensitive).
Select Chinese_ PRC_ CS_ As will migrate all data intact.
Select Chinese_ PRC_ CI_ As, if fine is reported during migration_ conf_ The entity table violates the words such as the primary key constraint. Usually, the project has dirty data.
You can execute the following SQL statement to view dirty data:select lower(ID),COUNT(1) FROM FINE_CONF_ENTITY GROUP BY LOWER(ID) HAVING COUNT(1) >1
This method is applicable to configuring external database when logging in data decision system for the first time.
The user can configure the external database when entering the platform for the first time, as shown in the following figure:
Click "Enable New database" to enter the external database configuration interface, select the database type as SQL server, and enter the corresponding information of the actual database. As shown in the following figure:
The description of each setting item is shown in the following table:
Automatic configuration without modification
Section 2.3 new database name
It is forbidden to share the database with other projects. It is recommended to create a new database
The database name can only contain numbers, letters, underscores and "."
The host name can only contain numbers, letters, underscores, "-" and "."
Users need to have create, delete, alter, update, select and insert permissions
1）Bi projects of version 5.1.15 and later only support drop-down selection mode
After completing the above settings correctly, click "connect to database" in the mode drop-down box. The system will automatically connect to the database and read the mode. Select it (try to select the mode with the same name as the database user)
Note: if you are prompted that the database connection fails, please check the above settings.
2）Bi projects before 5.1.15 only support manual input mode
The mode defaults to dbo
Administrators can use theSELECT * FROM sys.database_principals to find the schema of the database, or use the Navicat connection to view the schema of the database.
Wait for some time, and you will be prompted that Successfully enabled the new database . As shown in the following figure:
Note: do not refresh the page during migration.
This method is applicable to configuring external database for the first time after entering the data decision system.
The administrator logs in to the data decision system and clicks "manage > System > General > external database > to be configured", as shown in the following figure:
Input the corresponding information of the actual database and configure the external database. As shown in the following figure:
1) Bi projects of version 5.1.15 and later only support drop-down selection mode
The administrator can use select * from sys database_ Principals look for the schema of the database, or use Navicat connection to view the schema of the database.
4.3 Configuration succeeded
After waiting for a period of time, a pop-up prompt will pop up: the target database has been successfully enabled. Click OK. As shown in the following figure:
Note 1: do not refresh the page during migration.
Note 2: there is no need to restart after the database configuration is successful.
This method is applicable to migrating to a new database after the external database has been configured.
The administrator logs in to the data decision system and clicks "Manage > System > General > external database > configured", as shown in the following figure：
Description of the "migrate data to the database to be enabled" button:
1）Check "migrate data to the database to be enabled"
When the database is switched, the data of the original external database will be imported into the new database, and the historical data backup file will not be generated under the project.
If platform data already exists in the new database, the original platform data will be cleared before importing data. The prompt is shown in the following figure:
2）Uncheck "migrate data to the database to be enabled"
If the new external database is empty, it prompts that the current data must be migrated to the target database.
If the new external database is not empty
Before migration, the configuration information of the original database will be automatically backed up, and the db.properties.bak file will be generated in the webapps \ Webroot \ WEB-INF \ config directory. As shown in the following figure:
The Bi project of version 5.1.15 and later will automatically detect whether the jar package version corresponding to the data in the target database is consistent with the jar package version of the current project.
If it is inconsistent, a prompt will pop up: unable to enable! Project version required to enable the new database: XXX. Current project version: XXX. Please ensure the project version is consistent!
If the jar package version is consistent, directly enable the new database. After the migration is successful, the prompt is as shown in the following figure：
After waiting for a period of time, a pop-up prompt will pop up: successfully switched to the target database! If there is data difference between the old and new databases, the system operation may be affected. It is recommended to restart the project to ensure normal use.
Click "Determine" and restart the Bi project. The migration is successful. As shown in the following figure:
注：请勿在迁移过程中刷新页面。
Tips：
售前咨询电话
400-811-8890转1
在线技术支持
在线QQ：800049425
热线电话：400-811-8890转2
总裁办24H投诉
热线电话：173-1278-1526
文 档反 馈
鼠标选中内容，快速反馈问题
鼠标选中存在疑惑的内容，即可快速反馈问题，我们将会跟进处理。
不再提示
10s后关闭