Following was the error observed in one of our embedded sybase DB ERROR Assertion failed: 100910 (10.0.0.2465) Error deleting transaction log file
Could you please let me know the possibilities why it was trying to rename/delete the transaction log file ? There is no -m option used.Neither any db backup is also running
Following is the script for DB startup
start /D "<<path>>" dbsrv10.exe -qs -x tcpip(BroadcastListener=NO;host=XXX;port=8080) -qi -o "<<log file="" path="">>" -on 2m -n <<server name="">> "<<db name="">>"
asked 03 Jan '14, 09:18
This assertion means that your transaction log file is corrupted due to a bug that was fixed on 2003 Dec. 19 - CR #341887 (i.e. more than 10 years ago).
Under certain circumstances, rows inserted by means of the wide insert facility can contain string values that are longer than the maximum imposed by the definition(s) of the underlying column(s). In other words, the server can fail to truncate inserted column values, as necessary. The un-truncated values are inserted in both the database and the transaction log. Under normal circumstances, the user is not likely to notice any problems with the database because the values are properly truncated when they are read back later. However, the un-trancated values in the transaction log can impose problems for utilities that need to translate and/or replicate the operations from the transaction log. In order for the corruption to occur a wide insert with the following characteristics must take place for one or more columns: 1. The column value in the first row must contain be NULL, 2. A subsequent row must contain a string value that does not exceed the maximum size allowed for the column, and 3. The above must be followed at some point by a row containing a column value that needs to be truncated before insertion. This problem has now been fixed. A new server assertion ( number 100910 ) has been added to prevent this corruption from happening in the future.
You will need to rebuild your database.
I'll add that this assertion has long been removed from the software (in v11).
There are only a few times during operation we attempt to 'delete' the log file during database operation.
What other utilities do you have running on this system that may be touching the transaction log - virus scanners? Third-party backup software? Security auditing software?
You can use the Microsoft Sysinternals Tool 'Process Monitor' to scan for other processes touching the transaction log. (e.g. Filter » Filter... »