Some problems encountered during Dameng database migration
Dameng Database is a high-performance database management system with completely independent intellectual property rights launched by Dameng Company, referred to as DM. The latest version of Dameng Database Management System is version 8.0, referred to as DM8. What I want to talk about here is also the use of Dameng 8.
In the past, I used to connect to the DM8 database on the company's server in company projects. Later, I also created a database on my own computer, so that when I was doing development, I could connect to the database on the server as well as my own local database. database.
So, I started to migrate the database, and directly exported the database into an emp file according to my idea. I imported about 10 g, and then imported it into the local database, but the result was like this: When importing Failed to execute emp file. Because I used mysql in the past, I just exported the sql file directly when exporting, and then imported it into the specified database. So I felt that the database operation method was different. Then I checked online to find out how to export the database in DM8. In fact, At that time, I was supposed to try to use sql to export, but I didn't try. Maybe I lost my mind, so I forgot about it for now. Using DM8's database migration tool, you can directly export the database to the database you want to import, which is very convenient. This migration tool comes with DM8 and can usually be found in the start menu.
After opening, select New Project, Create New Migration, and then the following interface will appear. You need to fill in the data source. This step is to fill in the information of the exported database. Click Next. Fill in the IP, port, username, and password of the imported database. Click
Next
. ,
Next, select the corresponding mode, for example, mine is dm import dm, then select next, the following appears and click
Finish.
Then the problem came. The import took about an hour or more. It depends on the amount of data in your database. After importing,
I changed the configuration of connecting to the database in the project to local. As a result, the project ran without problems, but when I logged in Sometimes it prompts an invalid indication, or the view name reports an error:
select * from accountsbpt;
execution failed (statement 1)
Error [-2106] occurred near line 1:
Invalid table or view name [ACCOUNTSBPT]
When this error occurred, I thought that this table had not been imported, but this table had already been imported. Then, I added the schema name to this sql, and the execution was successful, but all the sql in the project were not schema name, so I had to change the database to see how it could be done without adding the schema name. Then I found out on the Internet that the username of the logged-in user is the same as the schema name. , you can query without adding the schema name, so I created a new user with the same name as the schema name. As a result, it kept prompting that the user creation failed. Then I followed the online prompts to create the table space first, and then prompted The creation of the table space failed, and there was really no other way. When I arrived at the company the next day, I asked a colleague of the company for advice. What he did was to delete the database, create a user first, and then use the database migration tool to import it. This time it didn't work. There's a problem,