In the migration tool log, information about replicated objects is preceded by the following banner:
=== Replication Information for Database 'pdb1' ===
The following is a sample log file for a primary database named pdb1:
sp_repostandby ’pdb1’ is NONE.
If the standby status for the database is not NONE, use the standby status as described in the post-migration steps above.
sp_config_rep_agent ’pdb1’
sp_config_rep_agent requests the current RepAgent configuration. The migration tool automatically restores RepAgent configuration, and you can use this log to verify the RepAgent configuration.
Parameter name Default Config Value Run value priority 5 5 5 fade timeout 30 30 30 scan timeout 15 15 15 retry timeout 60 60 60 rs username n/a rs1_user rs1_user trace flags 0 8194 8194 batch ltl true true true rs servername n/a rs1 rs1 send buffer size 2k 2k 2k trace log file n/a n/a n/a connect database n/a pdb1 pdb1 connect dataserver n/a pds1 pds1 can batch size 1000 1000 1000 security mechanism n/a n/a n/a msg integrity false false false unified login false false falses kip ltl errors false false false msg origin check false false false short ltl keywords false false false msg confidentiality false false false data limits filter mode stop stop stop msg replay detection false false false mutual authentication false false false send structured oqids false false false send warm standby xacts false false false msg out-of-sequence check false false false skip unsupported features false false false send maint xacts to replicate false false false (28 rows affected)
This is a list of explicitly replicated tables. sybmigrate automatically restores the replication status for explicitly replicated tables, and you can use this part of the log to verify the replication status of explicitly replicated tables.
sp_setreptable Name Repdef Mode ------------------------------ ---------- t1 owner_off t2 owner_on (2 rows affected)
This is a list of explicitly replicated stored procedures. The migration tool automatically restores the replication status for explicitly replicated stored procedures, and you can use this part of the log to verify the replication status of explicitly replicated stored procedures.
sp_setrepproc Name Type Log Mode ----------------------- ------------- ----------- p1 function log_sproc p2 function log_current p3 table log_sproc p4 table log_current (4 rows affected)
This is information about the secondary truncation page. You will need the generation_id column during the post-migration steps.
dbcc gettrunc secondary_trunc_page secondary_trunc_state dbrepstat generation_id database_id database_name ltl_version ---------------------------------------------------------- 621 1 167 0 6 pdb1 400 (1 row affected) This appears to be a replicated primary database. Make sure the post processing steps for a replicated primary database are performed. Please consult the manuals for the steps that need to be performed.
The following is an example log entry if your database is a replicate database.
This appears to be a replicate database. If the pagesize is greater than 2K, make sure the post processing steps for a replicate database are performed. Please consult the manuals for the steps that need to be performed.
The following is an example log entry for an RSSD database.
This appears to be a replication system database Make sure the post processing steps for a replication system database are performed. Please consult the manuals for the steps that need to be performed
All three logs can be present for a database, since a database can list the three categories.
