When sychronizing master detail table (both inserts) to Oracle Lite 10.2.0.2.0, we saw the following error on the mobile server administrator console:
integrity constraint violated - parent key not found
It definitely means that the foreign key constraint problem. Reviewing the table weight on our publication items, it seems they are set correctly. But the log revealed that the mobile server put the child insertion intot the queue first.
Finally, we found some clue from this post on OTN forum.
After download patch 5054276 from metalink and installed it on top of Oracle Lite 10.2.0.2.0, the problem is solved.