Attunity Replicate task when first created, it will be in stopped status. You will have have two options to start the brand new replication task. We will go over all these options and explain when we pick these options correctly and prevent data loss.
- Start Processing:
- Advanced Run Options:
Start Processing: This option is presented when you are starting the Attunity task for the first time since you developed this task. This option later get divided into two options after the jobs is started. When picking this option, it will do the full load of target and then start running the CDC if enabled.
Advance Run Options: This options will let you go back and start from the time you want to start it as long as the transaction logs are available. You will be asked with an option to punch in the date and time from where you want to start your replication. This option will let you skip full reload of data if that is not required as part of your requirement.
When the job is paused or stopped , you will be presented with three options to start back up. The options are not the same as in brand new replication task.
- Resume Processing:
- Reload Target:
- Advanced Run Options:
Resume Processing: Resumes task execution from the point that it was stopped. This options will go back to the date and time that it was stopped and start capturing the CDC from that time. This options is the highly used option during the maintenance of database where you are required to stop and resume processing task without losing any data.
Reload Target: Starts the Full Load and Change Processing (if enabled) from the beginning.This will options will clear all the logs, truncates target tables and starts running a full load on target tables. If the schema or a filter was changed after the task stopped, the task should
be reloaded as opposed to resumed. This options should be use with caution, this will truncate data if the truncate is enabled else it will append data.
Advance Run Options: This options will let you go back and start from the time you want to start it as long as the transaction logs are available. You will be asked with an option to punch in the date and time or current time from the server, or SCN or LSN from where you want to start your replication. This option will let you skip full reload of data if that is not required as part of your replication. Using date/time or current time to advance run is self explanatory but you SCN and LSN is not.
Specify the position in the log
from where to resume change processing. The source change position format
differs according to your source endpoint.
Some examples are as follows:
- Microsoft SQL Server - Specify the LSN (e.g. 000000c1:00001d6f:0004).
- Oracle - Specify the SCN (e.g. 10737419121).
- IBM DB2 for z/OS - Specify the LSN, which is the RBA in a non data sharing environment, and the LRSN in a data sharing environment.
Note The Source change position option is supported with the following
source endpoints only:
Oracle, Microsoft SQL Server, MySQL, PostgreSQL, SAP HANA with log-based
CDC, and IBM DB2 for z/OS.
It is very important that you understand these options so you pick them wisely and not lose any data when selecting these options. Enjoy replicating data using Attunity!!
Interested in working with me? I can be reached at pbaniya04[at]gmail.com for any questions, consulting opportunities or you may drop a line to say HELLO. Thank your again for visiting my blog and looking forward to serving you more.
Have a Database-ious Day!
Have a Database-ious Day!
This is very good explanation of the replicate process, nice to see someone writing on replicate topic
ReplyDelete