|
Hi, I have a remote database which was participating in synchronization using Mobilink, for performance reasons we need to rebuild this database (using dbunload), so that I will loose the transaction log files. Question: how can I re bring this rebuilded database into synchronization so that it continues from the same point of last synchronization? Thanks in advance |
|
Here's a how-to: http://dcx.sap.com/index.html#sa160/en/dbusage/wrtluu.html . Note, it will only work if you have not yet rebuilt the database normally. the link is not available, I get 404 error!! is there any alternative? what you mean with the note? do you mean that I should do the steps before rebuilding the database?
(22 Mar '17, 06:05)
Baron
Replies hidden
Sorry, I have corrected the link. These are the steps to rebuild a syncing database. If you have already rebuilt the database without following these particular steps, I fear they won't work now. But you should follow this topic to understand what the particular steps have as affect (I.e. keeping the log offsets "right").
(22 Mar '17, 06:56)
Volker Barth
Thanks for the reply, what is meant exactly with line 3? Starting Offset: Does this mean the minimum offset (on the first line of log file)? Ending Offset: Does this mean the maximum offset (on the last line of log file)? I see several offets (some with COMMIT, others with sql commands), so should I consider only the lines with COMMIT or absolute the first/last lines? Is there some source for better understanding the logic of offsets and truncations? Thanks
(22 Mar '17, 08:57)
Baron
Replies hidden
1
Sorry for the late response... I guess the next doc topic does answer your questions (and shows how to retrieve that value with DBLOG): Rebuilding databases involved in synchronization or replication (manual) It's the ending offset of the previous active transaction log that must be set for the rebuilt database, and the new TL must then "officially" begin with that offset.
(25 Mar '17, 07:52)
Volker Barth
|
