Nejčastěji odpovídající uživatel
Chyba pri zalohovani databazi (detected an error on page (1:0) in file...)

Dotaz
-
Zdravim,
chtel bych se zeptat, zda-li nemate zkusenost s nasleduji chybou:
[SQLSTATE 01000] (Message 3014) BACKUP 'db_adver' detected an error on page (1:0) in file 'D:\Dbs\db_adver.mdf'. [SQLSTATE 42000] (Error 3043) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013).
Chyba se projevuje jen obcas, napriklad po restartu SQL serveru je to tak z 80% ok a db lze zazalohovat a pod nekolika hodinach provozu jiz ne.
Jedna se o MS SQL 2008 Std + Win 2008 Std.
Rad doplnim cokoli, co je potreba, abych se tohoto problemu zbavil.
Dekuju moc,
Adam- Upravený A-d-a-m čtvrtek 28. května 2009 22:01
Odpovědi
-
Dobry vecer, takova chyba rozhodne nevesti nic dobreho... Zacal bych rozhodne kontrolou integrity databaze (DBCC CHECKDB). Jake pouzivate nastaveni pro validaci datovych stranek (Page Verify)? MP.
- Navržen jako odpověď Meisnerová Helena úterý 23. března 2010 8:26
- Označen jako odpověď KFL-MSMicrosoft employee neděle 20. února 2011 11:50
-
Vypada to podle vseho, ze se behem zalohovani nektera datova stranka obcas nacte chybne. To muze ukazovat na problem diskoveho driveru. Pouzivate certifikovane ovladace a je vas HW kompatibilni s SQL Serverem? Nejsou nahodou nejake souvisejici zaznamy v Event logu?
- Navržen jako odpověď Meisnerová Helena úterý 23. března 2010 8:26
- Označen jako odpověď KFL-MSMicrosoft employee neděle 20. února 2011 11:50
Všechny reakce
-
-
Ahoj,
dela mi to prevazne u tri databazi. Prvni má velikost 7.7GB, druha 4,4GB a treti 4.2GB. Je tam i nekolik mensich - radove v desitkach MB, ty jsou vetsinou bez problemu.
Server ma RAID 10 pole, slozene ze 4x400GB SAS. Je rozdelene na C: (100GB/52GB Free) a D:(670GB/480GB Free). Zalohy jsou nastaveny na D:\DbsBackup -> Pote jsou kopirovany na NAS.
Zalohu provadim jako JOB, ale uplne stejnou chybu to ukaze, pokud dam backup database rucne.
NTFS kompresi nepouzivam.
Dekuju moc za rekaci,
Adam -
Dobry vecer, takova chyba rozhodne nevesti nic dobreho... Zacal bych rozhodne kontrolou integrity databaze (DBCC CHECKDB). Jake pouzivate nastaveni pro validaci datovych stranek (Page Verify)? MP.
- Navržen jako odpověď Meisnerová Helena úterý 23. března 2010 8:26
- Označen jako odpověď KFL-MSMicrosoft employee neděle 20. února 2011 11:50
-
Ahoj,
provedl jsem kontrolu vsech DB. Vsechny testy jsou v poradku, viz jeden zkraceny vypis:
---------------------------------------------------------------------------------------------------------------------
DBCC results for 'ec'.
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
Service Broker Msg 9605, State 1: Conversation Priorities analyzed: 0.
DBCC results for 'sys.sysrscols'.
There are 1076 rows in 15 pages for object "sys.sysrscols".
DBCC results for 'sys.sysrowsets'.
.
.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'ec'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
---------------------------------------------------------------------------------------------------------------------
U vsech databazi mam nastaveno: PAGE_VERIFY na CHECKSUM.
Dekuji moc za reakci,
Adam
P.S.: Nakonec jeste pridam vypis z Job History u zalohovani
---------------------------------------------------------------------------------------------------------------------
Date 31.5.2009 1:00:00
Log Job History (backup)Step ID 1
Server SQL1
Job Name backup
Step Name BackupAll
Duration 00:04:14
Sql Severity 16
Sql Message ID 3013
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0Message
Executed as user: NT AUTHORITY\NETWORK SERVICE. 10 percent processed. [SQLSTATE 01000] (Message 3211) 20 percent processed. [SQLSTATE 01000] (Message 3211) 30 percent processed. [SQLSTATE 01000] (Message 3211) 40 percent processed. [SQLSTATE 01000] (Message 3211) 51 percent processed. [SQLSTATE 01000] (Message 3211) 61 percent processed. [SQLSTATE 01000] (Message 3211) 71 percent processed. [SQLSTATE 01000] (Message 3211) 81 percent processed. [SQLSTATE 01000] (Message 3211) 92 percent processed. [SQLSTATE 01000] (Message 3211) Processed 312 pages for database 'daybook', file 'daybook' on file 1. [SQLSTATE 01000] (Message 4035) 100 percent processed. [SQLSTATE 01000] (Message 3211) Processed 1 pages for database 'daybook', file 'daybook_log' on file 1. [SQLSTATE 01000] (Message 4035) BACKUP DATABASE successfully processed 313 pages in 0.180 seconds (13.585 MB/sec). [SQLSTATE 01000] (Message 3014) 10 percent processed. [SQLSTATE 01000] (Message 3211) 20 percent processed. [SQLSTATE 01000] (Message 3211) 30 percent processed. [SQLSTATE 01000] (Message 3211) 40 percent processed. [SQLSTATE 01000] (Message 3211) 50 percent processed. [SQLSTATE 01000] (Message 3211) 60 percent processed. [SQLSTATE 01000] (Message 3211) 70 percent processed. [SQLSTATE 01000] (Message 3211) 80 percent processed. [SQLSTATE 01000] (Message 3211) 90 percent processed. [SQLSTATE 01000] (Message 3211) Processed 292544 pages for database 'db_adver', file 'db_adver' on file 1. [SQLSTATE 01000] (Message 4035) 100 percent processed. [SQLSTATE 01000] (Message 3211) Processed 3 pages for database 'db_adver', file 'db_adver_log' on file 1. [SQLSTATE 01000] (Message 4035) BACKUP DATABASE successfully processed 292547 pages in 43.934 seconds (52.021 MB/sec). [SQLSTATE 01000] (Message 3014) 10 percent processed. [SQLSTATE 01000] (Message 3211) 20 percent processed. [SQLSTATE 01000] (Message 3211) 30 percent processed. [SQLSTATE 01000] (Message 3211) 40 percent processed. [SQLSTATE 01000] (Message 3211) 50 percent processed. [SQLSTATE 01000] (Message 3211) 60 percent processed. [SQLSTATE 01000] (Message 3211) 70 percent processed. [SQLSTATE 01000] (Message 3211) 80 percent processed. [SQLSTATE 01000] (Message 3211) 90 percent processed. [SQLSTATE 01000] (Message 3211) Processed 915584 pages for database 'ec', file 'ec' on file 1. [SQLSTATE 01000] (Message 4035) 100 percent processed. [SQLSTATE 01000] (Message 3211) Processed 12 pages for database 'ec', file 'ec_log' on file 1. [SQLSTATE 01000] (Message 4035) BACKUP DATABASE successfully processed 915596 pages in 205.274 seconds (34.846 MB/sec). [SQLSTATE 01000] (Message 3014) 10 percent processed. [SQLSTATE 01000] (Message 3211) 21 percent processed. [SQLSTATE 01000] (Message 3211) 32 percent processed. [SQLSTATE 01000] (Message 3211) 40 percent processed. [SQLSTATE 01000] (Message 3211) 51 percent processed. [SQLSTATE 01000] (Message 3211) 61 percent processed. [SQLSTATE 01000] (Message 3211) 70 percent processed. [SQLSTATE 01000] (Message 3211) 80 percent processed. [SQLSTATE 01000] (Message 3211) 91 percent processed. [SQLSTATE 01000] (Message 3211) Processed 296 pages for database 'felix', file 'webftp' on file 1. [SQLSTATE 01000] (Message 4035) 100 percent processed. [SQLSTATE 01000] (Message 3211) Processed 1 pages for database 'felix', file 'webftp_log' on file 1. [SQLSTATE 01000] (Message 4035) BACKUP DATABASE successfully processed 297 pages in 0.178 seconds (13.035 MB/sec). [SQLSTATE 01000] (Message 3014) BACKUP 'shop' detected an error on page (1:0) in file 'D:\Dbs\shop.mdf'. [SQLSTATE 42000] (Error 3043) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed. -
Vypada to podle vseho, ze se behem zalohovani nektera datova stranka obcas nacte chybne. To muze ukazovat na problem diskoveho driveru. Pouzivate certifikovane ovladace a je vas HW kompatibilni s SQL Serverem? Nejsou nahodou nejake souvisejici zaznamy v Event logu?
- Navržen jako odpověď Meisnerová Helena úterý 23. března 2010 8:26
- Označen jako odpověď KFL-MSMicrosoft employee neděle 20. února 2011 11:50