November 9, 2013 at 7:51 am
I got this message when trying to restore a DIIF backup
Msg 3183, Sev 16, State 2, Line 91 : RESTORE detected an error on page (56584:-1905079732) in database "Execunet_Clientview" as read from the backup set. [SQLSTATE 42000].
I will take a new DIFF backup & try again.
EDIT: With a new DIFF file, I get the same error. I wonder if there is a problem with the source database where the backup was taken ??
EDIT 2: Seems to be memory related, as discussed later in the thread
November 9, 2013 at 5:16 pm
Strange. I re-ran the job a 2nd time, and the restore of Database A completed normally this time (using a new DIFF backup), but the restore of Database C failed with that message.
Maybe the backups are getting corrupted somehow during ftp to the target servers.
November 10, 2013 at 2:55 am
homebrew01 (11/9/2013)
Maybe the backups are getting corrupted somehow during ftp to the target servers.
Wouldn't be the first time I've heard of that happening.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 10, 2013 at 9:35 am
Narrowing it down a bit. getting these messages yesterday on the server running the original backups, and the job that was supposed to backup 10 databases only backed up 2 then stopped.
"[font="Courier New"]There is insufficient system memory to run this query[/font]."
The load and jobs have not changed in the last year. 4 G of ram on the server, but task manager shows 2.2 G used and 1.7 G free. I would think more should be used. ?
Task Manager -> Processes shows sqlservr.exe using 1.7 G
November 10, 2013 at 10:11 am
32-bit SQL installation?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 10, 2013 at 11:20 am
Windows Server 2003 R2 Standard Edition SP2
2.8 Gz, 4 G RAM
@@Version:
Microsoft SQL Server 2005 - 9.00.4060.00 (Intel X86) Mar 17 2011 13:20:38 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
Only recent change I can think of was last week installing MySQL ODBC driver and setting up a linked server to MySQL on a Linux server for pushing table changes to a MySQL database.
November 10, 2013 at 11:57 am
Yup, 32 bit. You don't have AWE enabled, so SQL can only use 1.7 GB of memory. You're probably running into fragmented virtual address space (or are out of virtual address space), linked server drivers use that limited space, as do backup buffers. Try restarting SQL and consider replacing that with 64-bit at some point.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 10, 2013 at 2:45 pm
I rebooted this morning.
I thought AWE was set correctly. I'll have to read up on it ... forgot the details.
I just ran:
sp_configure 'awe enabled', 1
RECONFIGURE
I will restart SQL during quiet time tonight. Thanks for pointing me in the right direction.
Should I set max server memory to 3.25 Gig or so, leaving .75 G for other processes ?
November 10, 2013 at 10:12 pm
3GB max to start with. Adjust as necessary.
Still consider upgrading to 64-bit, if you've got a linked server driver causing MemToLeave problems, enabling AWE is not going to make it any better.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 10, 2013 at 10:45 pm
I'm not fa,iliar with the MemToLeave problems. I will have to read up on it.
Thanks
November 10, 2013 at 11:56 pm
Jonathan's Troubleshooting book, memory chapter.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 11, 2013 at 1:03 pm
Please correct me if I am wrong - but setting AWE won't have any affect on this system because it only has 4GB of memory. To be able to use AWE, you would need more than 4GB of memory - and then the memory above the 4GB could be accessed.
What I believe is needed here is the /3GB switch enabled.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
November 11, 2013 at 1:27 pm
Edit: Not sure anymore...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 17, 2013 at 4:46 pm
So, would something like -g700 be appropriate as a startup parameter to help the Linked Server memory issue ??
November 17, 2013 at 10:16 pm
Maybe. But it's a temporary mitigation. If you have stuff fragmenting MemToLeave, increasing the size will delay the problems, not prevent them.
Also, that means that, without AWE or 3GB, you now have 1.3 GB for SQL's buffer pool and other caches, not 1.7.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 15 posts - 1 through 15 (of 30 total)
You must be logged in to reply to this topic. Login to reply