ER Replication question
Posted in 2011
Topics: High Availability & Replication
IDS11.5FC7 We have been running replication on IDS10 for quite some time with no problems. Recently, we moved one of our databases to new servers with IDS 11.5. I am constantly seeing ATS failures on these new servers. It looks like the CDR process is trying to post child records before the parent record (SQL error -691). when I go back in to check on the records (soemtimes almost immediately) I can see that the parent record is now on the target server... so I do a repair on the ATS file and the child record will post too. My question is... shouldn't IDS know about fk relationships and post the records in order? Is there something I need to do to make sure this one table gets replicated before all the rest? I have the replicates in the same replicate set and even tried using an exclusive set but I am still seeing alot of errors. Certainly, I must be missing something. Any insight is appreciate. Laurie Laurie Gustin IT Programmer Analyst Department of Public Safety lgustin@utah.gov 801-965-4410
Yes, ER should be applying serially when there are referential constraints involved. The code to manage that has been in place since 9.3. My guess is that there was some kind of problem when we generated the RI apply ordering structures. You could try to run 'cdr stop' followed by 'cdr start' on the server having the problems to cause ER to refresh the RI apply order rules From: "Laurie Gustin" <lgustin@utah.gov> To: ids@iiug.org Date: 01/27/2011 09:43 AM Subject: ER Replication question [22606] Sent by: ids-bounces@iiug.org IDS11.5FC7 We have been running replication on IDS10 for quite some time with no problems. Recently, we moved one of our databases to new servers with IDS 11.5. I am constantly seeing ATS failures on these new servers. It looks like the CDR process is trying to post child records before the parent record (SQL error -691). when I go back in to check on the records (soemtimes almost immediately) I can see that the parent record is now on the target server... so I do a repair on the ATS file and the child record will post too. My question is... shouldn't IDS know about fk relationships and post the records in order? Is there something I need to do to make sure this one table gets replicated before all the rest? I have the replicates in the same replicate set and even tried using an exclusive set but I am still seeing alot of errors. Certainly, I must be missing something. Any insight is appreciate. Laurie Laurie Gustin IT Programmer Analyst Department of Public Safety lgustin@utah.gov 801-965-4410 ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
Thanks Madison! so far things are looking better. Thanks! Laurie >>> "Madison Pruet" <mpruet@us.ibm.com> 1/27/2011 8:55 AM >>> Yes, ER should be applying serially when there are referential constraints involved. The code to manage that has been in place since 9.3. My guess is that there was some kind of problem when we generated the RI apply ordering structures. You could try to run 'cdr stop' followed by 'cdr start' on the server having the problems to cause ER to refresh the RI apply order rules From: "Laurie Gustin" <lgustin@utah.gov> To: ids@iiug.org Date: 01/27/2011 09:43 AM Subject: ER Replication question [22606] Sent by: ids-bounces@iiug.org IDS11.5FC7 We have been running replication on IDS10 for quite some time with no problems. Recently, we moved one of our databases to new servers with IDS 11.5. I am constantly seeing ATS failures on these new servers. It looks like the CDR process is trying to post child records before the parent record (SQL error -691). when I go back in to check on the records (soemtimes almost immediately) I can see that the parent record is now on the target server... so I do a repair on the ATS file and the child record will post too. My question is... shouldn't IDS know about fk relationships and post the records in order? Is there something I need to do to make sure this one table gets replicated before all the rest? I have the replicates in the same replicate set and even tried using an exclusive set but I am still seeing alot of errors. Certainly, I must be missing something. Any insight is appreciate. Laurie Laurie Gustin IT Programmer Analyst Department of Public Safety lgustin@utah.gov 801-965-4410 ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.