Has anyone come across this assertion? I can't find any references on-line or elsewhere.
*** ERROR *** Assertion failed: 101419 (10.0.1.4310) E. 03/14 15:11:11. page not pinned
The db re-started without complaint, but I won't be able to do a validation until later (it's a huge database), but we have live log back-ups. The database files were moved on to new SAN hardware last night.
I suppose I am asking whether this is likely to indicate a database corruption, and if so what form it might take; also whether it can give us any indication of any possible problem with the hardware? The SAN is the latest top-spec EMC fibre-channel kit configured as RAID 10.
UPDATE DB passed validation
UPDATE Has happened again, about two weeks after the first time, no problems in between. Given John's explanation about heap pages, is this likely to be a related to a server bug or something we are doing?
FURTHER UPDATE This assertion carried on happening regularly (approx once or twice a week) until the server was upgraded to 11.0.1 - now about for weeks without repetition. It seems that the problem relates to v10.0.1 together with the particular hardware / environment.
Is this running on a Windows, Linux or other OS?
(I will assume Windows...)
Have you checked your OS settings regarding how you have configured the ( http://support.microsoft.com/kb/314482 ) page file / swap space? Have you monitored this system for 'low-memory' issues (either in real or virtual memory) via Performance Monitor (or similar)? Have you scanned for bad memory ( http://technet.microsoft.com/en-us/magazine/ff700221.aspx / http://www.memtest86.com/ / http://www.memtest.org/ ) as Volker has recommended?
What drive is the temporary file stored on and have you scanned that drive (chkdisk / scandisk) for potential issues?
answered 28 Mar '12, 14:13
Have you checked How to: Enable the Lock Pages in Memory Option (Windows)
It is disabled by default on Win 2008 R2.
answered 15 Mar '12, 09:30