Re: Delayed replication of 4 hours and no delay?
nitpick: You mentioned the term 'standby' which often times can indicate the replicate database in a warm standby configuration. A warm standby configuration can only have a single replicate database...
View ArticleRe: Delayed replication of 4 hours and no delay?
In addition what Mark wrote:In the simplest setup you would create a database replication definition for the primary database and then two database subscriptions - one subscription for each replicate...
View ArticleRe: Delayed replication of 4 hours and no delay?
I would suggest configuration using "Warm Standby" for production server and standby server (that with no delay) and based on created logical connection (configuration of two servers in "Warm Standby"...
View ArticleRe: sybase replIcation failover - hibernation mode
Dear All, I have tried sysadmin hibernate_off it doesnt work. as it was test setup i decided to build up again but with RS 15.7.1 SP200 , is it ceritied by SAP ? RegardsMohammad
View ArticleRe: Delayed replication of 4 hours and no delay?
I would like to add that using traditional "warm standby" might not satisfy the requirements, if the desire is to be able to also fail-over to the delayed copy. If the delayed copy is never to become...
View ArticleRe: Delayed replication of 4 hours and no delay?
Guys, thank you for your quick responses and and invaluable help!
View ArticleRe: sybase replIcation failover - hibernation mode
Hi Mohammed, No, I do not think SAP has certified SP200 with Business Suite for ASE. SP200 begins to support some new ASE 16.0 features - which require additional certification (both RepServer and ASE...
View ArticleRe: sybase replIcation failover - hibernation mode
Hello Stephen, Thanks , I have started setting up replication environment but installation master end up saying version not recognized. SWPM used is latest one (SWPM10SP05_2-20009707.SAR) any ideas...
View ArticleRe: sybase replIcation failover - hibernation mode
Hi Mohammad, Sorry - I should have thought of that - the SAP installer will not recognize the SP200 version for Replication Server or DR Agent. (As we identified - SP200 is not certified, which ends...
View ArticleRe: Delayed replication of 4 hours and no delay?
Mark A. Parsons wrote: I thought I'd seen Luc Van der Veurst do a write-up on an environment where he'd replaced all of his warm standby configs with MSA configs ... and how he was able to perform his...
View Articlewarm standby synch up
i have a question regarding sybase replication warm standby sync up and appreciate the clarification. let us suppose in a warm standby setup, the standby data has gone out of sync with the primary...
View ArticleRe: warm standby synch up
Think of the entries in the transaction log as being in single file, eg, 1,2,3,4,5 ... The dump marker (DM) is placed into the transaction log along with the transactions, eg:...
View ArticleRe: warm standby synch up
mark, thanks for the reply. so just to be clear : dump/clear the transaction log and zeroltm is not mandatory for warm standby resync? you can simply take the dump of the primary and load it into the...
View ArticleRe: warm standby synch up
No need to clear the PDB log or run rs_zeroltm. There should be no genid issues because you aren't rolling the PDB back to an earlier point in time. As for 'simply take the dump of the primary and load...
View ArticleRe: warm standby synch up
mark, btw not sure if you noticed the question about uncommitted transactions before the dump marker. appreciate your clarification on that. >and if transaction 7 and 8 are open transactions - for...
View ArticleRe: warm standby synch up
1 - Uncommitted txns in the dump file will be rolled back upon loading in the RDB. 2 - Repserver plays transactions against the RDB in the order in which they were committed (not the order in which...
View ArticleRe: warm standby synch up
ok mark, but when the commit (post dump marker) comes in through the DSI, will the replicate dataserver have access to the original transaction (which was rolled back)? is there a transaction id or...
View ArticleRe: warm standby synch up
Each transaction has a unique oqid, which consists of the gen id, source database info, etc, etc, etc. When a transaction is successfully applied/committed in the RDB the local rs_lastcommit table is...
View ArticleRe: warm standby synch up
oqid is used in replication - using the dbgenid, timestamp of log page, transaction id etc. but we are talking about the uncommitted transactions in the database dump and how they are reconciled...
View ArticleRe: warm standby synch up
There is no 'link' between what was rolled back (from the db dump) and what actually shows up later as a committed transaction that's applied via the DSI. What comes across in the db dump is an...
View Article