2337155 - SQL Remote intermittently fails to send messages | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2337155 - SQL Remote intermittently fails to send messages

Symptom

  • You see the following message while running SQL Remote Message Agent (dbremote) with -v verbose switch:
I. 2016-02-29 13:02:09. COMMIT
I. 2016-02-29 13:02:09. Sending message to "G080" (1-050151928772-050151938041-0)
I. 2016-02-29 13:03:32. Sending message to "G080" (1-050151938041-050152291226-0)
I. 2016-02-29 13:03:32. sopen "T:G080t04.1m7" failure 64: Invalid argument
I. 2016-02-29 13:03:32. sopen "T:G080t04.1m8" failure 64: Invalid argument
I. 2016-02-29 13:03:32. sopen "T:G080t04.1m9" failure 64: Invalid argument
I. 2016-02-29 13:03:32. sopen "T:G080t04.1ma" failure 64: Invalid argument
I. 2016-02-29 13:03:32. sopen "T:G080t04.1mb" failure 64: Invalid argument
E. 2016-02-29 13:03:32. Error sending message
I. 2016-02-29 13:03:32. Resend requests are being queued
I. 2016-02-29 13:04:40. Execution completed
  • On a next run, you see the following message with starting offset "stuck" (050151938041 in the example):
I. 2016-02-29 14:35:09. Processing transactions from active transaction log
I. 2016-02-29 14:35:10. Sending message to "G080" (1-050151938041-050152294405-0)
I. 2016-02-29 14:35:10. sopen "T:G080t04.1m7" failure 3: No such file or directory
I. 2016-02-29 14:35:10. sopen "T:G080t04.1m8" failure 3: No such file or directory
I. 2016-02-29 14:35:10. sopen "T:G080t04.1m9" failure 3: No such file or directory
I. 2016-02-29 14:35:10. sopen "T:G080t04.1ma" failure 3: No such file or directory
I. 2016-02-29 14:35:10. sopen "T:G080t04.1mb" failure 3: No such file or directory
E. 2016-02-29 14:35:10. Error sending message
I. 2016-02-29 14:35:10. Resend requests are being queued
I. 2016-02-29 14:35:10. Hovering at end of active log
I. 2016-02-29 14:36:16. Execution completed
  • Any subsequent runs generate same error messages with transaction log's ending offset increased
  • dbremote appears to work after few hours later and report insert/delete/update from the same stuck starting offset
I. 2016-02-29 17:04:17. Scanning logs starting at offset 050151938041
I. 2016-02-29 17:04:17. Processing transaction logs from directory "c:\vs_pos\"
I. 2016-02-29 17:05:15. Processing transactions from active transaction log
I. 2016-02-29 17:05:31. Sending message to "G080" (1-050151938041-050155323926-0)
I. 2016-02-29 17:05:31. Hovering at end of active log
  • As result, you lost some of the transactions

Read more...

Environment

  • SAP SQL SQL Anywhere - all supported versions
  • Sybase SQL Anywhere - all supported versions
  • SQL Remote
  • SQL Remote message files stored on a mapped drive
  • Any supported Microsoft Windows OS

Product

SAP SQL Anywhere all versions ; SQL Anywhere all versions

Keywords

anyhwere, asa, synchronization, synchronizes, synchronizing, missing file, disconnect, mapped drive, network, NET USE, connectivity, connection, Windows, system, code , 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 ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.