| Author |
Topic |
|
fredong
Yak Posting Veteran
80 Posts |
 Posted - 2005-09-14 : 13:42:57
|
| When try to restore the transaction log from legato and I got this error. Please advise.748] RESTORE transaction [CopyOfOklahoma_Test1] FROM virtual_device='Legato#bbe5d927-0dd3-44d7-8342-ee52e3a2667c'[748] G:\rt_2002_1Q\nsr\db_apps\bsmsql\nsrsqlado.cpp(1641): ExecuteFailed event arrived.[748] Microsoft SQL Server Provider error:[748] [Microsoft][ODBC SQL Server Driver][SQL Server]The log in this backup set begins at LSN 110000000011300001, which is too late to apply to the database. An earlier log backup that includes LSN 102000000188100001 can be restored..[748] [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG is terminating abnormally..[748] Thread 2984 exited with status 2304.k |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-09-14 : 13:52:47
|
| You are trying to restore a transaction log but you have skipped one that needs to be applied still. You have to start with a full backup and the entire transaction log chain. You can't skip a single tlog. You could have a differential in between there, but you still the entire tlog chain after the diff. So if you want to restore this tlog, you need to figure out which tlogs you are missing and apply those first.Tara |
 |
|
|
fredong
Yak Posting Veteran
80 Posts |
Posted - 2005-09-15 : 09:07:29
|
| I have restored in order but still ran into this problem. We have backup the log every hour from 8 am to 8 pm and for somehow after i restored the 8 am to 1pm and then tried to restore the 2 pm and it returned this error. I have checked with my developer and during the 1pm to 2pm time they have done a copy wizard on 3 store procedures and accidentally copy the tables as well which they not supposed to, to another database and for somehow it create a mess in the database. Is there way to make correction on the 2pm log by not committing the copy wizard or remove it?k |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-09-15 : 12:15:56
|
quote:
I have restored in order but still ran into this problem.
You are missing one of the transaction logs, which is why you are encountering that error. The copy wizard did not create this problem. Perhaps someone ran a transaction log backup outside of your backup routines. There is nothing preventing anyone from doing this.Tara |
|
|
|
fredong
Yak Posting Veteran
80 Posts |
Posted - 2005-09-15 : 12:21:33
|
| is there a way to look at the what LSN # in a log?k |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-09-15 : 12:24:57
|
| The only way that I know of is to attempt restoring it.Tara |
|
|
|
madamala
Starting Member
1 Post |
Posted - 2005-09-29 : 16:21:02
|
| Try this..........select database_name, backup_finish_date, type, [name], user_name, first_lsn, last_lsn, * from backupsetwhere database_name = 'XXX'order by 2It gives you the lsn.........But you can check the other retreived columns to see if any backups were done outside of your routines |
|
|
|
fredong
Yak Posting Veteran
80 Posts |
Posted - 2005-09-29 : 16:38:43
|
| what database is the backupset located?k |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-09-29 : 20:30:21
|
quote:
Originally posted by fredong
what database is the backupset located?k
msdbTara |
|
|
|
|
The log in this backup set begins at LSN 110000000