RE: Log Reader Error
- From: "Ken Roberts" <KenRoberts@xxxxxxxxxxxxxxxxx>
- Date: Mon, 14 Nov 2005 13:17:09 -0800
Michael,
I have performed the steps listed. The DBCC produced no errors. I will
repost tomorrow to let you know if the DTS job continues to cause the error.
Thanks,
Ken
"Michael Cheng [MSFT]" wrote:
> Hi Ken,
>
> Welcome to use MSDN Managed Newsgroup!
>
> From your descriptions, I understood you encounter the error message 9003:
> The LSN (2081235:261:1) passed to log scan in database 'StarDatabase' is
> invalid. If I have misunderstood your concern, please feel free to point it
> out.
>
> If you see this message during startup when the SQL Server process tries to
> recover the database or as a result of an ATTACH statement, the log file
> for the database is corrupted. If you see the message during a restore
> process, the backup file is corrupted. If you see this message during a
> replication process, the replication metadata may be incorrect.
>
> Based on my knowledge, this error message might be generated when the log
> sequence number (LSN) in the transaction log of the published database does
> not match the LSN in the distribution database for that publication.
>
>
>
> Please follow the steps below and let me know the result (recreate the
> whole replication)
>
>
>
> 1. In Enterprise Manager, in Tools/Replication, select Generate SQL Script
> to create a script for the current replication setup, in order to recreate
> the same replication later.
>
>
>
> 2. Use Enterprise Manager to drop the publication.
>
>
>
> 3. On the published_db in Query Analyzer, run the following code:
>
>
>
> EXEC sp_repldone NULL, NULL, 0, 0, 1
>
>
>
> 4. Back up or truncate the transaction log of the published database with
> one of the following commands:
>
>
>
> BACKUP LOG 'dbname' TO DISK = '[Backup Device]'
>
> -- Use this command to take a backup of the log.
>
>
>
> -or-
>
>
>
> BACKUP LOG 'dbname' WITH TRUNCATE_ONLY
>
> -- This command will truncate the log and does not back up the log.
>
>
>
> -or-
>
>
>
> BACKUP LOG 'dbname' WITH NO_LOG
>
> -- Use only if your transaction log is full and you cannot run the
> previous
> commands.
>
>
>
> NOTE: If you truncate the log with NO_LOG or TRUNCATE_ONLY, the changes
> recorded in the log are not recoverable. For recovery purposes, immediately
> execute BACKUP DATABASE. For more information on these log backup options,
> see the
> topic BACKUP in SQL Server Books Online.
>
>
>
> 5. Run DBCC CHECKDB(<Database Name>) on the published database to make sure
> that there are no problems with the database before creating a new
> publication.
>
>
>
> 6. Re-create the publication.
>
>
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
>
> Sincerely yours,
>
> Michael Cheng
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
.
- Follow-Ups:
- RE: Log Reader Error
- From: Michael Cheng [MSFT]
- RE: Log Reader Error
- References:
- RE: Log Reader Error
- From: Michael Cheng [MSFT]
- RE: Log Reader Error
- Prev by Date: Re: Alternative to vertical partitioning??
- Next by Date: Re: Transactional Replication
- Previous by thread: RE: Log Reader Error
- Next by thread: RE: Log Reader Error
- Index(es):
Relevant Pages
|
