error in starting DB coz of a secondary log file

  • HI DBA's,

    I have issue in starting a DB..

    details:

    I have created secondary log file in separate drive to perform an activity,late it was removed in DB Property.

    yesterday backup was taken for the DB to do some activity and later it was restored.today morning the server was restarted and the DB was not getting started with the error(PFA).

    thanks in advance!

  • What was the exact order things were done in, and what exactly was done?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • thanks for the reply..

    1)added secondary log file to the DB.

    2)deleted the secondary log file via DB properties.

    3)took a full backup.

    4)restored the backup(from point 3 backup)

    5)server gets restarted.

    6)the DB doesnโ€™t come online.

    the error message was from errorlog after restart of the server.

    ๐Ÿ™

  • After step 4 everything was working?

    Can you restore the backup again?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • kesavan.rv (8/11/2014)


    HI DBA's,

    I have issue in starting a DB..

    details:

    I have created secondary log file in separate drive to perform an activity,late it was removed in DB Property.

    yesterday backup was taken for the DB to do some activity and later it was restored.today morning the server was restarted and the DB was not getting started with the error(PFA).

    thanks in advance!

    Because no checkpoint occurred the deleted file was still part of the system catalog. When deleting a file either a checkpoint for simple recovery databases or a log backup for full recovery databases removes the system catalog entry for the deleted file.

    Try taking a fresh backup of the database and execute the following against both the backup files, you'll likely see a difference in the output

    RESTORE FILELISTONLY FROM DISK = 'drive:\somepath\yourbackupfilename.bak'

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" ๐Ÿ˜‰

  • Ya,the DB was working fine..currently I am restoring the DB..

  • Perry Whittle,

    currently I am restoring the DB from the backup(backup of step 3).once the restore is done should I take a log-backup backup(DB is in full recovery) to fix this issue?

    thanks..

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply