Symptom
- Your dbmlsync shows the following output and doesn't progress any further. Each dbmlsync run has the same "Log scan starting at offset xxxxx" message shown:
I. 2016-08-02 15:41:46. Begin synchronizing subscription(s) 'sample_sub'
I. 2016-08-02 15:41:46. Log scan starting at offset 0915872257377
I. 2016-08-02 15:41:46. Processing transaction logs from directory "C:\DemoDB\"
I. 2016-08-02 15:41:46. Processing transactions from active transaction log
- In some occasions, the following error messages are reported:
I. 2016-08-01 18:03:03. Begin synchronizing subscription(s) 'sample_sub'
I. 2016-08-01 18:03:03. Log scan starting at offset 0915872257377
I. 2016-08-01 18:03:03. Processing transaction logs from directory "C:\DemoDB\"
I. 2016-08-01 18:03:03. Processing transactions from active transaction log
E. 2016-08-02 05:26:30. Connection was terminated
E. 2016-08-02 05:26:30. Upload aborted at offset 0915872257377
E. 2016-08-02 05:26:30. SQL statement failed: (-308) Connection was terminated
E. 2016-08-02 05:26:30. SQL statement failed: (-101) Not connected to a database
I. 2016-08-02 05:26:30. Synchronization completed
E. 2016-08-02 05:26:31. SQL statement failed: (-101) Not connected to a database
- If there are renamed offline logs, errors could look like the following:
I. 2016-08-02 19:49:40. Begin synchronizing subscription(s) 'sample_sub' I. 2016-08-02 19:49:40. Log scan starting at offset 0915872257377 I. 2016-08-02 19:49:40. Processing transaction logs from directory "C:\DemoDB\" I. 2016-08-02 19:49:40. Transaction log "C:\DemoDB\160802AA.LOG" starts at offset 0914719625710 I. 2016-08-02 19:49:40. Processing transactions from transaction log "C:\DemoDB\160802AA.LOG" I. 2016-08-03 19:40:24. Transaction log ends at offset 0916881323256 I. 2016-08-03 19:40:25. Transaction log "C:\DemoDB\160802AB.LOG" starts at offset 0916881323256 I. 2016-08-03 19:40:25. Processing transactions from transaction log "C:\DemoDB\160802AB.LOG" I. 2016-08-03 19:40:38. Transaction log ends at offset 0917180723027 I. 2016-08-03 19:40:38. Processing transactions from active transaction log E. 2016-08-03 19:40:38. Connection was terminated E. 2016-08-03 19:40:38. Upload aborted at offset 0917180722993 E. 2016-08-03 19:40:38. SQL statement failed: (-308) Connection was terminated E. 2016-08-03 19:40:38. SQL statement failed: (-101) Not connected to a database I. 2016-08-03 19:40:38. Synchronization completed E. 2016-08-03 19:40:38. SQL statement failed: (-101) Not connected to a database
- Readings from Task Manager indicate there are activities going on (i.e. I/O Read Bytes and I/O Write Bytes increase).
Read more...
Environment
- SAP Sybase SQL Anywhere 12
- Windows OS - Any supported versions
Product
SAP Sybase SQL Anywhere 12.0
Keywords
anyhwere, asa, connection, timeout, blob, performance, IdleTimeout, disconnect, disconnected , KBA , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.