Welcome to Sign in | Help

Database SUSPECT - sql server 2005

  •  11-04-2008, 1:20 PM

    Database SUSPECT - sql server 2005

    salut,

    am si eu o problema cu cateva baze de date de pe un server 2005

    pe server sunt cam 20 baze de date dintre care dimineata am gasit 5 cu SUSPECT

    nu am backup-uri ca sa le pot face restore.....

    cum pot rezolva problema...nu am nici cea mai vaga idee cum sa recuperez datele

    momentan am facut doar:

    am rulat scriptul

    SELECT [Name], DBID, Status
    FROM master.dbo.sysdatabases
    GO

    Name DBID  Status
    master 1  65544
    tempdb 2  8
    model 3  65536
    msdb 4  65544
    GeckoDev 5  1073741849
    OctopusCentralProva 6  65544
    OpsBo 8  16
    MagazzinoRandom 9  4194328
    OctopusCentralDevClean  12 65536
    Dukes 14  16  suspect
    DBBackup 15  16
    Coco 16  4194328
    Celestina 17  4194328
    GustoOsteria 23  16  suspect
    OctopusBOLuca 25  4194328
    OpsAnticoArco 27  4194328
    OpsLibreria 28  16  suspect
    GeckoPiperno 34  1073741840  suspect
    AnticoCentral 35  1073807369
    AnticoCaffeOctopus 36  1077936153
    Random_CRM 37  1073741840  suspect
    CocomerinoCentral 41  1077936153
    OctopusCocomerino 42  1077936153
    OctopusCentralDev 45  65536

    am dat un restart la server si cateva si-au revenit, au mai ramas in suspect doar 2 si anume DUKES si RANDOM_CRM, ce as putea sa le fac?

    mai atasez si parte din log:

    11/01/2008 14:13:45,spid22s,Unknown,An error occurred during recovery<c/> preventing the database 'Dukes' (database ID 14) from restarting. Diagnose the recovery errors and fix them<c/> or restore from a known good backup. If errors are not corrected or expected<c/> contact Technical Support.
    11/01/2008 14:13:45,spid22s,Unknown,Error: 3414<c/> Severity: 21<c/> State: 1.
    11/01/2008 14:13:45,spid22s,Unknown,The log scan number (43842:31173:1) passed to log scan in database 'Dukes' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication<c/> re-create the publication. Otherwise<c/> restore from backup if the problem results in a failure during startup.

    multumesc mult.

    alex.

View Complete Thread
Powered by Community Server (Commercial Edition), by Telligent Systems