Migrating Oracle to EDB migration combat with Navicat Premium

1.1 DB Migration Analysis

?? Before migrating data from Oracle to EDB, you need to do a lot of prep work. For example, it is necessary to analyze the source database data size, data stability, heterogeneous database compatibility, encoding mode, business logic (stored procedures, functions, triggers) and other migration, preferably before the migration implementation of a migration plan; Select the Migration tool to implement data migration. Save the migration log; After the migration, you need to verify the integrity of the data, consistency, and so on, record the number of checks, check the old and new database corresponding record number is consistent. Check the special sample data to see if the same sample is consistent in the old and new database.
?? Migrate the database source to Oracle, the target database is EDB; Migration tool: Navicat PREMIUM11; The source database has a total of 149 tables, this migration only migrates 64 tables, because this migration data volume is not small, take a migration (structure and data) way; use Postgres The Enterprise Manager tool creates the EDB target database and, after the migration, randomly extracts 2 samples for the migration result verification.

1.2 DB Migration Preparation

To create a target database:
Open the Postgres Enterprise Manager tool. For example, as seen in 1.1.

Figure 1.1
Open the server you just joined. Create target database login user test. For example, as seen in 1.2 and 1.3.

Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqv/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70/gravity /center ">
Figure 1.2

Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqv/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70/gravity /center ">

Figure 1.3
Right-databases Open the Create Database dialog box, as seen in 1.4, fill in the Properties tab with the target database name test and select the login user test created in the previous step, and then switch to the Definition tab. Fill in the database related properties, the "Connection limit" by default, then click OK, for example, 1.5 to see.

Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqv/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70/gravity /center ">

Figure 1.4

Figure 1.5
Create a schema in the target database. Open the database test (homologous database schema) that was built in the previous step. Then right-schemas Select new schema, fill in the schema name and select owner. For example, as seen in 1.6 and figure 1.7.

Figure 1.6

Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqv/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70/gravity /center ">

Figure 1.7
To this. The target database has been created well.

1.3 DB Migration Implementation

This migration tool selects Navicat Premium. Open Navicat Premium. Then connect the migration source and target databases separately.
Navicat Premium is a multi-connection database management tool. It allows you to connect to MySQL, SQLite, Oracle, and PostgreSQL databases in a single program, making it easier to manage different types of databases. The most important thing is that it doesn't have to be oracleclient.
It is not necessary to install the Oracle client without the assumption. Occupy a large space. There are about 500M. After loading it is very difficult to unload clean. According to Navicat official documents. In fact, only need to download Oracle Instance client can be, the specific solution can be in Baidu search "Navicat Premium oci".
Connect to the source database, as seen in 1.8.

Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqv/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70/gravity /center ">

Figure 1.8
Connect the target database, as seen in 1.9, open the target database test and open the schema. Refresh the table, view, and so on, confirming that the following objects, such as tables, views, and so on, are empty, as seen in 1.10.

Figure 1.9

Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqv/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70/gravity /center ">

Figure 1.10
In the Navicat premium menu bar, click Tools and select Transfer data. Open the Transfer Data dialog box, fill in the Migration database information in the General tab, and select the migration object, for example, as seen in 1.11, and then turn on the Advanced tab to set migration details (Migrate data/Migrate table structure/migrate data and structure at the same time), for example, 1.12 see. Click "Start" When you are finished setting up.

Figure 1.11

Figure 1.12
After the migration is complete. The time in the Infolog is no longer changed. You can see that this migration takes a total of 237.914s, as seen in 1.13.

Figure 1.13

1.4 DB Migration Verification

This migration verification selects the first two tables as samples for correctness and completeness verification. Ri_abandon_info Table summary information in the source database for example, as seen in 1.14, migrating the Ri_abandon_info table summary information in the target database, as seen in 1.15, is a control that can feel that the table data is migrated without problems.

Figure 1.14

Figure 1.15
Right-ri_abandon_info The table in the source database and select Design table. For example, as seen in 1.16, the Ri_abandon_info table in the target database is the same operation. For example, as seen in 1.17, it is not a problem to determine the table structure migration by comparing the constraints (primary, foreign key), index, and other information of the two table objects.

Figure 1.16

Watermark/2/text/ahr0cdovl2jsb2cuy3nkbi5uzxqv/font/5a6l5l2t/fontsize/400/fill/i0jbqkfcma==/dissolve/70/gravity /center ">

Figure 1.17
Verify the table structure and data migration of the validated table in the same way as the Ri_tksu_white_list_his table in the source database and the Ri_tksu_white_list_his table in the target database.

1.5 DB Migration Results

After the verification of the sample, the basic confirmation of this database migration is successful.

Migrating Oracle to EDB migration combat with Navicat Premium