OK, with this performance problem we have to go to Oracle support.
On 2016.04.13 I wrote:
Earlier I mentioned that we had successful test with the API calls. A small C program was created. There is one question about it:
We use synchronization in both directions:
oseSetNumOption(sess, OSE_OPT_TRANSPORT_DIRECTION, OSE_SYNC_DIR_SENDRECEIVE);
There are 2 publications. When we select only one to synchronize:
oseSelectPub(oseSess sess, const char *pub)
records will be synchronized only in this publication / SQLite database.
The problem is that both databases are locked during the synchronization. Is this a bug, or we can switch off this behavior?
The question is still open: can we switch off this feature?