Constraint errors during apply on destination site

Question

We are trying to acheive replication between two sites. we have about 100+ tables with parent child relationships with one key being present in almost all the tables.
The same database schema is installed on both the m/c.
When i execute a transaction on the first m/c that covers about 50-60 tables, it reaches the apply of the second and gives "constraint errors" for many tables. However, some tables having a similar structure go thru, but the transaction does not commit.
To make it proceed,i used to disable the constraint after every reported constraint. This way, i could go far ahead (just to check), but got stuck in a "No data found" error.
I do not have any DML handlers installed.
The question is that if both the sites have identical schemas with same constraints, if the transaction could go thru fully on the first, why does it give constraint errors at the second.
We have tried all these on a single/two table scenario and everything worked like a charm.
It could be some mistake on my part, but could someone give me any pointers where to look.

Answer 1

It would be helpful to know what kind of constraint failures you are getting.
When dealing with foreign key constraints, be sure to make them deferrable constraints. At the apply site, the ordering is by transaction so individual LCRs within a transaction are not guaranteed to be performed in the same order as at the source site.
Check your supplemental logging to ensure that you are logging the appropriate columns.