![]() ![]() However, if this database participates in replication or synchronization (SQL Remote, Mobilink, or Rep Server) there could be other problems to address.Īfter verifying and/or re-adjusting the location of the log files, the transaction logs should be fixed.Ģ. The error message you received suggests that the engine may have tried to recover and create a new log file.ĭoes the engine finally start? If it does start eventually and users are able to connect, the server may have resolved the problem. Note: If you do not specify a path, the log file will be searched for or created in the same directory as the database. If the log file has a path associated with it, either make sure that the relevant path exists on the new machine and the log file is in that directory, or reassign the log file path.Ĭ:\Program Files\Rational\sqlany50\win32> dblog -t d:\dbfilename.log dbfilename.db Transaction log starting offset is 0000523939 Transaction log current relative offset is 0000535186 "dbfilename.db" is using no log mirror file "dbfilename.db" is using log file "asademo.log" You can check this by running:Ĭ:\Program Files\Rational\sqlany50\win32> dblog c:\dbfilename.dbĪdaptive Server Anywhere Transaction Log Utility Version 8. Check to ensure the log file has an absolute path and the path is valid on the new machine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |