logshipping error

Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][OD
BC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS AdviceSounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:

>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][O
DBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>|||yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon

logshipping error

Hi Guys,
i am using log shipping in sql server 2000(sp3) but in loading in the
destination it is giving following error
Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
transaction ID (0:90997930), on page (1:783096),
in the source database there are no problems now but there wsa one index
corruption and loss of data.
pLS Advice
Sounds like the corruption on the primary DB has put the tlog syncs out
of whack (that's the technical term for it). I would resync from a
recent full DB backup (and subsequent log backups) that was done AFTER
the corruption was fixed. (This might mean a complete resync of the log
shipping pair for you using the DB maint wizard.)
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
bijupg@.hotmail.com wrote:

>Hi Guys,
>i am using log shipping in sql server 2000(sp3) but in loading in the
>destination it is giving following error
>Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3456: [Microsoft][ODBC SQL
>Server Driver][SQL Server]Could not redo log record (8078:18995:3), for
>transaction ID (0:90997930), on page (1:783096),
>in the source database there are no problems now but there wsa one index
>corruption and loss of data.
>pLS Advice
>
|||yes.
Sounds like you need to Re-Synch the DBs
Greg Jackson
PDX, Oregon

Logshipping

Hi

I have a problem in logshipping any one help would be appreciated.

during logshipping when i am adding data (log.data,transactlog)to the
destination database when i select the destination server name(server2)it
didn't showing any drives present .instead showing local drives.if i select
3rd server then it shows perfect all the available drives .If any one knows
the error please let me know u help would be appreciated.

Thanks,
pardhi

--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forum...eneral/200509/1I don't really know, but I would first look at permissions - the MSSQL
service account may not be able to access some drives. If this isn't
helpful, you should give some more details - exactly which dialogue
you're looking at (I guess you're using the maintenance plan wizard?),
which drives you can see, which drives you can't see (are they local
drives, mapped network drives, UNC paths...), what happens if you use
sp_add_log_shipping_plan directly etc.

Simon|||Thanks simon for your response.

Its weired working from home and not from office.

Thanks

Simon Hayes wrote:
>I don't really know, but I would first look at permissions - the MSSQL
>service account may not be able to access some drives. If this isn't
>helpful, you should give some more details - exactly which dialogue
>you're looking at (I guess you're using the maintenance plan wizard?),
>which drives you can see, which drives you can't see (are they local
>drives, mapped network drives, UNC paths...), what happens if you use
>sp_add_log_shipping_plan directly etc.
>Simon

--
Message posted via http://www.sqlmonster.com|||Hello, Iam also having similer problem.. would be interested to see more
coments.

Thanks,

--
admin

Admin

http://www.exforsys.com
http://www.geekinterview.com
http://www.itquestionbank.com
http://www.myitblog.com
----------------------
admin's Profile: http://www.exforsys.com/forum/member.php?userid=1
View this thread: http://www.exforsys.com/forum/showthread.php?t=5864|||Hello, I am having similer problem.. would be interested to see more
comments in detail..

Thanks,

--
techguru
----------------------
techguru's Profile: http://www.exforsys.com/forum/member.php?userid=9401
View this thread: http://www.exforsys.com/forum/showthread.php?t=5864