TT-00750
Log read encountered log record with incorrect LSN at location log_file_number.log_file_offset -- remainder of log ignored
Cause
TimesTen encountered an unexpected value while reading the log. The transaction log corruption is likely the result of a crash affecting the file system.
Action
If this error is encountered at any time other than recovery, is not the result of a crash that you believe may have affected the disk controller, or if you are concerned that durably committed information may have been lost, contact TimesTen Customer Support.
Additional Information
During recovery, the transaction log is effectively truncated at the point of the unexpected value, and the operation continues. Depending on the position of the error, some logged information may be lost. It is extremely unlikely that durable commits are lost, but it is possible on some operating systems.
TT-00750
Log read encountered log record with incorrect LSN at location log_file_number.log_file_offset -- remainder of log ignored
Cause
TimesTen encountered an unexpected value while reading the log. The transaction log corruption is likely the result of a crash affecting the file system.
Action
If this error is encountered at any time other than recovery, is not the result of a crash that you believe may have affected the disk controller, or if you are concerned that durably committed information may have been lost, contact TimesTen Customer Support.
Additional Information
During recovery, the transaction log is effectively truncated at the point of the unexpected value, and the operation continues. Depending on the position of the error, some logged information may be lost. It is extremely unlikely that durable commits are lost, but it is possible on some operating systems.
TT-00750
Log read encountered log record with incorrect LSN at location log_file_number.log_file_offset -- remainder of log ignored
Cause
TimesTen encountered an unexpected value while reading the log. The transaction log corruption is likely the result of a crash affecting the file system.
Action
If this error is encountered at any time other than recovery, is not the result of a crash that you believe may have affected the disk controller, or if you are concerned that durably committed information may have been lost, contact TimesTen Customer Support.
Additional Information
During recovery, the transaction log is effectively truncated at the point of the unexpected value, and the operation continues. Depending on the position of the error, some logged information may be lost. It is extremely unlikely that durable commits are lost, but it is possible on some operating systems.
