Access2000 migrate to Oracle9i Essentials _oracle

The Oracle tutorial being looked at is: Access2000 migrate to Oracle9i essentials. -->Oracle9i provides a powerful migration capability to migrate data from multiple databases to Oracle. Oracle's new Release Migration Tool provides a simple solution for migrating from Access2000 to Oracle92010, which overcomes the problem of garbled Chinese and the truncation of strings, as follows is the whole process of migrating from Access2000 to Oracle92010.

First, download the latest version of OMWB (Oracle migration Workbench) to Otn and install to Http://otn. oracle.com/tech/migration/focusareas/access.html Download Oracle Migration Workbench release 9.2.0.1.2 for Microsoft Windows The latest versions of 98/NT/2000/XP and Plug-ins migrated from Access 2.0, or to the Oracle platform, are 92012. First install the OMWB in a different home directory than Oracle, and then install the Access plug-in to the same directory.

Preparing a data source for migration

To the \omwb\msaccess_exporter directory in the OMWB home directory, Open the Omwb2000.mde file, enter the Access database file you want to migrate, and the XML description file that will be generated for the database, and you'll find that you have generated an XML file with the same name under the same path as access, which records the columns and relationships of the tables in the Access database , the definition of the view. OMWB supports the Chinese table name and column name for access, but be careful to modify the \omwb\msaccess_exporter\schema.dtd file before generating the XML file, and the first row of encoding= "Iso-8859-1" Modified to Encoding= "GBK" and then generate an XML file for the database by opening the Omwb2000.mde file, the table name and column name are successfully displayed in Chinese, and the same method is used to modify the encoding of the generated XML file to encoding= before migrating to Oracle "GBK".

Third, run OMWB, perform the migration process

Run OMWB, as prompted, enter a description file for the Access database, the XML file generated in the previous step, that generates a data source for the migration based on the file, including tables, indexes, primary keys, relationships, and table validation rules. Next, the Oracle model is generated, OMWB the table space and two users automatically. Both the data source and the target data model are stored in Oracle's data archive, which is generated by the system prompts when the OMWB tool is installed. The next step is to perform the migration process, and you can also generate a script for the migration.

Solving the problem of truncated Chinese characters

OMWB provides data types that are mapped by data sources and purposes, modifying the data to reflect changes in the data length and type of the migration target, but I tried many times not to solve the problem, including modifying the source data type in the access model that was generated by OMWB reading XML files. The problem is access itself. First open the Access database, modify the data type and length in its datasheet, save the database and then exit, and then generate an XML description for the database, we will find that the table column definition of the XML file has changed, rerun OMWB, and after the source data model is generated for the migration, The data type and length of the source and target models are also automatically changed, and the subsequent migration process can correctly migrate long Chinese strings. Oracle's Enterprise Manager and Application Server Web interface has a few of the same problems, the modification of the data archive does not solve the problem, which is the Oracle Database products graphical interface tool defects

<