04.05.2007, 18:54 | #1 |
Участник
|
Добрый день.
Ситуация следующая - пользователи постоянно подвисают. /Такого раньше небыло. практически не возможно работать. Может кто-то что-то подскажет по логам - 2007-05-04 15:38:44.14 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86) Aug 6 2000 00:57:48 Copyright © 1988-2000 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: ) 2007-05-04 15:38:44.14 server Copyright © 1988-2000 Microsoft Corporation. 2007-05-04 15:38:44.14 server All rights reserved. 2007-05-04 15:38:44.14 server Server Process ID is 392. 2007-05-04 15:38:44.14 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. 2007-05-04 15:38:44.15 server SQL Server is starting at priority class 'high'(4 CPUs detected). 2007-05-04 15:38:45.25 server Working Set size set to 1651840 kilobytes. 2007-05-04 15:38:45.25 server SQL Server configured for thread mode processing. 2007-05-04 15:38:45.26 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks. 2007-05-04 15:38:45.32 server Attempting to initialize Distributed Transaction Coordinator. 2007-05-04 15:39:03.62 spid3 Starting up database 'master'. 2007-05-04 15:39:05.50 spid3 0 transactions rolled back in database 'master' (1). 2007-05-04 15:39:05.50 spid3 Recovery is checkpointing database 'master' (1) 2007-05-04 15:39:08.51 server Using 'SSNETLIB.DLL' version '8.0.194'. 2007-05-04 15:39:08.51 spid5 Starting up database 'model'. 2007-05-04 15:39:09.01 spid3 Server name is 'NTS'. 2007-05-04 15:39:09.01 spid8 Starting up database 'msdb'. 2007-05-04 15:39:09.01 spid9 Starting up database 'pubs'. 2007-05-04 15:39:09.01 spid10 Starting up database 'Northwind'. 2007-05-04 15:39:09.01 spid11 Starting up database 'NavisionDataBaseSD'. 2007-05-04 15:39:09.01 spid13 Starting up database 'NavisionLogBaseSD'. 2007-05-04 15:39:09.01 spid12 Starting up database 'NAV'. 2007-05-04 15:39:09.01 server SQL server listening on Shared Memory, Named Pipes. 2007-05-04 15:39:09.01 server SQL Server is ready for client connections 2007-05-04 15:39:09.64 spid12 Analysis of database 'NAV' (8) is 100% complete (approximately 0 more seconds) 2007-05-04 15:39:11.82 spid5 Clearing tempdb database. 2007-05-04 15:39:14.35 spid1 Warning: unable to allocate 'min server memory' of 2048MB. 2007-05-04 15:39:14.89 spid8 Recovery is checkpointing database 'msdb' (4) 2007-05-04 15:39:15.67 spid5 Starting up database 'tempdb'. 2007-05-04 15:39:15.76 spid3 Recovery complete. 2007-05-04 15:39:16.23 spid51 Using 'xpsqlbot.dll' version '2000.80.194' to execute extended stored procedure 'xp_qv'. 2007-05-04 16:00:01.54 spid67 Using 'xpstar.dll' version '2000.80.194' to execute extended stored procedure 'xp_sqlmaint'. 2007-05-04 16:10:07.66 spid68 Error: 9002, Severity: 17, State: 2 2007-05-04 16:10:07.66 spid68 The log file for database 'tempdb' is full. Back up the transaction log for the database to free up some log space.. 2007-05-04 16:10:57.64 spid70 Using 'xplog70.dll' version '2000.80.194' to execute extended stored procedure 'xp_msver'. Я так понимаю что проблема с tempdb. Но, вот что можно сделать чтобы восстановить нормальную работу сервера ? |
|