The last few weeks we have been seeing the following types of error, about the same time (luckily not peak) and lasting about 20 mins

Sap.Data.SQLAnywhere.SAException (0x80004005): Connection error: Timeout occurred while waiting for connection response

Sap.Data.SQLAnywhere.SAException (0x80004005): Database server not found

Sap.Data.SQLAnywhere.SAException (0x80004005): Connection error: No IP address found for Error

Today the DB server crashed (first time that has ever happened and I have used Sybase going back to 1996)

Where is the best place to start looking to track down where these errors are coming from? The error code appears to be very generic

Thanks

asked 29 Jan, 18:05

gchq's gravatar image

gchq
236151727
accept rate: 33%

Can you add LOG=<file_spec> to the connection string for client side connection debugging and add -z -o <filespec) the the server startup. You can also configure the server option by using sa_server_option() procedure to set DebuggingInformation (-z) and the ConsoleLogFile (-o).

Do you have any insight into what the server is doing at the time that this occurs given that it occurs about the same time each day? Do you have an event or other schedule task?

If you have a support, please consider opening an incident so that we can look into this topic in more detail.

(29 Jan, 18:59) Chris Keating

Chris

Thanks for the reply

Then I just add this to the end of the string ...;PrefetchBuffer=8192; LOG=SomeFileName"?

Where will client side logging be saved to? Do I need to add an extension to the file name (.log, .txt...)? Is both client side and server side required? (We can only restart the DB server once a month when the host machine updates are applied and it's rebooted)

(29 Jan, 19:23) gchq

When troubleshooting connectivity, it is best to get logs from both client and server. The file name is user defined and has no specific naming requirements. I suggest providing a full path to avoid any issues with were the file is created. As noted, you do not need to restart the server - in that case, use the sa_server_option procedure to enable the debug logging and if needed the log file (if there is not an -o option being used).

call sa_server_option( 'DebuggingInformation', 'Yes' ); call sa_server_option( 'ConsoleLogFile', '<filespec>' );

When the problem is captured, you can turn off this logging as follows:

call sa_server_option( 'DebuggingInformation', 'No' ); call sa_server_option( 'ConsoleLogFile', '' );

Note: ConsoleLogFile should only be set if the engine is not already using -o. If that is already used, the debug information will be directed to that location.

(29 Jan, 20:46) Chris Keating
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×158

question asked: 29 Jan, 18:05

question was seen: 85 times

last updated: 29 Jan, 20:46