Powerful features of Oracle 9i

We all know that Oracle 9i has powerful functions, including the migration function. We can migrate data from a variety of different databases to Oracle. Oracle Database is a newly released migration tool that provides a simple and easy solution for migrating data from Access 2000 to Oracle 92010.

This solution overcomes Chinese Garbled text and string truncation issues. The following describes the entire process of migration from Access 2000 to Oracle 92010.

1. download the latest OMWBOracle Migration Workbench)

Install and download the Oracle Migration Workbench Release 9.2.0.1.2 for MicrosoftWindows98/NT/2000/XP and plug-ins for Migration from Access 2.0, 95, 97 or 2000 to the Oracle platform, the latest versions of both are 92012. First install OMWB in a different home directory from Oracle, and then install the Access Plug-in to the same directory.

2. Prepare data sources for Migration

Go to the \ OMWB \ msaccess_exporter directory in the Omwb main directory, open the omwb2000.mde file, and enter the Access database file to be migrated and the XML description file to be generated for the database, at this time, you will find that an XML file with the same name is generated in the same path as Access. Open this file, which records the columns, relations, and view definitions of Access database tables.

OMWB supports Access to Chinese table names and column names. However, before generating an XML file, you must modify \ Omwb \ msAccess_exporter \ schema. dtd file, Change encoding = "ISO-8859-1" in the first line to encoding = "GBK", and then generate an XML file for the database by opening the omwb2000.mde file, at this time, the table name and column name are successfully displayed in Chinese. Before migrating to Oracle 9i, you must use the same method to modify the generated XML file encoding to encoding = "GBK ".

3. Run OMWB to execute the migration process

Run OMWB and enter the description file of the Access database as prompted, that is, the XML file generated in the previous step. The data source is generated for the migration according to the file, the data source includes tables, indexes, primary keys, links, and table verification rules. Next, the Oracle model is generated. OMWB automatically generates tablespaces and two users. Both the data source and target data models are stored in the Oracle archive, which is generated by the system prompt when the OMWB tool is installed.

Next, you can execute the migration process and generate a script program for the migration.

4. Solve the Problem of Chinese Character Truncation

OMWB allows you to change the data length and type of the migration target by means of data source and target data types. However, this problem cannot be solved after several attempts, modifying the source data type in the Access model generated by reading XML files from OMWB does not help. The problem lies in Access itself.

First, open the Access database, modify the data type and length in the data table, save the database, exit, and generate an XML description for the database again. Then, we will find that the table column definition in the XML file has changed, run OMWB again. After the source data model is generated for migration, the data type and length of the source and target models are automatically changed. Then, the long Chinese string can be correctly migrated during the migration process.

There are several identical problems in the web interface of the Enterprise Manager and application server provided by Oracle 9i. Modifying the data archives cannot solve the problem, this is also a defect in the graphical interface tool of Oracle database products.