Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-01-18 : 00:55:11
|
John writes "I'm running SQL 7.0 SP3 on windows 2000 advanced server.
When aborting a multi-database operation via the C++ ITransaction interface, the following error is sometimes reported in the Application Log:
Error 3314, Severity 21, State 4
Error while undoing logged operation in database XYZ.
Error at log record id [7:469:2]
The log for XYZ is not available
The operation is indeed aborted ie none of the operations were applied to the databases.
It seems that the order in which the databases are enlisted into the transaction can make a difference. For example, I have two databases, A and B. I begin a transaction (via the C++ OLEDB interfaces), enlist A, enlist B, execute a command in both databases, abort the transaction and then unenlist A, unenlist B. This causes the error. If I reverse the order of enlisting (ie enlist B, enlist A), I do not get the error when aborting.
It also seems to be database-dependent. On some databases I never see this error. I've re-created the databases from scratch thinking that maybe there was a glitch in the way the databases were created, but I still get the error.
Any insight you might have would be appreciated...Thanks!" |
|
|
|
|
|
|
|
Transaction Log errors during multi-database transactions