I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The SQL Server instance is at SP4 with the
additional hot fix for the AWE memory problem.
We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still showing only 4 GB of RAM. Task Manager on
the server itself shows all 8 GB.
The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on. The startup log says AWE is enabled.
Still, EM shows only 4 GB of RAM. I have another instance on a non-clustered machine and it shows all 8 GB correctly.
Any ideas what the problem could be?
Thanks,
EdEd
Did you set up MAX Memory?
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed|||Hi Uri,
Yes, max memory is set. Here is ooutput of sp_configure for memory options:
name minimum maximum config_value run_value
awe enabled 0 1 1 1
max server memory (MB) 4 2147483647 6144 6144
min server memory (MB) 0 2147483647 0 0
"Uri Dimant" wrote:
> Ed
> Did you set up MAX Memory?
>|||Where exactly are you seeing this 4GB? What does sp_configure show for the
MAX Memory?
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed Enstrom" <nospam@.invalid.net> wrote in message
news:47ccccc1$0$15174$607ed4bc@.cv.net...
>I have a SQL Server 2000 instance on a Windows Server 2003 cluster. The
>SQL Server instance is at SP4 with the additional hot fix for the AWE
>memory problem.
> We updated the OS memory from 4 GB to 8 GB but Enterprise Manager is still
> showing only 4 GB of RAM. Task Manager on the server itself shows all 8
> GB.
> The /PAE switch is in boot.ini (not /3GB switch) and AWE is turned on.
> The startup log says AWE is enabled.
> Still, EM shows only 4 GB of RAM. I have another instance on a
> non-clustered machine and it shows all 8 GB correctly.
> Any ideas what the problem could be?
> Thanks,
> Ed|||In Enterprise Manager, right-click on the instance.
On the General tab, the OS Memory: line shows 3839(MB)
The Memory tab shows range of 0 to 3839 MB.
in sp_configure, max server memory (MB) is 6144
"Andrew J. Kelly" wrote:
> Where exactly are you seeing this 4GB? What does sp_configure show for the
> MAX Memory?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>|||It sounds like either the hotfix did not succeed or you applied the wrong
one. If you run xp_msver do you see the proper version for that hotfix? Is
this Enterprise Edition of SQL Server? This was on a cluster. Did the
hotfix get applied to both nodes?
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
> In Enterprise Manager, right-click on the instance.
> On the General tab, the OS Memory: line shows 3839(MB)
> The Memory tab shows range of 0 to 3839 MB.
> in sp_configure, max server memory (MB) is 6144
> "Andrew J. Kelly" wrote:
>> Where exactly are you seeing this 4GB? What does sp_configure show for
>> the
>> MAX Memory?
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors|||Hi Andrew,
Results from xp_msver:
Index Name Internal_Value Character_Value
1 ProductName Microsoft SQL Server
2 ProductVersion 524288 8.00.2187
3 Language 1033 English (United States)
4 Platform NT INTEL X86
5 Comments NT INTEL X86
6 CompanyName Microsoft Corporation
7 FileDescription SQL Server Windows NT
8 FileVersion 2000.080.2187.00
9 InternalName SQLSERVR
10 LegalCopyright © 1988-2004 Microsoft Corp. All rights reserved.
11 LegalTrademarks Microsoft® is a registered trademark of Microsoft
Corporation. Windows(TM) is a trademark of Microsoft Corporation
12 OriginalFilename SQLSERVR.EXE
13 PrivateBuild
14 SpecialBuild 143327232
15 WindowsVersion 248381957 5.2 (3790)
16 ProcessorCount 4 4
17 ProcessorActiveMask 15 0000000f
18 ProcessorType 586 PROCESSOR_INTEL_PENTIUM
19 PhysicalMemory 3839 3839 (4025999360)
20 Product ID
The hotfix was applied. So far as I know, it was successful (no errors).
It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
this version for clustering).
This is what is driving me nuts. Everything looks right, but SQL Server is
not seeing all the memory.
"Andrew J. Kelly" wrote:
> It sounds like either the hotfix did not succeed or you applied the wrong
> one. If you run xp_msver do you see the proper version for that hotfix? Is
> this Enterprise Edition of SQL Server? This was on a cluster. Did the
> hotfix get applied to both nodes?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Ed" <Ed@.discussions.microsoft.com> wrote in message
> news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
> > In Enterprise Manager, right-click on the instance.
> > On the General tab, the OS Memory: line shows 3839(MB)
> > The Memory tab shows range of 0 to 3839 MB.
> > in sp_configure, max server memory (MB) is 6144
> >
> > "Andrew J. Kelly" wrote:
> >
> >> Where exactly are you seeing this 4GB? What does sp_configure show for
> >> the
> >> MAX Memory?
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >> Solid Quality Mentors
> >>
>|||OK well you actually have the Cumulative Update not just the hotfix but it
still should contain it as far as I know. What do the perfmon counters for
SQL Memory Target and Total memory show? If they show the 6GB then it
sounds like a bug in the gui. You may need to contact PSS if perfmon or
DBCC MEMORYSTATUS are not showing the right amount.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:9D711AC5-1218-42B4-825F-6F8BF60B35CE@.microsoft.com...
> Hi Andrew,
> Results from xp_msver:
> Index Name Internal_Value Character_Value
> 1 ProductName Microsoft SQL Server
> 2 ProductVersion 524288 8.00.2187
> 3 Language 1033 English (United States)
> 4 Platform NT INTEL X86
> 5 Comments NT INTEL X86
> 6 CompanyName Microsoft Corporation
> 7 FileDescription SQL Server Windows NT
> 8 FileVersion 2000.080.2187.00
> 9 InternalName SQLSERVR
> 10 LegalCopyright © 1988-2004 Microsoft Corp. All rights reserved.
> 11 LegalTrademarks Microsoft® is a registered trademark of Microsoft
> Corporation. Windows(TM) is a trademark of Microsoft Corporation
> 12 OriginalFilename SQLSERVR.EXE
> 13 PrivateBuild
> 14 SpecialBuild 143327232
> 15 WindowsVersion 248381957 5.2 (3790)
> 16 ProcessorCount 4 4
> 17 ProcessorActiveMask 15 0000000f
> 18 ProcessorType 586 PROCESSOR_INTEL_PENTIUM
> 19 PhysicalMemory 3839 3839 (4025999360)
> 20 Product ID
> The hotfix was applied. So far as I know, it was successful (no errors).
> It is on both nodes of the cluster. Windows Server 2003 Enterprise (need
> this version for clustering).
> This is what is driving me nuts. Everything looks right, but SQL Server
> is
> not seeing all the memory.
> "Andrew J. Kelly" wrote:
>> It sounds like either the hotfix did not succeed or you applied the wrong
>> one. If you run xp_msver do you see the proper version for that hotfix?
>> Is
>> this Enterprise Edition of SQL Server? This was on a cluster. Did the
>> hotfix get applied to both nodes?
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors
>>
>> "Ed" <Ed@.discussions.microsoft.com> wrote in message
>> news:E1779412-EA48-495C-A9F5-79B39619ED52@.microsoft.com...
>> > In Enterprise Manager, right-click on the instance.
>> > On the General tab, the OS Memory: line shows 3839(MB)
>> > The Memory tab shows range of 0 to 3839 MB.
>> > in sp_configure, max server memory (MB) is 6144
>> >
>> > "Andrew J. Kelly" wrote:
>> >
>> >> Where exactly are you seeing this 4GB? What does sp_configure show
>> >> for
>> >> the
>> >> MAX Memory?
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >> Solid Quality Mentors
>> >>
>>|||Andrew,
Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a UI
issue. I have another server (non-clustered) at the same SQL 8,00.2187 (SP4)
version with 8 GB and it is working properly. I suspect the problem is
related to clustering, but I do not know enough about that to pinpoint the
cause. I will continue to investigate.
Thanks for the DBCC MEMORYSTATUS idea. I did not know about this function.
It does not appear in Help.
Ed
"Andrew J. Kelly" wrote:
> OK well you actually have the Cumulative Update not just the hotfix but it
> still should contain it as far as I know. What do the perfmon counters for
> SQL Memory Target and Total memory show? If they show the 6GB then it
> sounds like a bug in the gui. You may need to contact PSS if perfmon or
> DBCC MEMORYSTATUS are not showing the right amount.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>|||It certainly sounds like the Hoxfix didn't work properly. I would give MS a
call.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:3C36BE31-DFED-469C-BC93-27808286BEB5@.microsoft.com...
> Andrew,
> Perfmon shows 3.2 GB total memory for SQL Server, so the problem is not a
> UI
> issue. I have another server (non-clustered) at the same SQL 8,00.2187
> (SP4)
> version with 8 GB and it is working properly. I suspect the problem is
> related to clustering, but I do not know enough about that to pinpoint the
> cause. I will continue to investigate.
> Thanks for the DBCC MEMORYSTATUS idea. I did not know about this
> function.
> It does not appear in Help.
> Ed
> "Andrew J. Kelly" wrote:
>> OK well you actually have the Cumulative Update not just the hotfix but
>> it
>> still should contain it as far as I know. What do the perfmon counters
>> for
>> SQL Memory Target and Total memory show? If they show the 6GB then it
>> sounds like a bug in the gui. You may need to contact PSS if perfmon or
>> DBCC MEMORYSTATUS are not showing the right amount.
>> --
>> Andrew J. Kelly SQL MVP
>> Solid Quality Mentors|||Right. I've pretty much come to the same conclusion.
Thanks for the help.
Ed
"Andrew J. Kelly" wrote:
> It certainly sounds like the Hoxfix didn't work properly. I would give MS a
> call.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>|||The problem has been solved. It turns out that we had to stop and restart
the cluster in order for SQL Server to see the extra memory. We had to wait
until Friday night to do it.
When we added the memory, we failed over the SQL Server service, took the
machine down, added the memory and brought the machine back up again. The
cluster was never stopped.
Thanks again for your help.
Ed
"Andrew J. Kelly" wrote:
> It certainly sounds like the Hoxfix didn't work properly. I would give MS a
> call.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment