I was troubleshooting my ePO server inaccessibility, then discovered that my ePO database is too large (100GB). I ran a query to delete old events. As McAfee technical support was online to troubleshoot ePO, I canceled the query, exited SQL Server Management Studio, restarted server. The database went into recovery mode, so I left it recovering over the weekend. Today I found that the recovery did not finish, the database is in 'recovery pending'. In error.log, it ended with recovery is complete, but there is"insufficient system memory in resource pool 'internal' to run this query." just before the end. I checked the task manager, there is sufficient memory (Total physical memory is 8GB, there is 49% free memory).
When I restarted the SQL server service, the database again went into 'In recovery' but after a while (~30 minutes) it became 'Recovery Pending'.
How can I verify if the memory is the cause of the recovery failure?
The objective is to bring online the ePO database, loss of records in the event table is not much of an issue.
The error.log:
2016-01-20 14:44:58.64 Server Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (Intel X86)
Oct 19 2012 13:43:21
Copyright (c) Microsoft Corporation
Standard Edition on Windows NT 6.2 <X64> (Build 9200: ) (WOW64) (Hypervisor)
.
.
2016-01-20 14:45:01.32 spid6s Starting up database 'model'.
2016-01-20 14:45:01.55 spid6s Clearing tempdb database.
2016-01-20 14:45:01.66 spid6s Starting up database 'tempdb'.
2016-01-20 14:45:01.70 spid18s The Service Broker endpoint is in disabled or stopped state.
2016-01-20 14:45:01.70 spid18s The Database Mirroring endpoint is in disabled or stopped state.
2016-01-20 14:45:01.70 spid18s Service Broker manager has started.
2016-01-20 14:45:14.43 spid17s Recovery of database 'ePO_SSNPEPO0001' (5) is 0% complete (approximately 26676 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2016-01-20 14:47:33.13 spid17s Failed allocate pages: FAIL_PAGE_ALLOCATION 1
2016-01-20 14:47:33.13 spid17s
Process/System Counts Value
---------------------------------------- ----------
Available Physical Memory 4188368896
Available Virtual Memory 191361024
Available Paging File 6562304000
Working Set 74620928
Percent of Committed Memory in WS 100
Page Faults 35290
System physical memory high 1
System physical memory low 0
Process physical memory low 0
Process virtual memory low 0
2016-01-20 14:47:33.13 spid17s .
.
.
2016-01-20 14:49:33.77 spid17s Error: 701, Severity: 17, State: 223.
2016-01-20 14:49:33.77 spid17s There is insufficient system memory in resource pool 'internal' to run this query.
2016-01-20 14:50:23.77 spid4s Recovery is complete. This is an informational message only. No user action is required.
Valuable skills are not learned, learned skills aren't valuable.