Restoring Primary Databases

Follow this procedure for all primary databases, including the RSSD, if it is a primary database.

If the page size changes during the migration, you must also alter the rs_lastcommit and rs_threads system tables.

  1. If the original primary database had warm standby on, restore the standby status. Enter:
    sp_reptostandby database_name, status

    sybmigrate saves the standby status in the migration log of the source database.

  2. Increase the generation ID by 1. Enter:
    dbcc settrunc ("ltm", "gen_id", gen_id)

    You can view the current generation ID in the migration log of the source database.

  3. Reset the secondary truncation point:
    dbcc settrunc ("ltm", "valid")
  4. Zero the Replication Server locator value for this database. Enter:
    rs_zeroltm server, database_name
  5. If this database is an active connection in a warm standby configuration, rematerialize the standby database by dumping the primary and loading the dumps into the standby. See the Replication Server documentation for instructions.
  6. Start the RepAgent on the primary database. Enter:
    sp_start_rep_agent database_name
  7. Log in to the Replication Server and restart log transfer:
    resume log transfer from server.database
Related concepts
Postmigration Procedures
Restoring Replicate Databases
Related tasks
Amending System Tables When the Logical Page Size Changes