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

LOGS

hello, i get this error
Microsoft OLE DB Provider for SQL Server error '80040e14'
The log file for database 'autosmotos' is full. Back up the transaction log
for the database to free up some log space.
So i try to delete the LOF file with this command:
ALTER DATABASE [autosmotos]
REMOVE FILE [autosmotos_Log]
GO
But i get
The primary data or log file cannot be removed from a database
Q: how i can i set off this option or how can i empty the log file ?
Gerard.hi Gérard,
I'll do a shrink over that .LDF file or in the case that you would have
enough free space, you could make another LOG file in the same volume.
A question, what recovery model own your database? If your database contains
only 'development data' or 'test data' a good idea is have as simple model.
Current location: Alicante (ES)
"Gérard Leclercq" wrote:

> hello, i get this error
> Microsoft OLE DB Provider for SQL Server error '80040e14'
> The log file for database 'autosmotos' is full. Back up the transaction lo
g
> for the database to free up some log space.
>
> So i try to delete the LOF file with this command:
> ALTER DATABASE [autosmotos]
> REMOVE FILE [autosmotos_Log]
> GO
>
> But i get
> The primary data or log file cannot be removed from a database
>
> Q: how i can i set off this option or how can i empty the log file ?
>
> Gerard.
>
>
>|||underprocessable|||BACKUP LOG autosmotos WITH TRUNCATE_ONLY
GO
DBCC SHRINKFILE(autosmotos_LOG,1)
GO
You may then want to issue the following command :-
ALTER DATABASE autosmotos SET RECOVERY SIMPLE
But i would suggest reading up on this 1st
HTH. Ryan
"Grard Leclercq" <gl@.pasdemail.fr> wrote in message
news:MQ8Uf.330505$cT4.10333346@.phobos.telenet-ops.be...
>I work in hard conditions. The db is on a internetserver. I don't have
>access to the Enterprise so i have to ask, and ask, and ask my provider but
>i get no help. I found a trial version of a on-line manager. In attach some
>settings. Maybe this help.
> Is there an instruction to delete or schrink the log file or to turn it
> off ?
> "Enric" <vtam13@.terra.es.(donotspam)> schreef in bericht
> news:9033071E-3A41-42C8-85B2-A35FE6919F70@.microsoft.com...
>
>|||Thank you, the log is empty now(i suppose because the error is not longer
there)
gerard
"Ryan" <Ryan_Waight@.nospam.hotmail.com> schreef in bericht
news:uLJ7qSZTGHA.6084@.TK2MSFTNGP14.phx.gbl...
> BACKUP LOG autosmotos WITH TRUNCATE_ONLY
> GO
> DBCC SHRINKFILE(autosmotos_LOG,1)
> GO
> You may then want to issue the following command :-
> ALTER DATABASE autosmotos SET RECOVERY SIMPLE
> But i would suggest reading up on this 1st
> --
> HTH. Ryan
>
> "Grard Leclercq" <gl@.pasdemail.fr> wrote in message
> news:MQ8Uf.330505$cT4.10333346@.phobos.telenet-ops.be...
>