on 2015 Jun 23 10:06 AM
Hi All,
when ever my sqlanywhere client db crashes , i dont get any crashdump or any log file in powerbuilder 10.0 application.
is there a way to enable the logs and crash dump.badly i need for help . unable to figure out how and why my application crashes. the crashes started happening after migrating application to WINDOWS 2008 R2. it was not happening in windows XP machine.. thanks in advance
Request clarification before answering.
Dbeng50.exe is very old and no longer supported... and AFAIK it never produced a crash dump file.
Before migrating to Windows 2008 R2, did you check to see if your software is supported on it? Because SQL Anywhere 5 is not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
...and AFAIK some folks have reported that SQL Anywhere 5 does not run stable on Windows 7 and above, cf. that FAQ search...
HERE IS WHAT TO DO...
Steps to fix the transaction log
Stop the service from Sybase Central.
Move the existing log file that is tied to the database to a different location.
Launch a command prompt and navigate to where your SQL Anywhere databases are stored.
For example: F:\\Temp>
Type > dbeng50.exe software.db You may need to type in the full path to your dbeng50 executable if sqlany50 is not in your system path. For example: "C:\\Program Files\\sqlany50\\win32\\dbeng50.exe" dbfilename.db
Note: This step will start the database server without the transaction log for the first time.
Note: This step will fix the database server.
Note: This step will connect to the database and write a new transaction log.
Click the Shutdown button to stop the server.
Launch Sybase Central and restart the service.
Note: You can adjust the file so that it no longer uses a transaction log.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The OP was asking about diagnostic log files (like a crash dump or dbsrv50 -o text file), NOT the database transaction log file.
> You can adjust the file so that it no longer uses a transaction log.
That is very dangerous advice, and should always be accompanied by warnings about unintended consequences.
For example, the Version 5.5 Help says this about dbinit -n: "The transaction log is required for data replication and provides extra security for database information in case of media failure or system failure."
The Version 16 Help says this, and the point about performance is probably true for Version 5.5 as well: "Creating a database without a transaction log saves disk space, but can result in poorer performance because each commit causes a checkpoint. Also, if your database becomes corrupted and you are not running with a transaction log, data is not recoverable. The transaction log is required for data replication and provides extra security for database information during a media or system failure."
User | Count |
---|---|
75 | |
30 | |
9 | |
8 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.