Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Error / Car Scheduler / Physical Log size 20000 is too small.

Hello,

CUCM version : 8.6.2 on vmware.

Every day at 1H, I've got theses two warnings :

At Fri Dec 30 00:56:36 CET 2011 on node 192.168.80.20, the following SyslogSeverityMatchFound events generated:

SeverityMatch : Critical

MatchedEvent : Dec 30 00:56:11 pbxtela01 local7 2 : 1: padeobxtela01.hq.corp.leroymerlin.com: Dec 29 2011 23:56:11.342 UTC : %UC_CAR-2-CARIDSEngineCritical: %[ClassID=pbxtela01_car8_6_2_20000_2-7][ClassMsg=Dynamic Server Initialization failure.][Specific-Msg=WARNING! Physical Log size 20000 is too small.           Physical Log overflows may occur during peak activity.           Recomme][AppID=Cisco CAR Scheduler][ClusterID=][NodeID=padeobxtela01]: Pay Attention. This alarm does not compromise data or prevent the use of the system.

AppID : Cisco Syslog Agent

ClusterID :

NodeID : pbxtela01

TimeStamp : Fri Dec 30 00:56:11 CET 2011

ClassID : pbxtela01_car8_6_2_20000_2-7 ClassMsg : Dynamic Server Initialization failure.

Specific-Msg : WARNING! Physical Log size 20000 is too small.

         Physical Log overflows may occur during peak activity.

         Recomme

AppID : Cisco CAR Scheduler

ClusterID :

NodeID : pbxtela01

TimeStamp : Fri Dec 30 00:56:11 CET 2011.

The alarm is generated on Fri Dec 30 00:56:11 CET 2011.

Is there a solution two avoid these two messages ?

Best regards.

Everyone's tags (3)
4 REPLIES
New Member

Re: Error / Car Scheduler / Physical Log size 20000 is too small

I am seeing the same problem on my 8.6.2.20000-2 server.  Any resolution to this?

New Member

Re: Error / Car Scheduler / Physical Log size 20000 is too small

Hello,

the messages disappeared all alone.

Best regards

Cisco Employee

Error / Car Scheduler / Physical Log size 20000 is too small.

Searched and found the information as below.

The reason of the physical log overflow is below: 

The physical log can overflow if you use simple large objects or smart large
objects in a database with transaction logging turned off, as the following
example shows.


When the database server processes these simple large objects, each portion
of the simple large object that the database server stores on disk can be
logged separately, allowing the thread to exit the critical sections of code
between each portion.  However, if logging is turned off, the database
server must carry out all operations on the simple large object in one
critical section.  If the simple large object is large and the physical log
small, this scenario can cause the physical log to become full. 

However, there is no action required due to no system impact.

Recommended minimum Physical Log size is 160 times maximum concurrent user
threads.

This alarm is not a concern, there was no system or database problem.
New Member

Error / Car Scheduler / Physical Log size 20000 is too small.

I am also getting this issue on 8.6.2asu2 system.  I found this bug:

CSCtt44392 Bug Details

Increase log file size for informix in CAR
Symptom:
RTMT alert is generated:

ClassID : se015a_cm21a_car8_6_2_21001_1-7
ClassMsg : Dynamic Server Initialization failure.
Specific-Msg : WARNING! Physical Log size 20000 is too small.
Physical Log overflows may occur during peak activity.
Recomme
AppID : Cisco CAR Scheduler

Conditions:

Upgrade was done to 8.6.2 ES and we see this alert in RTMT.

Workaround:

None. It is not service effecting.

4214
Views
0
Helpful
4
Replies
CreatePlease login to create content