Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2005-02-01 : 07:55:32
|
| Matt writes "This is more a comment than a question, however your input and comments would be very welcome. Just a point of information for anyone running SQLServer 2000 Enterprise Edition on Windows Server 2003 Enterprise Edition, using extended memory (AWE enabled, /PAE). We had lots of trouble with O/S 1450 errors and so forth, when the server was configured with the /3GB switch in boot.ini. We found articles online that the reason might be related to the PTE tables, and the ability of the OS to manage the memory mapping as the PTE tables become filled. In fact, with /3GB in, the PTE tables were only about 20000 entries. With the /3GB out, the paging tables got to about 180000 entries, nearly 10x increase. Below is an example of some of the errors we used to have. We do not experience these anymore. I've purposely removed names of files, databases, and directories, because of my company's policy.2004-11-10 21:34:35.16 spid1 Error: 823, Severity: 24, State: 4 2004-11-10 21:34:35.16 spid1 I/O error 1450(Insufficient system resources exist to complete the requested service.) detected during write at offset 0x00000042530000 in file '<MDF file>'.. ----------- 2004-11-13 17:05:25.17 spid2 LogWriter: Operating system error 1450(Insufficient system resources exist to complete the requested service.) encountered. 2004-11-13 17:05:25.26 spid2 Write error during log flush. Shutting down server 2004-11-13 17:05:25.55 spid167 Error: 9001, Severity: 21, State: 4 2004-11-13 17:05:25.55 spid167 The log for database '<database>' is not available.. 2004-11-13 17:05:25.62 spid167 Error: 9001, Severity: 21, State: 1 2004-11-13 17:05:25.62 spid167 The log for database '<database>' is not available.. 2004-11-13 17:05:25.68 spid167 Error: 9001, Severity: 21, State: 1 2004-11-13 17:05:25.68 spid167 The log for database '<database>' is not available.. 2004-11-13 17:05:25.77 spid167 Error: 3314, Severity: 21, State: 4 2004-11-13 17:05:25.77 spid167 Error while undoing logged operation in database '<database>'. Error at log record ID (32283:38320:3).. 2004-11-13 17:05:25.79 spid167 Error: 9001, Severity: 21, State: 1 2004-11-13 17:05:25.79 spid167 The log for database '<database>' is not available.. 2004-11-13 17:05:25.85 spid167 Error: 3314, Severity: 21, State: 5 2004-11-13 17:05:25.85 spid167 Error while undoing logged operation in database '<database>'. Error at log record ID (32283:38320:1).. 2004-11-13 17:05:26.63 spid22 Database '<database>' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. 2004-11-13 17:05:26.70 spid22 Database '<database>' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. 2004-11-13 17:05:27.23 spid22 Starting up database '<database>'. 2004-11-13 17:05:34.53 spid22 Analysis of database '<database>' (8) is 100% complete (approximately 0 more seconds) 2004-11-13 17:05:34.54 spid22 Recovery of database '<database>' (8) is 0% complete (approximately 8 more seconds) (Phase 2 of 3). 2004-11-13 17:05:34.81 spid22 Recovery of database '<database>' (8) is 100% complete (approximately 0 more seconds) (Phase 2 of 3). ----------- *Dump thread - spid = 106, PSS = 0x57a61220, EC = 0x57a61548 *Stack Dump being sent to <location>\SQLDump0001.txt * ******************************************************************************* * * BEGIN STACK DUMP: * 11/13/04 19:24:30 spid 106 * * * * Input Buffer 140 bytes - * dbcc dbreindex(N'[dbo].<[tablename>]', N'', 90, sorted_data_reorg) * .... 2004-11-13 19:24:32.55 spid106 Stack Signature for the dump is 0x6E979C26 2004-11-13 19:24:32.57 spid106 SQL Server Assertion: File: <buffer.c>, line=3745 Failed Assertion = '!(bp->bdbid == dbid && ALL_ON (BUF_HASHED | |
|
|
|
|
|
|
|
Avoiding OS 1450 errors with SQL2KEE/Win2K3EE