November 23, 2012 at 12:32 am
After principal server crushes trying to activate mirror and getting error message below while trying to execute query below:
Msg 4303, Level 16, State 1, Line 1
The roll forward start point is now at log sequence number (LSN) 3992000004364800001. Additional roll forward past LSN 3992000004424800001 is required to complete the restore sequence.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris
November 23, 2012 at 1:14 am
Could you post the T-SQL Statement that you used to perform the restore?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
November 23, 2012 at 1:23 am
restore database clinic with recovery
“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris
November 23, 2012 at 2:11 am
From Books Online:
FORCE_SERVICE_ALLOW_DATA_LOSS
Forces database service to the mirror database after the principal server fails with the database in an unsynchronized state or in a synchronized state when automatic failover does not occur.
We strongly recommend that you force service only if the principal server is no longer running. Otherwise, some clients might continue to access the original principal database instead of the new principal database.
FORCE_SERVICE_ALLOW_DATA_LOSS is available only on the mirror server and only under all the following conditions:
The principal server is down.
WITNESS is set to OFF or the witness is connected to the mirror server.
Force service only if you are willing to risk losing some data in order to restore service to the database immediately. For information about alternatives to forcing service, see Asynchronous Database Mirroring (High-Performance Mode).
Forcing service suspends the session, temporarily preserving all the data in the original principal database. Once the original principal is in service and able to communicate with the new principal server, the database administrator can resume service. When the session resumes, any unsent log records and the corresponding updates are lost.
ALTER DATABASE <dbname> SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS;
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
November 23, 2012 at 2:13 am
Was your intent to restore additional backups?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
November 23, 2012 at 2:18 am
Welsh Corgi (11/23/2012)
Was your intent to restore additional backups?
He's trying to fail database mirroring over to the mirror after the principal crashed.
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
November 23, 2012 at 3:22 am
Trying to make mirror the principal ,principal no longer available.
“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris
November 23, 2012 at 3:29 am
Basically am running two statements:
1.alter databasename set partner off
2.restore databasename with recovery
It is the second statement that is failing,so are suggesting that after restore databasename with recovery gives an error can run ALTER DATABASE <dbname> SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS;?
“When I hear somebody sigh, ‘Life is hard,’ I am always tempted to ask, ‘Compared to what?’” - Sydney Harris
November 23, 2012 at 4:23 am
Hi,
1st you execute
ALTER DATABASE Dbname SET PARTNER OFF
Then you execute below query
RESTORE DATABASE Dbname WITH RECOVERY
It will work..
Satish
November 23, 2012 at 10:56 am
kapfundestanley (11/23/2012)
Basically am running two statements:1.alter databasename set partner off
2.restore databasename with recovery
It is the second statement that is failing,so are suggesting that after restore databasename with recovery gives an error can run ALTER DATABASE <dbname> SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS;?
No. INSTEAD OF. Don't drop mirroring and recover the database at all. Force service on the mirror so that mirroring is preserved. If you drop mirroring, then your apps that try to connect to it via the "failover partner" attribute will fail. It will only allow connections to the "failover partner" if that partner is in a database mirroring session.
November 23, 2012 at 10:57 am
saidapurs (11/23/2012)
Hi,1st you execute
ALTER DATABASE Dbname SET PARTNER OFF
Then you execute below query
RESTORE DATABASE Dbname WITH RECOVERY
It will work..
Satish
Wrong advice. You should be advising him to force service on the mirror.
August 1, 2014 at 4:21 pm
Hi All,
we are also facing same problem when we try to execute "restore database SID with recovery" command, can you help us with solution.
Msg 4303, Level 16, State 1, Line 1
The roll forward start point is now at log sequence number (LSN) 59802000006517200023. Additional roll forward past LSN 59802000006529000001 is required to complete the restore sequence.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
Regards,
Vino
August 1, 2014 at 4:35 pm
Please start a new thread. Don't piggyback. </etiquette lesson>
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply