Every few days (4 to 7 days), I got this error message. I have included the
complete error below. Is this something to do with my
maintenance/backup/recovery plan setting?
Thanks to your help.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(6)
Event ID:17055
Date:1/3/2005
Time:10:00:04 PM
User:NT AUTHORITY\SYSTEM
Computer:BELDISP2
Description:
18278 :
Database log truncated: Database: PowerBiz.
Data:
0000: 66 47 00 00 10 00 00 00 fG.....
0008: 09 00 00 00 42 00 45 00 ...B.E.
0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
0018: 50 00 32 00 00 00 09 00 P.2....
0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
0028: 65 00 72 00 42 00 69 00 e.r.B.i.
0030: 7a 00 00 00 z...
What recovery mode is this DB in? Are there any scheduled jobs that are
issuing a Truncate Log or Backp Log with Truncate?
Andrew J. Kelly SQL MVP
"Abel Chan" <awong@.newsgroup.nospam> wrote in message
news:E1D93214-50C0-4573-A00A-EF83E853FC93@.microsoft.com...
> Hi there,
> Every few days (4 to 7 days), I got this error message. I have included
> the
> complete error below. Is this something to do with my
> maintenance/backup/recovery plan setting?
> Thanks to your help.
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (6)
> Event ID: 17055
> Date: 1/3/2005
> Time: 10:00:04 PM
> User: NT AUTHORITY\SYSTEM
> Computer: BELDISP2
> Description:
> 18278 :
> Database log truncated: Database: PowerBiz.
> Data:
> 0000: 66 47 00 00 10 00 00 00 fG.....
> 0008: 09 00 00 00 42 00 45 00 ...B.E.
> 0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
> 0018: 50 00 32 00 00 00 09 00 P.2....
> 0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
> 0028: 65 00 72 00 42 00 69 00 e.r.B.i.
> 0030: 7a 00 00 00 z...
>
|||First of all, this is NOT an error message, it is an Application Event log
event entry. Informational. Issued by SQL Server.
The message says that the System explicitly truncated the transaction log.
Depending on your current database recovery mode setting, this may or may not
be an issue.
If the database is currently set to SIMPLE recovery, then there would be no
need to truncate the transaction log--it would happen automatically with
every checkpoint process.
On the other hand, if you are in Bulk_Logged or Full recovery, then
truncating the transaction log could render your database unrecoverable.
You'd have to restore the database from backup.
There are two possible recommendations:
1. Create a Full backup immediately after a truncate log action.
2. Initiate a transaction log backup schedule and stop truncating the log
entirely.
Sincerely,
Anthony Thomas
"Abel Chan" wrote:
> Hi there,
> Every few days (4 to 7 days), I got this error message. I have included the
> complete error below. Is this something to do with my
> maintenance/backup/recovery plan setting?
> Thanks to your help.
> Event Type:Error
> Event Source:MSSQLSERVER
> Event Category:(6)
> Event ID:17055
> Date:1/3/2005
> Time:10:00:04 PM
> User:NT AUTHORITY\SYSTEM
> Computer:BELDISP2
> Description:
> 18278 :
> Database log truncated: Database: PowerBiz.
> Data:
> 0000: 66 47 00 00 10 00 00 00 fG.....
> 0008: 09 00 00 00 42 00 45 00 ...B.E.
> 0010: 4c 00 44 00 49 00 53 00 L.D.I.S.
> 0018: 50 00 32 00 00 00 09 00 P.2....
> 0020: 00 00 50 00 6f 00 77 00 ..P.o.w.
> 0028: 65 00 72 00 42 00 69 00 e.r.B.i.
> 0030: 7a 00 00 00 z...
>
|||Hi Andrew and Anthony,
Thanks to you both for the prompt response. Really appreciate this level of
support.
I think this event log is related to the way we create our maintenance plan
as I stated in another request:
http://msdn.microsoft.com/newsgroups...xp=&sloc=en-us
Currently, our maintenance plan combines both master and the User databases
together. It also selects Transaction Log Backup option. Transaction Log
Backup always failed under the SQL Server Agent Jobs list.
Since disk space is not an issue at this point, I am thinking to restructure
the maintenance plan. Please let me know if you would also recommend the
following measure to protect our data. If you have a better idea which I
believe you definitely have, please let me know also. Again, thanks so much
for your help and support.
Maintenance Plan for System databases
1. Select Recovery mode Simple for master.
2. Select Recovery mode Full for model.
3. Select Recovery mode Simple for msdb.
4. Create a maintenance plan for these system databases.
5. Select all options (Reorganize data and index pages, check database
integrity, back up the database as part of the maintenance plan and etc)
except backup the transaction log.
Maintenance Plan for the User database
1. Select Recovery mode Full for the User database.
2. Create a maintenance plan for the User database.
5. Select all options (Reorganize data and index pages, check database
integrity, back up the database as part of the maintenance plan and etc)
including backup the transaction log.
Additional information: We have a Raid 5 disk array on our production
database server. We copy the database backup into a backup library and
another backup server.
"Andrew J. Kelly" wrote:
> What recovery mode is this DB in? Are there any scheduled jobs that are
> issuing a Truncate Log or Backp Log with Truncate?
> --
> Andrew J. Kelly SQL MVP
>
> "Abel Chan" <awong@.newsgroup.nospam> wrote in message
> news:E1D93214-50C0-4573-A00A-EF83E853FC93@.microsoft.com...
>
>
|||That is fine with a few exceptions. There is no need to do the
optimizations on the system dbs since the maint plan uses DBREINDEX which is
not valid for system tables anyway. Make sure you don't have it set to
shrink the databases or logs as part of the MP or as an option for the DB's.
Andrew J. Kelly SQL MVP
"Abel Chan" <awong@.newsgroup.nospam> wrote in message
news:98779723-E9A8-45C4-B90D-6E7E4598AEE0@.microsoft.com...[vbcol=seagreen]
> Hi Andrew and Anthony,
> Thanks to you both for the prompt response. Really appreciate this level
> of
> support.
> I think this event log is related to the way we create our maintenance
> plan
> as I stated in another request:
> http://msdn.microsoft.com/newsgroups...xp=&sloc=en-us
> Currently, our maintenance plan combines both master and the User
> databases
> together. It also selects Transaction Log Backup option. Transaction Log
> Backup always failed under the SQL Server Agent Jobs list.
> Since disk space is not an issue at this point, I am thinking to
> restructure
> the maintenance plan. Please let me know if you would also recommend the
> following measure to protect our data. If you have a better idea which I
> believe you definitely have, please let me know also. Again, thanks so
> much
> for your help and support.
> Maintenance Plan for System databases
> 1. Select Recovery mode Simple for master.
> 2. Select Recovery mode Full for model.
> 3. Select Recovery mode Simple for msdb.
> 4. Create a maintenance plan for these system databases.
> 5. Select all options (Reorganize data and index pages, check database
> integrity, back up the database as part of the maintenance plan and etc)
> except backup the transaction log.
> Maintenance Plan for the User database
> 1. Select Recovery mode Full for the User database.
> 2. Create a maintenance plan for the User database.
> 5. Select all options (Reorganize data and index pages, check database
> integrity, back up the database as part of the maintenance plan and etc)
> including backup the transaction log.
> Additional information: We have a Raid 5 disk array on our production
> database server. We copy the database backup into a backup library and
> another backup server.
> "Andrew J. Kelly" wrote:
|||Got it!!!
Thanks so much for your help.
You are really a MVP - quick, care, and to the point.
Abel Chan
"Andrew J. Kelly" wrote:
> That is fine with a few exceptions. There is no need to do the
> optimizations on the system dbs since the maint plan uses DBREINDEX which is
> not valid for system tables anyway. Make sure you don't have it set to
> shrink the databases or logs as part of the MP or as an option for the DB's.
> --
> Andrew J. Kelly SQL MVP
>
> "Abel Chan" <awong@.newsgroup.nospam> wrote in message
> news:98779723-E9A8-45C4-B90D-6E7E4598AEE0@.microsoft.com...
>
>
No comments:
Post a Comment