Red Gate forums :: View topic - The Notable Timeout Expired Problem
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Log Rescue
SQL Log Rescue forum

The Notable Timeout Expired Problem

Search in SQL Log Rescue forum
Post new topic   Reply to topic
Jump to:  
Author Message
acorcoran



Joined: 13 Nov 2006
Posts: 7

PostPosted: Mon Nov 13, 2006 7:52 pm    Post subject: The Notable Timeout Expired Problem Reply with quote

We're running a licensed version of the latest version of SQL Log Rescue and are having some troubles in our most critical time Smile (Murphy's Law). On smaller databases (50MB), I am able to run the Log Rescue (Analysis, etc). When I jump up to intermediate (in our standards) of a 500MB database, I get the famous "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding." This happens during the Analysis phase.

Our C: has 13GB free, so running this on the 500MB database should not be an issue. I've even pointed the TMP environment variable to a different drive (40GB Free), but receive the same error. I'm stumped and have been working with Chris in tech support (via the phone). Any help would be greatly appreciated as we are trying to roll back a couple of transactions from this morning's event.

Aaron
Back to top
View user's profile Send private message
Brian Donahue



Joined: 23 Aug 2004
Posts: 6674

PostPosted: Tue Nov 14, 2006 5:32 pm    Post subject: Reply with quote

Hi Aaron,

Did Chris send you a query to run similar to the one in the code block, below? My suspicion is that Log Rescue is hanging, not due to an over-abundance of log data, but because it can't locate the log file. In other words, if you run this query, and it doesn't ever return, then maybe there is a problem with log rescue. In one case the query never returned because the log file path was relative and Log Rescue couldn't resolve it.
Code:
DECLARE @logfilename nchar(261)
DECLARE @challange int
set @challange = 12345
DECLARE @minFileID int
set @minFileID = 0
SET @logfilename  = (select top 1 filename from
<name of database>..sysfiles1  where (status & 0x40) !=0)
SET @logfilename  = RTRIM(@logfilename) + '*'
exec master..xp_LogRescue @challange, @logfilename , @minFileID
Back to top
View user's profile Send private message
MarceloFarinelli



Joined: 30 Jan 2008
Posts: 2

PostPosted: Wed Jan 30, 2008 5:51 pm    Post subject: Reply with quote

Hi, I executed this query and it never returns, so now I understand why I'm getting those timeouts.

I checked sysfiles1 and the file paths are correct. There are no invalid entries and all paths are absolute.

My DB is very small (5mb) and I have plenty of disk space (13GB).

Version is 1.2.0.29

I also read all the other related posts but no solution yet.

Any other tips?
Back to top
View user's profile Send private message
Brian Donahue



Joined: 23 Aug 2004
Posts: 6674

PostPosted: Wed Jan 30, 2008 6:06 pm    Post subject: Reply with quote

Aside from the sysfiles issue, there is one other documented cause for this problem involving transactions currently running in the database being analyzed.

Hopefully this helps.
Back to top
View user's profile Send private message
MarceloFarinelli



Joined: 30 Jan 2008
Posts: 2

PostPosted: Wed Jan 30, 2008 6:14 pm    Post subject: Reply with quote

Thanks for replying so fast.

I just checked, but there are no processes running on that database, so no open transactions.

Thanks anyway.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group