Question Re: SQL Anywhere Problem with proxy in Technology Q&A

SQL Anywhere Problem with proxy

roy_bungert — Thu, 09 Jul 2026 10:29:53 GMT

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

Re: SQL Anywhere Problem with proxy

VolkerBarth — Thu, 09 Jul 2026 12:18:12 GMT

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.)

Re: SQL Anywhere Problem with proxy

roy_bungert — Thu, 09 Jul 2026 12:58:04 GMT

Hi Volker

Usually the proxy-DB dies a sudden death without any notification. But I never looked at the console log of the main-DB. I will try it.

Re: SQL Anywhere Problem with proxy

chris_keating — Thu, 09 Jul 2026 20:44:58 GMT

If you have access to support, you might want to collect the crash dump from the diagnostic directory and open support case. It is most likely going to be found in %ALLUSERSPROFILE%\SQL Anywhere 17\diagnostic. Please refer to https://help.sap.com/docs/SAP_SQL_Anywhere/61ecb3d4d8be4baaa07cc4db0ddb5d0a/813e27e76ce210148bcad4e46a79b31f.html?locale=en-US&state=PRODUCTION&version=17.0.01#remarks which outlines where the directory might be located.

Re: SQL Anywhere Problem with proxy

roy_bungert — Fri, 10 Jul 2026 07:32:11 GMT

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

Re: SQL Anywhere Problem with proxy

jack_schueler — Fri, 10 Jul 2026 14:45:33 GMT

Re: But I never looked at the console log of the main-DB. I think the suggestion was to look also at the console log of the proxy-DB. You could enable request level logging for the proxy-DB. That will place a lot of output in the console log but it should help you see what was happening at termination.

Re: SQL Anywhere Problem with proxy

roy_bungert — Fri, 10 Jul 2026 15:15:23 GMT

Thank you. I enabled request level logging for the proxy-DB and wait for the next stop.