Failed allocate pages: FAIL_PAGE_ALLOCATION 1
Question
Tuesday, October 24, 2017 4:55 AM
Hi,
I have installed SQL Server 2016 on Cluster. The installation was successfull and it was fine and I was able to do failover between nodes.
Next Day when I tried to failove the instance, SQL Server fails to come up with below error message in SQL Server Log.
Failed allocate pages: FAIL_PAGE_ALLOCATION 1
Even Log shows
The SQL Server (XXX) service terminated with the following error:
Ran out of memory
But this is a new server with 512 GB RAM and nothing runs on it.
Please help
All replies (5)
Tuesday, October 24, 2017 5:37 AM
Is there any dump file created? Can you run DBCC memorystatus and see available physical memory value?
BTW, what value have you given to MAX Memory setting?
if 'lock pages in memory' LPIM is set to or not?
Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting: Large scale of database and data cleansing
Remote DBA Services: Improves MS SQL Database Performance
SQL Server Integration Services: Business Intelligence
Tuesday, October 24, 2017 6:40 AM
Hi,
It is new installation on this server and I have not set anything so far.
I am not even able to connect SSMS nor thru sqlcmd.
I used to -f in startup parmaters, and SQL Server came online, but when I tried to login in SSMS, it gives me message that "SQL Server is running in Single user mode"
But i cant -m startup parameter in starup parameters.
Thanks
Tuesday, October 24, 2017 7:40 AM
in the Startup Parameters box, select the -m parameter in the Existing Parameters box, and then click Remove. Restart the Database Engine to restore SQL Server to the typical multi-user mode.
Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting: Large scale of database and data cleansing
Remote DBA Services: Improves MS SQL Database Performance
SQL Server Integration Services: Business Intelligence
Tuesday, October 24, 2017 7:41 AM
Make sure you connect to the correct node
Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting: Large scale of database and data cleansing
Remote DBA Services: Improves MS SQL Database Performance
SQL Server Integration Services: Business Intelligence
Tuesday, October 24, 2017 3:38 PM
So what is memory available on the node where you are failing over SQL Server. Do you have sufficient memory on the other node.
If SQL Server is not coming online and throwing OOM error its basically user configured Very very low max server memory or no memory is available on node where SQL Server is failed over
Cheers,
Shashank
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it