debugsqlMinor
Keep getting message: Failed allocate pages: FAIL_PAGE_ALLOCATION 540
Viewed 0 times
messagekeepgettingfail_page_allocationallocatefailed540pages
Problem
I'd appreciate some help with the following, I've done some Googling, but haven't managed to resolve this one.
I keep receiving a message in the SQL Log 'Failed allocate pages: FAIL_PAGE_ALLOCATION 540', followed by a dump which I'll add to the end of this question.
For your information, the build is:
The server is part of a 2 node Availability Group, this is the current primary node.
This instance is hosting the databases for Microsoft SharePoint
I ran a Perfmon trace for 24 hours which only revealed PLE dropping after one of the dumps, and then rising back up. Nothing else particularly odd.
SQL Server is still running.
EXTRACT FROM SQL LOG:
```
10/03/2014 09:59:52,spid866,Unknown,CACHESTORE_XMLDBELEMENT (node 0) KB---------------------------------------- ----------VM Reserved 0VM Committed 0Locked Pages Allocated 0SM Reserved 0SM Committed 0Pages Allocated 8
10/03/2014 09:59:52,spid866,Unknown,CACHESTORE_XMLDBTYPE (node 0) KB---------------------------------------- ----------VM Reserved 0VM Committed 0Locked Pages Allocated 0SM Reserved 0SM Committed 0Pages Allocated 8
10/03/2014 09:59:52,spid866,Unknown,CACHESTORE_VIEWDEFINITIONS (node 0) KB---------------------------------------- ----------VM Reserved 0VM Committed 0Locked Pages Allocated
I keep receiving a message in the SQL Log 'Failed allocate pages: FAIL_PAGE_ALLOCATION 540', followed by a dump which I'll add to the end of this question.
For your information, the build is:
- Virtual Server running on vCenter
- Windows Server 2008 R2 64bit SQL
- Server 2012 SP1 Enterprise (11.0.2100) 8GB RAM SQL Server Max and Min memory is set to 6144 MB
The server is part of a 2 node Availability Group, this is the current primary node.
This instance is hosting the databases for Microsoft SharePoint
I ran a Perfmon trace for 24 hours which only revealed PLE dropping after one of the dumps, and then rising back up. Nothing else particularly odd.
SQL Server is still running.
EXTRACT FROM SQL LOG:
```
10/03/2014 09:59:52,spid866,Unknown,CACHESTORE_XMLDBELEMENT (node 0) KB---------------------------------------- ----------VM Reserved 0VM Committed 0Locked Pages Allocated 0SM Reserved 0SM Committed 0Pages Allocated 8
10/03/2014 09:59:52,spid866,Unknown,CACHESTORE_XMLDBTYPE (node 0) KB---------------------------------------- ----------VM Reserved 0VM Committed 0Locked Pages Allocated 0SM Reserved 0SM Committed 0Pages Allocated 8
10/03/2014 09:59:52,spid866,Unknown,CACHESTORE_VIEWDEFINITIONS (node 0) KB---------------------------------------- ----------VM Reserved 0VM Committed 0Locked Pages Allocated
Solution
Because there are only 8208 pages allocated to MEMORYCLERK_SQLLOGPOOL in the excerpt not sure kb2769594 is the culprit/fix.
Also no reference to internal pool or HADR as in the kb2769594 example.
https://support.microsoft.com/kb/2769594
So I think culprit/fix may be something else.
Surprising that no large pages allocated at all - I'd expect some for non-bpool with 8 gb of RAM on the server.
SQL Server Enterprise edition?
Low system memory is somewhat suprising - is there another large memory consumer beside SQL Server?
Which OS version? Is the NTFS file cache well under control?
edit
Via twitter also asked if 'lock pages in memory' LPIM is expected - no locked pages indicated above.
Also no reference to internal pool or HADR as in the kb2769594 example.
https://support.microsoft.com/kb/2769594
So I think culprit/fix may be something else.
Surprising that no large pages allocated at all - I'd expect some for non-bpool with 8 gb of RAM on the server.
SQL Server Enterprise edition?
Low system memory is somewhat suprising - is there another large memory consumer beside SQL Server?
Which OS version? Is the NTFS file cache well under control?
edit
Via twitter also asked if 'lock pages in memory' LPIM is expected - no locked pages indicated above.
Context
StackExchange Database Administrators Q#78310, answer score: 5
Revisions (0)
No revisions yet.