Hi Folks,

an application i am using requires Sybase SQL Anywhere 7. Since a few
days, the system welcomes me with the following dialog box:
Internal database error *** ERROR *** Assertion failed: 201117
Attempt to close a file marked as dirty -- transaction rolled back
As you may expect, the corresponding application does not work
anymore...
and unfortunatly i don't have a recent backup of the database.
Do you have any ideas how to repair the database?

Please let me know if you have any ideas and
thanks in advance!

Hi again,
is there realy no way to fix that problem?
I'm completly new to sql anywhere, so any (even basic) hit is
appreciated.

Thanks anyway...

Hi again,
as described at http://www.sybase.com/detail?id=1010805, i've:
1. renamed the original (damaged) transaction log and
2. forced the database server to start after the transaction log has
been lost, using the -f option at the command dbeng7.
Now the database seems to be up and running again.
The only question that remails is:
All the data, entered at the day at which the system crashed are
obviously lost, but may other data also be affected/altered by the
rollback?
If i understand it right, only the data from the transaction log is
lost but the database itself is still valid and unaltered. Am i right
with this assumption?
I wonder if somebody's able to enlighten me this time...
Thanks in advance anyway.