|
Hi all, i have a ASA12 service that crashes unexcpectedly, unfortunately both -o message log and Windows 2008 event log do not show any useful info. ASA12 (build 3276) runs on a Windows 2008 R2 64 bit server with 8 GB Ram. ASA12 starts with -ch 6 GB switch. Do you know some tool/switch to capture more details in this situation ? Thanks Mark |
|
You could try: 1) allowing dbsupport to capture a crash log and submit it to SQL Anywhere development for analysis (post the submission ID here and someone may take a look at it). 2) validating your database to make sure that it hasn't been corrupted. 3) upgrading to a more recent build to see if the problem has already been fixed - this won't tell you what was causing the issue but if the problem goes away it would at least get you past the problem. In addition to Mark's suggestions, you can always open a technical support case with Sybase technical support and we can work with you to investigate the crash. We have internal tools to assist that we can provide to you for specific situations, if required.
(18 Jun '12, 15:16)
Jeff Albion
Hi all, i will try to use all your directions, i will update asap. Thanks Mark
(19 Jun '12, 04:18)
info2012
|
|
In addition to Marks suggestions you can use the following server configuration commands Turn on capturing of the most recently-prepared SQL statement for each connection. Used for the sa_conn_activity -zl Turn on logging of SQL operations. The default is NONE. -zr { all | SQL | none } Redirect request logging information to a separate file. -zo filename -zo "E:Sybase ASA 09.0Application Log FilesEmprise-DB6-ASA9 SQL Commands.log" Limit the size of the log file used for request logging. -zs size -zs 500K Specifies the number of request log file copies to retain. -zn integer -zn 1 |
