Oracle9i provides powerful migration functions to migrate data from multiple databases to Oracle. Oracle's new migration tool provides a simple and easy solution for migrating data from Access2000 to Oracle92010. This solution overcomes Chinese garbled characters and string truncation issues, the following is the full migration from Access2000 to Oracle92010:
Oracle9i provides powerful migration functions to migrate data from multiple databases to Oracle. Oracle's new migration tool provides a simple and easy solution for migrating data from Access2000 to Oracle92010. This solution overcomes Chinese garbled characters and string truncation issues, the following is the full migration from Access2000 to Oracle92010:
Oracle9i provides powerful
MigrationFunction, from a variety of databases to Oracle
MigrationData. Oracle released
MigrationThe tool provides
MigrationThis solution overcomes Chinese Garbled text and string truncation issues. The following is a simple solution from Access2000 to Oracle92010.
Migration.
1. Download and install
Download the latest OMWB (Oracle Migration Workbench) from OTN and install it to the http://otn.Oracle.com/tech/migration/focusareas/Access.html to download Oracle Migration Workbench Release 9.2.0.1.2 for Microsoft Windows 98/NT/2000/XP and from Access 2.0, 95, 97 or 2000 to Oracle Platform
MigrationPlug-ins. 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.MigrationPrepare a data source
Open the omwb2000.mde file in the \ OMWB \ msaccess_exporter directory of the Omwb main directory and enter
MigrationThe Access database file and the XML description file for the database to be generated. Then, you will find that an XML file with the same name is generated in the same path as Access. Open this file, it 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" to encoding = "GBK" for the first line, and then generate an XML file for the database by opening the omwb2000.mde file, the table name and column name are displayed in Chinese.
MigrationBefore Oracle, you must use the same method to modify the generated XML file encoding to encoding = "GBK ".
3. Run OMWB and executeMigrationProcess
Run OMWB and enter the description file of the Access database as prompted, that is, the XML file generated in the previous step.
MigrationGenerate a data source that 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. The next step is to execute
MigrationThe process can also be
MigrationGenerate a script program.
4. Solve the Problem of Chinese Character Truncation
OMWB allows you to change the volume of data from the data source and target.
MigrationThe Data Length and type of the target, but this problem cannot be solved after many attempts, including modifying the source data type in the Access model generated by the XML file read by the OMWB. 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
MigrationAfter the source data model is generated, the data type and length of the source and target models are automatically changed.
MigrationThe process is correct.
MigrationLong Chinese string. There are several identical problems in the web interface of the Enterprise Manager and application server provided by Oracle. Modifying the data archives cannot solve the problem, which is also a defect of the graphical interface tool of Oracle Database.
