Добро пожаловать в форум, Guest  >>   Войти | Регистрация | Поиск | Правила | В избранное | Подписаться
Все форумы / Microsoft SQL Server Новый топик    Ответить
 Откат транзакций  [new]
Yayaadmin
Guest
Нигде не нашел ничего внятного на эту тему поэтому решил спросить здесь.
Так вот, по какой то причине в базе все транзакции были завершены (откат или накат), служба работала нормально, в логах ошибок нет, вообще ничего нет, одно сообщение что столько то транзакций откачено, столько то сделан накат тр. Из за этого все текущие процессы в системе выпали в ошибку, вопрос почему СУБД может сама решить завершить все транзакции?
Сервак рейд 10, он периодически рушиться и перестравается, может из за этого быть проблема? Через 10 мин после этого он как раз начал перестраиваеться.
Также на сервере за 10 минут до этого были ошикби типа "система windows обнаружила что файл реестра используется другим приложением" и "mmc.exe процесс был завершен из за необработанного исключения", но это вроде не должно было повлиять. Больше никаких ошибок нет.
11 май 16, 06:31    [19156045]     Ответить | Цитировать Сообщить модератору
 Re: Откат транзакций  [new]
o-o
Guest
У нас как-то раз место в базе закончилось во время ребилда. Что-то он плохо рассчитал необходимое место и стал откатывать начатый ребилд. Джоб на этой базе упал, а саму базу сервер отправил в оффлайн. Сам. Правда, еррорлог был разукрашен всевозможными сообщениями
+

Could not allocate space for object 'dbo.DO_Master_Tipo_FG_T'.'PK_DO_Master_Tipo_FG_T' in database 'S1057' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
Could not allocate a new page for database 'S1057' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
During undoing of a logged operation in database 'S1057', an error occurred at log record ID (2971091:1335:109). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Database S1057 was shutdown due to error 1101 in routine 'XdesRMReadWrite::RollbackToLsn'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.

The log for database 'S1057' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
During undoing of a logged operation in database 'S1057', an error occurred at log record ID (2971091:11519:609). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
The log for database 'S1057' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
During undoing of a logged operation in database 'S1057', an error occurred at log record ID (2971013:7336:235). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Starting up database 'S1057'.
Recovery of database 'S1057' (23) is 0% complete (approximately 697 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 1% complete (approximately 1754 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 1% complete (approximately 2316 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 1% complete (approximately 2824 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 2% complete (approximately 1851 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 3% complete (approximately 1820 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 4% complete (approximately 1806 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 4% complete (approximately 1788 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
12 transactions rolled forward in database 'S1057' (23). This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 4% complete (approximately 1788 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
To allow recovery to succeed, the log file 'S1057' has been expanded beyond its maximum size. After recovery completes, you should either increase the size of the log file in the database or schedule more frequent backups of the log (under the full or bulk-logged recovery model).
Recovery of database 'S1057' (23) is 3% complete (approximately 2272 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 5% complete (approximately 1324 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 9% complete (approximately 780 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 14% complete (approximately 496 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 20% complete (approximately 326 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 26% complete (approximately 230 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 32% complete (approximately 180 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 36% complete (approximately 151 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 39% complete (approximately 134 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 41% complete (approximately 123 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 43% complete (approximately 116 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 46% complete (approximately 107 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 47% complete (approximately 102 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 48% complete (approximately 99 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 50% complete (approximately 93 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 51% complete (approximately 91 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 52% complete (approximately 91 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 53% complete (approximately 89 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 54% complete (approximately 89 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 55% complete (approximately 88 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 56% complete (approximately 86 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 57% complete (approximately 84 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 58% complete (approximately 82 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 59% complete (approximately 80 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 60% complete (approximately 77 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 61% complete (approximately 74 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 62% complete (approximately 71 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 63% complete (approximately 69 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 65% complete (approximately 66 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 66% complete (approximately 64 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 67% complete (approximately 61 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 68% complete (approximately 59 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 69% complete (approximately 57 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 70% complete (approximately 55 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 71% complete (approximately 53 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 72% complete (approximately 51 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 73% complete (approximately 50 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 74% complete (approximately 48 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 75% complete (approximately 46 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 76% complete (approximately 44 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 77% complete (approximately 42 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 78% complete (approximately 40 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 79% complete (approximately 38 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 80% complete (approximately 37 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 81% complete (approximately 35 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 82% complete (approximately 33 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 83% complete (approximately 31 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 84% complete (approximately 29 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 85% complete (approximately 27 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 86% complete (approximately 25 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 87% complete (approximately 23 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 88% complete (approximately 21 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 89% complete (approximately 20 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 90% complete (approximately 18 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 91% complete (approximately 16 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 92% complete (approximately 14 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 93% complete (approximately 12 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
1 transactions rolled back in database 'S1057' (23). This is an informational message only. No user action is required.
Recovery is writing a checkpoint in database 'S1057' (23). This is an informational message only. No user action is required.
Recovery completed for database S1057 (database ID 23) in 195 second(s) (analysis 32495 ms, redo 48260 ms, undo 107060 ms.) This is an informational message only. No user action is required.
CHECKDB for database 'S1057' finished without errors on 2016-01-25 06:39:02.137 (local time). This is an informational message only; no user action is required.
Could not allocate space for object 'dbo.DO_Master_Tipo_FG_T'.'PK_DO_Master_Tipo_FG_T' in database 'S1057' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
Could not allocate a new page for database 'S1057' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
During undoing of a logged operation in database 'S1057', an error occurred at log record ID (2971367:13313:100). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Database S1057 was shutdown due to error 1101 in routine 'XdesRMReadWrite::RollbackToLsn'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
The log for database 'S1057' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
During undoing of a logged operation in database 'S1057', an error occurred at log record ID (2971367:15350:288). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
The log for database 'S1057' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
During undoing of a logged operation in database 'S1057', an error occurred at log record ID (2971265:6255:1). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Starting up database 'S1057'.
Recovery of database 'S1057' (23) is 0% complete (approximately 449 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 0% complete (approximately 2848 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 0% complete (approximately 4036 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 1% complete (approximately 2731 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 1% complete (approximately 2699 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 1% complete (approximately 2692 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 1% complete (approximately 2692 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
To allow recovery to succeed, the log file 'S1057' has been expanded beyond its maximum size. After recovery completes, you should either increase the size of the log file in the database or schedule more frequent backups of the log (under the full or bulk-logged recovery model).
BACKUP failed to complete the command BACKUP DATABASE S1057 WITH DIFFERENTIAL. Check the backup application log for detailed messages.
Recovery of database 'S1057' (23) is 0% complete (approximately 5737 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 1% complete (approximately 3924 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 2% complete (approximately 2693 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 3% complete (approximately 1631 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 4% complete (approximately 1136 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 6% complete (approximately 802 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 8% complete (approximately 577 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 11% complete (approximately 423 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 15% complete (approximately 315 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 18% complete (approximately 242 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 22% complete (approximately 193 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 26% complete (approximately 158 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 30% complete (approximately 133 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 33% complete (approximately 116 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 36% complete (approximately 104 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 39% complete (approximately 94 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 41% complete (approximately 86 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 44% complete (approximately 80 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 46% complete (approximately 73 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 49% complete (approximately 69 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 50% complete (approximately 66 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 51% complete (approximately 67 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 53% complete (approximately 64 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 54% complete (approximately 61 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 56% complete (approximately 58 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Database differential changes were backed up. Database: S1057B, creation date(time): 2011/12/22(13:00:28), pages dumped: 12573, first LSN: 28225:14519:190, last LSN: 28225:14581:1, full backup LSN: 28224:23550:49, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'W:\USERDATA\DBBACKUP\MSSQL10_50.USEPCPDZ3\MSSQL\DIFF\S1057B_DB_201601271211.BAK'}). This is an informational message. No user action is required.
Recovery of database 'S1057' (23) is 57% complete (approximately 57 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 59% complete (approximately 55 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 60% complete (approximately 53 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 62% complete (approximately 52 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 63% complete (approximately 50 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 64% complete (approximately 48 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 66% complete (approximately 46 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 67% complete (approximately 45 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 68% complete (approximately 43 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 70% complete (approximately 41 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 71% complete (approximately 40 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 72% complete (approximately 38 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 74% complete (approximately 36 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 75% complete (approximately 34 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 76% complete (approximately 33 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 78% complete (approximately 31 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 79% complete (approximately 30 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 80% complete (approximately 28 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 81% complete (approximately 26 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 83% complete (approximately 25 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 84% complete (approximately 23 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 85% complete (approximately 21 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 87% complete (approximately 20 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 88% complete (approximately 18 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 89% complete (approximately 16 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 90% complete (approximately 14 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
Recovery of database 'S1057' (23) is 91% complete (approximately 12 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
1 transactions rolled back in database 'S1057' (23). This is an informational message only. No user action is required.
Recovery is writing a checkpoint in database 'S1057' (23). This is an informational message only. No user action is required.
Recovery completed for database S1057 (database ID 23) in 151 second(s) (analysis 7952 ms, redo 43235 ms, undo 97090 ms.) This is an informational message only. No user action is required.
CHECKDB for database 'S1057' finished without errors on 2016-01-25 06:39:02.137 (local time). This is an informational message only; no user action is required.
Could not allocate a new page for database 'S1057' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
Could not allocate space for object 'dbo.M_A_MP_tab_1_pt_3_4_T'.'PK_M_A_MP_tab_1_pt_3_4_T' in database 'S1057' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

11 май 16, 08:46    [19156186]     Ответить | Цитировать Сообщить модератору
 Re: Откат транзакций  [new]
Yayaadmin
Guest
У нас вроде все не так плохо.
Как я сказал единственное сообщение сколько он откатил и накатил транзакций, и все. После этого сразу сделал чек, все норм. Случай единичный, но хочу разобраться почему.
11 май 16, 08:56    [19156212]     Ответить | Цитировать Сообщить модератору
 Re: Откат транзакций  [new]
aleks2
Guest
Yayaadmin
Нигде не нашел ничего внятного на эту тему поэтому решил спросить здесь.
Так вот, по какой то причине в базе все транзакции были завершены (откат или накат), служба работала нормально, в логах ошибок нет, вообще ничего нет, одно сообщение что столько то транзакций откачено, столько то сделан накат тр. Из за этого все текущие процессы в системе выпали в ошибку, вопрос почему СУБД может сама решить завершить все транзакции?
Сервак рейд 10, он периодически рушиться и перестравается, может из за этого быть проблема? Через 10 мин после этого он как раз начал перестраиваеться.
Также на сервере за 10 минут до этого были ошикби типа "система windows обнаружила что файл реестра используется другим приложением" и "mmc.exe процесс был завершен из за необработанного исключения", но это вроде не должно было повлиять. Больше никаких ошибок нет.


Сказочник, такие заявы лучше подкреплять цитатой из журнала MS SQL и System.

ЗЫ. А так то, служба SQL-сервера аварийно остановилась и автоматом был перезапущена.
Вариант: была перезапущена ручками.
11 май 16, 09:28    [19156335]     Ответить | Цитировать Сообщить модератору
 Re: Откат транзакций  [new]
o-o
Guest
Накаты/откаты транзакций просто так не делаются, это же recovery.
И его сервер делает при выводе базы в онлайн. Значит, до этого база была в оффлайне или ресторилась.
У нас тоже случай единичный, и вообще при нехватке места в базе обычно приостанавливается писательская деятельность, а вот чтобы базу в оффлайн это я такое впервые вижу. И в интернете ничего внятного не нашлось на текст ошибки.
Просто как факт, при невозможности записать на диск, оказывается, возможен перевод базы в оффлайн по инициативе самого сервера
11 май 16, 09:29    [19156340]     Ответить | Цитировать Сообщить модератору
 Re: Откат транзакций  [new]
Yayaadmin
Guest
aleks2
Yayaadmin
Нигде не нашел ничего внятного на эту тему поэтому решил спросить здесь.
Так вот, по какой то причине в базе все транзакции были завершены (откат или накат), служба работала нормально, в логах ошибок нет, вообще ничего нет, одно сообщение что столько то транзакций откачено, столько то сделан накат тр. Из за этого все текущие процессы в системе выпали в ошибку, вопрос почему СУБД может сама решить завершить все транзакции?
Сервак рейд 10, он периодически рушиться и перестравается, может из за этого быть проблема? Через 10 мин после этого он как раз начал перестраиваеться.
Также на сервере за 10 минут до этого были ошикби типа "система windows обнаружила что файл реестра используется другим приложением" и "mmc.exe процесс был завершен из за необработанного исключения", но это вроде не должно было повлиять. Больше никаких ошибок нет.


Сказочник, такие заявы лучше подкреплять цитатой из журнала MS SQL и System.

ЗЫ. А так то, служба SQL-сервера аварийно остановилась и автоматом был перезапущена.
Вариант: была перезапущена ручками.


Службу никто не трогал

2016-05-11 09:02:36.970 Backup Log was backed up. Database: СП, creation date(time): 2015/04/27(18:38:11), first LSN: 983842:20965:1, last LSN: 983845:27449:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'VNBU0-12116-8088-1462932011'}). This is an informational message only. No user action is required.

2016-05-11 09:03:20.720 Backup Log was backed up. Database: WF, creation date(time): 2015/04/27(22:49:26), first LSN: 5685324:23224:1, last LSN: 5685341:9113:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'VNBU0-12116-13024-1462932177'}). This is an informational message only. No user action is required.

2016-05-11 09:13:15.740 spid89 16 transactions rolled forward in database 'WF' (10). This is an informational message only. No user action is required.

2016-05-11 09:13:15.790 spid89 0 transactions rolled back in database 'WF' (10). This is an informational message only. No user action is required.

2016-05-11 09:27:00.980 spid89 DBCC CHECKDB (WF) executed by User found 0 errors and repaired 0 errors. Elapsed time: 0 hours 13 minutes 45 seconds. Моментальный снимок внутренней базы данных имеет точку разбиения с номером LSN = 0056c061:00003f29:00c9 и первый номер LSN = 0056c061:00003e94:0001.

2016-05-11 09:30:46.680 spid6s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\Data\tempdb.mdf] in database [tempdb] (2). The OS file handle is 0x0000000000000844. The offset of the latest long I/O is: 0x000000282e0000

2016-05-11 09:30:46.680 spid6s SQL Server has encountered 14 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [D:\Data\templog.ldf] in database [tempdb] (2). The OS file handle is 0x0000000000000840. The offset of the latest long I/O is: 0x000000026da000

2016-05-11 10:02:45.010 Backup Log was backed up. Database: СП, creation date(time): 2015/04/27(18:38:11), first LSN: 983845:27449:1, last LSN: 983852:27692:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'VNBU0-7896-9936-1462935613'}). This is an informational message only. No user action is required.

2016-05-11 10:03:27.430 Backup Log was backed up. Database: WF, creation date(time): 2015/04/27(22:49:26), first LSN: 5685341:9113:1, last LSN: 5685373:10797:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'VNBU0-7896-12360-1462935783'}). This is an informational message only. No user action is required.

Хотя он и пишет что 0 transactions rolled back в системе все активные процесы остановились. Да и в принципе в первые вижу чтобы сервер просто так решил сделать накат\откат транзакций.
В 9:30 как раз начал перестраиваться рейд.
Служба перезапускалась месяц назад (если посмотреть по времени создания tempdb)


o-o
Если бы база была переведена в офлайн были бы сообщения, а так ничего.
11 май 16, 10:16    [19156562]     Ответить | Цитировать Сообщить модератору
 Re: Откат транзакций  [new]
o-o
Guest
ну так у вас же было запущено DBCC CHECKDB.
оно себе делает внутренний снэпшот базы и в нем откатывает/докатывает транзакции,
чтобы на консистентном снэпшоте работать.
хотя в сообщении написано про базу, относится оно к снэпшоту.
найдите в еррорлоге DBCC CHECKDB остальных баз и обнаружите то же самое
11 май 16, 10:45    [19156771]     Ответить | Цитировать Сообщить модератору
 Re: Откат транзакций  [new]
o-o
Guest
там даже спид указан тот самый, который выполнял DBCC CHECKDB (89)
11 май 16, 10:49    [19156802]     Ответить | Цитировать Сообщить модератору
 Re: Откат транзакций  [new]
Yayaadmin
Guest
o-o
ну так у вас же было запущено DBCC CHECKDB.
оно себе делает внутренний снэпшот базы и в нем откатывает/докатывает транзакции,
чтобы на консистентном снэпшоте работать.
хотя в сообщении написано про базу, относится оно к снэпшоту.
найдите в еррорлоге DBCC CHECKDB остальных баз и обнаружите то же самое


Ясно, спасибо. Когда раньше checkdb делал не обращал на это внимание видимо. Просто именно в это время (где то в 9:11) все процессы в системе выпали в ошибку, а почему непонятно.
CHECK я запустил сразу же после того как сказали о проблемах, где то через пару минут.
11 май 16, 10:56    [19156829]     Ответить | Цитировать Сообщить модератору
Все форумы / Microsoft SQL Server Ответить