04-30-2013 01:00 PM
may be you want to try the following - How to Increase Timeout Values for Synchronization - Answer ID 23416
04-30-2013 01:04 PM - edited 04-30-2013 01:31 PM
I've done that, I've extended it to 360 seconds. Will extend it to 900 seconds.
After reading that KB again, I have been adjusting databasecommandtimeout.default, but my issue occurs an hour after initialization. I'll try adjusting databasecommandtimeout.long and see if that has another affect.
05-01-2013 08:52 AM - edited 05-01-2013 08:55 AM
Sync failed after adjusting commandtimout.long to two hours, set to three to see if that makes a difference. Is there anything I can run in ACTDIAG to see why sync is hanging?
This issue is now affecting multiple remote databases.
05-06-2013 06:25 AM
Almost no files are changing, it's all object ACL, object history.
Running the report on subscriber shows that schema sync completes, but data is never sent. No other information beyond that.
Any thoughts? Did adjust filebuffersize to test.