cdr migrate server

• Static mode-offline data migration
  • Create storage spaces using storage pool
  • Migrate schema (except referential integrity) and data in parallel
  • Build referential integrity
• Dynamic mode – online data migration
  • Create storage spaces using storage pool
  • Migrate schema (except referential integrity) and data in parallel
  • Resynchronize data using Enterprise Replication
  • Build referential integrity

The cdr migrate server command automates tasks such as:

• Define Enterprise Replication domain between the two servers.
• Add ERKEY columns for the tables that does not have primary key or unique index columns.
• Create required storage spaces for the databases
• Apply database schema from source server to target server
• Create replicate definitions
• Synchronize data between source and target server instances
• Build referential integrity

1. define_er: Define ER
2. 1. add_erkey: Add ERKEY to source schema
   2. add_replcheck : Add REPLCHECK column and index to source schema
3. create_spaces: Create storage spaces using storagepool
4. 1. create_schema_loaddata: Multi phase replay of schema and data
      • Phased migration of schema and data:
        • Phase 1:
          • Migrate database schema except indexes, primary key, unique and referential constraints
          • Create all tables as “RAW" tables
        • Phase 2:
          • Start multiple parallel jobs for data load and index builds
          • Each job includes: make sure table is a raw table, Load data using “insert into … select * from …�? ISTAR query, Build indexes, primary key and unique key constraints
        • Phase 3:
          • Build referential constraints
   2. create_schema_nodata : Create database schema
   3. create_schema_loaddata_nori : Create database schema without referential integrity and load data
5. create_replicates: Create replicate, replicate set and grid definitions
6. sync_data: Synchronize data
7. add_ri: Add referential integrity
8. all: Execute all phases (with phase create_schema_loaddata_nori)
9. static: Execute create_spaces and create_schema_loaddata phases
10. dynamic: Execute all phases similar to ‘all’

If you decide to execute the above phases individually, then phase order need to be maintained.

1. To auto create required storage spaces, storage pool is a requirement at source and target servers.
2. SQLHOSTS files at both source and target server must be already configured with ER group information.
3. Trusted host configuration must be already established between source and target servers.
4. Source server must be 11.70xC1 or higher version.

1. Cannot mix multiple database code-sets in same data migration command.
2. Parallel data load using ISTAR query do not support tables with smart large objects(BLOB and CLOB), user created UDTs and collection datatypes.
   • Requires customization to unload/load data using external tables or using any other supported unload/load commands.
3. Tenant databases and database sharding are not supported.
4. Cannot use this tool for database code-set migration

cdr migrate server -s source -t target -p phase [-d database] [--exec]