SA12 dbremote errors

[VolkerBarth]

We are currently experiencing issues with dbremote running on remote databases. Replication has been running for months without issue but now we are getting the database locking up and dbremote failing to run. Dbremote seems to lose connection while processing files:

I. 2013-11-11 17:43:29. UPDATE shipclip.NIIN
                           SET FSC=NULL,
                               COG=NULL,
                               DESCR=NULL,
                               UNIT_PRICE=224.08,
                               BRF=NULL,
                               UOM=NULL,
                               AAC=NULL,
                               SLC=NULL,
                               SLAC=NULL,
                               NET_PRICE=NULL
                        VERIFY (FSC,COG,DESCR,UNIT_PRICE,BRF,UOM,AAC,SLC,SLAC,NET_PRICE)
                        VALUES ('4820','9B','SEAT,VALVE',222.21,.25,'EA','Z','0','00',0)
                         WHERE NIIN='012090384'
E. 2013-11-11 18:02:07. SQL statement failed: (-85) Communication error
E. 2013-11-11 18:04:08. SQL statement failed: (-832) Connection error: Shared memory connection to server timed out
E. 2013-11-11 18:04:08. Error connecting to database
E. 2013-11-11 18:04:08. SQL statement failed: (-101) Not connected to a database
E. 2013-11-11 18:04:08. SQL statement failed: (-85) Communication error
E. 2013-11-11 18:04:08. Communication error (-85)
E. 2013-11-11 18:04:08. SQL statement failed: (-85) Communication error
E. 2013-11-11 18:04:08. Communication error (-85)
E. 2013-11-11 18:04:08. SQL statement failed: (-101) Not connected to a database
I. 2013-11-11 18:04:08. Shutdown by request
I. 2013-11-11 18:04:08. Execution completed
I. 2013-11-11 19:02:43. SQL Remote Message Agent Version 12.0.1.3750

[VolkerBarth]

You may try to add the LOG=filename connection parameter to DBREMOTE's connection string to get debug information on connection issues.

You also might use sa_conn_info() and sa_locks() in a DBISQL session to try to find out whether the operations from SQL Remote are blocked by concurrent OLAP transactions...

---

If this is a blocking issue, have you set individual values for the BLOCKING and BLOCKING_TIMEOUT options, or are they used with their default values (ON and 0, meaning infinite waiting on blocks to be released)?

[regdomaratzki]

Does the database engine log have any entries from around the same time to indicate what might have happened?

[Former Member]

Are you modifying the SUBSCRIBE BY values for an article when this happens?

[Former Member]

We have pulled the remote database from the remote server and currently running the database on a stand-alone server with no other connections but the dbremote replication and still getting the same errors.

The database stops and dbremote ends after 1 update statement.
BLOCKING and BLOCKING_TIMEOUT options are default

[regdomaratzki]

re: "the database stops"

Does the database engine log have any entries from around the same time to indicate what might have happened?

Did the database engine crash and generate a mini-dump file?