Today we will start practicing the data migration functionality of the Gold Warehouse database. Until now, we have been using a simplified version of the Docker image, which does not integrate visual manipulation tools. Therefore, to make it easier to follow, we need to download and install an additional Windows version of the installation package.
Note that if you do not intend to install the database, you can choose not to install the relevant components during the installation process. We won't show you the exact installation procedure, as it is very intuitive and similar to the installation of other common software.
mounting
Once the download is complete, simply double-click on the installation package and follow the prompts to install it. As shown in the picture, you can start the installation process after clicking the installation package.
In this operation, we mainly use the KDTS visualization tool provided by the Gold Depot database. We just need to find the folder where the KDTS tool is located and double-click it to run the .bat startup file.
Here I stepped on a pitfall, encountered double-click startup has been reporting errors, prompting "can not find the file path". At first I thought it was the Chinese path that was causing the problem, but upon closer inspection I realized that there was no Chinese path at all. The only thing that puzzles me is that there is a space at the end of one of the folder names.
So, I decided to try reinstalling the program into a directory with no spaces in the path, and surprisingly it ran smoothly. It seems that the root of the problem was really the space in that folder name.
Immediately after that, we launched the batch (.bat) file in accordance with the normal process, the results of the program started smoothly and successfully run without any error message. The specific running status is shown in the figure.
By default, the program does not open the browser automatically, but displays a message in the console window that the service was started successfully. At this point, the user only needs to close this window to continue the operation. After closing the window, we can check the status of the program directly in the browser by visiting the default address, which is:http://localhost:54523/
In addition, the default login username and password for the web page are respectively:kingbase / kingbase, you can use these credentials to log in.
Migration UI
After entering the correct username and password, we successfully logged in and entered the system interface. Next we operate a little.
First, in order to start the migration operation, we need to create a data source, that is, specify the database we want to migrate. Here I will demonstrate how to do this for MySQL version 8. It is very important to make sure that you select the correct database type - in this case MySQL version 8 - when choosing the data source type.
If the wrong database version or type is selected, the system may have unforeseen exceptions.
Remember that you should not create a new data source directly in the "Migration Data Management" when you are migrating data. This is because once you create a new data source in this interface, the system needs to refresh the page for the new data source information to take effect.
If you don't want to refresh the page frequently and waste time, then it is recommended to go ahead and finish configuring the data source information before you start the configuration.
Next, we can continue to configure the KES link information normally. During the configuration process, please take special care not to select the wrong KES compatibility mode, otherwise the configuration may fail. Please refer to the following picture for the specific effect.
Next, we directly click on the database information we have selected, the default will be all migrated, if you do not want to migrate some information, you can choose to remove the check box. As shown in the figure:
Immediately after that, after clicking the Save and Migrate button, wait for the task to start, don't click it more than once, he's going to be a little slow here. Then, we can go to see the migration progress of the task, because I am a table here, so the migration is very fast.
If you have a lot of large tasks, there are also task execution batches here for you to view, you can choose to migrate slowly, and if there are any errors there are also partial migration logs here for you to view.
At this point, our MySQL database was migrated properly to the KES Gold Warehouse database.
summarize
Through this operation, we successfully migrated MySQL database to KES Gold Warehouse database and completed the related configuration and data migration smoothly. During the process, we encountered some minor problems, such as spaces in the file path, but the problem was solved by adjusting the installation path. It is worth noting that when configuring the data source, you need to be careful to choose the correct database type and compatibility mode to avoid unnecessary errors. Overall, the data migration feature of GoldCura Database is easy to use, but requires careful operation and checking of details to ensure successful completion of the migration task.
I'm Rain, a Java server-side coder, studying the mysteries of AI technology. I love technical communication and sharing, and I am passionate about open source community. I am also a Tencent Cloud Creative Star, Ali Cloud Expert Blogger, Huawei Cloud Enjoyment Expert, and Nuggets Excellent Author.
💡 I won't be shy about sharing my personal explorations and experiences on the technology path in the hope that I can bring some inspiration and help to your learning and growth.
🌟 Welcome to the effortless drizzle! 🌟