Database log truncated error message in CallManager EventViewer

Answered Question
Apr 15th, 2007
User Badges:

I have Call Manager 4.1(3) with BARS 4.0.6000. CM tunes for making backup every night and every time I see two error messages in EventViewer:



Event Type: Error

Event Source: MSSQLSERVER

Event Category: (6)

Event ID: 17055

Date: 4/15/2007

Time: 2:00:25 AM

User: ELVARY-CCMP\BackAdmin

Computer: ELVARY-CCMP

Description:

18278 :

Database log truncated: Database: CDR.

Data:

0000: 66 47 00 00 10 00 00 00 fG......

0008: 0c 00 00 00 45 00 4c 00 ....E.L.

0010: 56 00 41 00 52 00 59 00 V.A.R.Y.

0018: 2d 00 43 00 43 00 4d 00 -.C.C.M.

0020: 50 00 00 00 04 00 00 00 P.......

0028: 43 00 44 00 52 00 00 00 C.D.R...




and




Event Type: Error

Event Source: MSSQLSERVER

Event Category: (6)

Event ID: 17055

Date: 4/15/2007

Time: 2:00:07 AM

User: ELVARY-CCMP\BackAdmin

Computer: ELVARY-CCMP

Description:

18278 :

Database log truncated: Database: Ccm0300.

Data:

0000: 66 47 00 00 10 00 00 00 fG......

0008: 0c 00 00 00 45 00 4c 00 ....E.L.

0010: 56 00 41 00 52 00 59 00 V.A.R.Y.

0018: 2d 00 43 00 43 00 4d 00 -.C.C.M.

0020: 50 00 00 00 08 00 00 00 P.......

0028: 43 00 43 00 4d 00 30 00 C.C.M.0.

0030: 33 00 30 00 30 00 00 00 3.0.0...


At the same time backup files is create.

Does anyone know what do the errors mean? Can they lead restore process to fail?




Correct Answer by jbarcena about 10 years 2 months ago

The event that you see in the App log is not a problem. It is telling you the SQL backup

has completed and as such the transactional logs are not needed and so are deleted. This

is so because if we keep the transactional logs the size of the Database will increase

causing disk space shortage and hence we will have issues with services stopping.


MCS BackupUtility by default " deletes " the transactional [ ART / CDR ] logs after a

backup. When this is done you will see the error you mention. This is nothing to worry

about. MCSBackup basically reduces/removes unnecessary data to be backed up, grab a copy

of the database, and backup this copy to the stream file. I think it would be better that

message type is changed from Error to Information by Microsoft.


Microsoft has already announced this issue :


http://support.microsoft.com/default.aspx?scid=kb;en-us;818202


Upon research, I also found that this error is basically due to two different Bugs in

Microsoft. Here is the link which gives us more information on this :



http://proxify.com/p/000010A/http/support.microsoft.com/default.aspx?scid=kb;en-us;308267


So again in short nothing to worry about - just informational message that the

transactional logs have been truncated [ deleted ]. Do let me know if I could be of

further help or if I could proceed with closure of this SR. Thank you and you have a nice

day ahead.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
gary.mattson Mon, 04/16/2007 - 12:31
User Badges:

It's a normal occurrence as part of the SQL backup procedure and can be safely ignored.

Correct Answer
jbarcena Mon, 04/16/2007 - 12:39
User Badges:
  • Red, 2250 points or more

The event that you see in the App log is not a problem. It is telling you the SQL backup

has completed and as such the transactional logs are not needed and so are deleted. This

is so because if we keep the transactional logs the size of the Database will increase

causing disk space shortage and hence we will have issues with services stopping.


MCS BackupUtility by default " deletes " the transactional [ ART / CDR ] logs after a

backup. When this is done you will see the error you mention. This is nothing to worry

about. MCSBackup basically reduces/removes unnecessary data to be backed up, grab a copy

of the database, and backup this copy to the stream file. I think it would be better that

message type is changed from Error to Information by Microsoft.


Microsoft has already announced this issue :


http://support.microsoft.com/default.aspx?scid=kb;en-us;818202


Upon research, I also found that this error is basically due to two different Bugs in

Microsoft. Here is the link which gives us more information on this :



http://proxify.com/p/000010A/http/support.microsoft.com/default.aspx?scid=kb;en-us;308267


So again in short nothing to worry about - just informational message that the

transactional logs have been truncated [ deleted ]. Do let me know if I could be of

further help or if I could proceed with closure of this SR. Thank you and you have a nice

day ahead.


Actions

This Discussion