The transplantation between the Oracle database is a better policy (import / export) with the portfolio of the Oracle database. Although it is also possible to use the REVERSE ENGINEERING in Sybase's Power Designer to perform database structure, then the more complex data import process, but for job queues, snapshots, etc. have to be created. EXPORT outputs the entire database, specifies the user, specifies, and related data dictionary, and the Output Transport binary of Export output includes commands needed to completely rebuild all selected objects. I am using Oracle's MIS (Oracle Database) data to transplanted from the Windows NT platform to the Digital UNIX platform to share the experience and summary of experience with everyone. 1. Transplantation Environmental Operating System Platform: Windows NT Database: Oracle 8.0.5 for Windows NT Server: HP NetServer LH3 Target Operating System Platform: Digital Unix Alpha V4.0 Database: Oracle 8.0.4 for Digital Unix Server: Alphaaserver ES40 Small Machine 2. Data Guide to perform data export on the NT server, the Oracle Export Tool has the command line and the graphical interface two people directly with the command line mode: C:> Exp80 gxmisdba / manager file = C: Expdat .dmp log = c: Export.log is about to export the specified user ... The external function library name is exporting the user GXMISDBA. Object type definition of the user GXMISDBA is about to export GXMISDBA's object .... Export database link The serial number is exported. The cluster definition is being exported. The table is about to export GXMISDBA through a regular path ..... Are exporting table AAAAA 0 lines are exported.. Export table EVT_CARRIER_CONFIGURATION 0 line is exported. .. Export.... Job queue. Export refresh groups and subgroups are derived without warning.
3. Data Import In the NT server, the exported output is converted to binary file expdat.dmp (using the Binary Transmission Operation Method to Import $ IMP GXMISDBA / Manager file = / expdat) .dmp full = y log = u01import.log Connected to: Oracle8 Enterprise Edition Release 8.0.4.0.0 - Production PL / SQL Release 8.0.4.0.0 - Production Export file created by EXPORT: V08.00.05 via conventional path importing GXMISDBAs. objects into GXMISDBA importing table "AAAAA" 0 rows imported importing table "EVT_CARRIER_CONFIGURATION" 0 rows imported importing table "TBL_AJ_STK" 331 rows imported IMP-00017:...... following statement failed with ORACLE error 2437: "ALTER TABLE" TBL_KJ_JLRY "ADD CONSTRAINT" PK_TBL_KJ_JLRY "PRIMARY KEY (" FLD_KJ_JLRY_BH "," FLD_KJ_JLRY_XM ") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE (INITIAL 10240 NEXT 10240 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 50 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)" "ENABLE NOVALIDATE" IMP-00003: Oracle Error 2437 Encountered ORA-0243 7: cannot enable (gxmisdba.pk_tbl_kj_jlry) - Primary key violated.. Import Terminated successfully with warnings. Data imports more than 20 similar errors, post-analyzing the "TBL_AJ_STK" table in which an error is reported, discovers the "FLD_KJ_JLRY_XM" field value (key One of the words consists of "FLD_KJ_JLRY_XM" field value in the Digital UNIX server Oracle database is displayed as "????" (viewed by Oracle SQL Plus), resulting in Oracle SQL Plus A line displays the field value of "????" to modify, if you change to the Chinese value "test", after submit, use the SQL statement to view the field value of "????" in the row of "????" becomes "Test", this shows that the Oracle dataset on the Digital Unin server can store Chinese characters, but Oracle 8.0.4 for Digital Unin's import tool IMP does not convert the Chinese data exported by Oracle 8.0.5 for Windows NT IMP80.
4. View character set parameter 4.1 View Oracle 8.0.5 for Windows NT Props $ Content Name Value $ --------------------------- ---------- DICT.BASE 2 NLS_LANGUAGE AMERICAN NLS_TERRITORY AMERICA NLS_CURRENCY $ NLS_ISO_CURRENCY AMERICA NLS_NUMERIC_CHARACTERS., NLS_CALENDAR GREGORIAN NLS_DATE_FORMAT DD-MON-YY NLS_DATE_LANGUAGE AMERICAN NLS_CHARACTERSET ZHS16GBK NLS_SORTBINARY NLS_NCHAR_CHARACTERSET ZHS16GBK NLS_RDBMS_VERSION 8.0.5.0.0 GLOBAL_DB_NAMEORACLE.WORLD EXPORT_VIEWS_VERSION7 15 lines have been selected. 4.2 View Oracle 8.0.4 for Digital Unin PROPS $ Content SQL> Connect Sys / CHANGE_ON_INSTALL NAME VALUE $ ---------------------------- ----------- DICT.BASE 2 NLS_LANGUAGE AMERICAN NLS_TERRITORY AMERICA NLS_CURRENCY $ NLS_ISO_CURRENCY AMERICA NLS_NUMERIC_CHARACTERS., NLS_CALENDAR GREGORIAN NLS_DATE_FORMAT DD-MON-YY NLS_DATE_LANGUAGE AMERICAN NLS_CHARACTERSET ZHS16CGB231280 NLS_SORT BINARY NLS_NCHAR_CHARACTERSET ZHS16CGB231280 NLS_RDBMS_VERSION 8.0.4.0.0 GLOBAL_DB_NAME ORCL . World Export_Views_version7 15 rows selected. Discovery Oracle 8.0.4 for Digital Unin uses Oracle's recommended Chinese character set zHS16CGB231280 in the Digital UNIX environment, and the character set of the two is different, so I reinstall Oracle on the Digital Unin server, choose The same character set on NT ZHS16GBK (China's Simple Chinese Temple 16 National Tag Library). After the installation is complete, the character set of Oracle 8.0.4 for Digital Unin and Oracle 8.0.5 for Windows NT is identified by viewing the contents of the PROPS $. So use Oracle 8.0.4 for Digital Unin to re-perform data import 5. Problem solutions later I found in Oracle 8.0.5 for Windows NT server (or workstation with Oracle 8.0.5 for Windows 95/98) Directly imported the Oracle 8.0.4 for Digital Unin database directly to the Oracle 8.0.4 for Digital Unin database, and the problem is resolved. 5.1 On the NT server, modify TNSNAMES.ORA (or via Oracle Net8 Easy Config) Set the database connection string GXMIS (you can set it) points to the Oracle 8.0.4 for Digital Unin server.
