Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

18278:Database log truncated:Database:XXX

Status
Not open for further replies.

francox

IS-IT--Management
Jul 19, 2001
26
CH
SQL 2K sp2 on NT4 EE SP6a.
During the DTS Import operation from the production Server (SQL 7.0 SP1) to the Test Server (SQL 2K SP2) I receive the following notification error on the NT application log:

EVENT ID: 17055
Source: MSSQLSERVER
Type: Error
category: Backup
Description:18278:
Database log truncated: Database: XXX

The operation of Import succeed, but I have the "red error" on my NT application log.

The package simply import a full database from one server to another server,tables, Views, Stored procedures, data,referential integrity constraints,security and indexes.It is a copy Sql Server objects Task.

The error is showing on the 2K Server.
The recovery model is set to full on the SQL 2K and the option "truncate log on checkpoint" is NOT set on the SQL 7.0 Server.

The question is that this is the only activity on the Server during the night.I have scheduled a full backup DB at 6.00 in the morning while the import DB is scheduled at 4.00.It may be that for some reason DTS set the DB in simple recovery mode and that is
why I receive this error?

One thing to note is that the category of the error on NT event log is "backup".
We have thirdparty backup tool with sql agent and in fact we backup the DB on the SQL 7.0 Server at 1.00 in the morning, then, at 4.00 in the morning, start the job that Import from the SQL 7.0 Server to the SQL 2K Server.

The package is on the SQL 2K so is the job.

The error happens a few seconds after the job (import) start.
The thirdparty backup is already done on the SQL 7.0 Server at 1.00 in the morning.
My Import starts at 4.00 in the morning and I have always this same error at the same time.

There is no other activity on the 2 servers, only the import job is running at that time.
Any idea?
Franco







 
Andrew Lambert on SQLmag forum tell me so:
"Check out Q308267 on support.microsoft.com The document implies that the problem is fixed in SP2 but there is no mention of it in the SP2 fixlist.

DTS changes the recovery model of the target DB, once you are out of Full model, the LSN sequence is wrong and logs won't restore."
Franco
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top