SQL Anywhere Problem with proxy

[VolkerBarth]

We have a very strange problem with the use of proxy tables.

We run two databases in two different instances (dbsrv17.exe) at the same server.

One of them is the main-DB, the other the Proxy-DB. In that Proxy-DB we defined the access to some tables of the main-db via proxy. (ODBC / TCPIP)

Everything runs well. But 1 to 3 times a day the proxy-db stops running without any message. In the event log of the server there’s an entry with eventid 7034 and the message

“Service “SQL Anywhere – proxydb “ was finished unexpected. This already happened x times.”

After this happened we must restart the db-service of the Proxy-DB.

Any idea?

Server Version: 17.0.11.8360

Windows 2022 Build 20348

ODBC 17.0.11.8360

RAM: 32 G

Main-DB: -ch 16G

Proxy-DB: -ch 6G

Kind Regards

Roy

[VolkerBarth]

Do you use a console log (dbsrv -o ...) on both server instances, and if so, what does it tell around the time the second database server crashes?
You might also use a database event of type "Disconnect" to track disconnects and their reason. Of course, if the database server crashes, it might not tell about the reason...
I do assume your application(s) do connect to both databases. Is there a chance the connection to the main database blocks access within the proxy database to the linked main-db tables? (Although I would expect that these deadlocks would be detected and solved automatically.)

[roy_bungert]

Hi Chris

I wanted to submit the dump via dbsupport but I got the message that the dump can't be send /received.

The dump file itself can't be transferred to this forum, only the log file. Is there another way to send the dump? Perhaps per mail? 

Thanks

Roy

SA17_20260709_124834_7288.crash_log.txt