30023 DATA RANGE on Callmanager 5.x

Answered Question
Jan 21st, 2008
User Badges:
  • Events Top Contributors,

    External, 2014

hi,

I would like to know if somebody knows how i can fix the issue of data range on a callmanager 5.x ? I have found solutions for 3.x or 4.x only, like the link below: http://www.ciscotaccc.com/kaidara-advisor/voice/showcase?case=K83216461

Correct Answer by Rob Huffman about 9 years 4 months ago

Hi Guilherme,


I think you may be hitting one of these bugs which both give the Error 30023;


CSCsl69542 Bug Details


CAR not able to load CDR flat files after W1 migration

Symptom:


After upgrade from callmanager 4.x to callmanager 6.0.1, CAR is not able to load CDR flat files into CAR DB.


Conditions:


Upgrade from callmanager 4.x to callmanager 6.0.1 with CAR


Workaround:


Run the following queries fro CLI:


Run sql Select max(Error_Record_Id) from car:tbl_error_id_map


returned


Get the result of above query as and run the following:


Run sql update car:tbl_system_preferences set param_value= where param_name='MAX_ERROR_RECORD_ID'


for example, if "max(Error_Record_Id) from car:tbl_error_id_map" return 100, then please update 'MAX_ERROR_RECORD_ID' as 101.


Further Problem Description:


When CDR load failed, in CAR scheduler traces,


ERROR [DailyCdrLoad] beans.EBErrorIdMap -save(): SQL Error while saving data java.sql.SQLException: Unique constraint informix.pktbl_error_id_map_01) violated.


is found.

1st Found-In

6.0


Fixed-In

6.0(1.2120.1)

7.0(0.39000.6)

5.1(3.1111.1)




CSCsk99713 Bug Details


Loader does not start until next schedule if it is detected running

Symptom:

CAR loader does not start until its next schedule time. If 'Continuous Loading 24/7' is

enabled and such timing/racing condition happens, loader will skip at most up

to 24 hours of a window for loading CDRs/CMRs. Hence new records will have a

delay to be loaded into CAR database for reporting.


Note: Besides "DailyCdrLoad", this condition can happen to: "DatabaseAlert" or

"DeleteReports" or "DatabaseMaintenance" or "TaskMonitor", although the chances

are less than "DailyCdrLoad" loader.


Conditions:

This is an interim case and should not happen very often. And tt's likely to happen

if we have 'Continuous Loading 24/7' enabled and running for days or weeks.


Workaround:

Simply restart 'CAR Scheduler' service, if one suspects a delay on CDR loading

caused by this issue.


Further Problem Description:

If waiting or delay is not an issue, the workaround can be simply do nothing,

and scheduler will reschedule things (repouplate schedules) again in midnight 00:00,

and loader will start off to load CDRs again every midnight continuously.

1st Found-In

6.1

5.0

5.1

6.0


Fixed-In

6.1(0.9901.430)

5.1(3.9901.22)

6.1(1.1000.11)


Hope this helps!

Rob

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Rob Huffman Tue, 01/22/2008 - 07:37
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Guilherme,


I think you may be hitting one of these bugs which both give the Error 30023;


CSCsl69542 Bug Details


CAR not able to load CDR flat files after W1 migration

Symptom:


After upgrade from callmanager 4.x to callmanager 6.0.1, CAR is not able to load CDR flat files into CAR DB.


Conditions:


Upgrade from callmanager 4.x to callmanager 6.0.1 with CAR


Workaround:


Run the following queries fro CLI:


Run sql Select max(Error_Record_Id) from car:tbl_error_id_map


returned


Get the result of above query as and run the following:


Run sql update car:tbl_system_preferences set param_value= where param_name='MAX_ERROR_RECORD_ID'


for example, if "max(Error_Record_Id) from car:tbl_error_id_map" return 100, then please update 'MAX_ERROR_RECORD_ID' as 101.


Further Problem Description:


When CDR load failed, in CAR scheduler traces,


ERROR [DailyCdrLoad] beans.EBErrorIdMap -save(): SQL Error while saving data java.sql.SQLException: Unique constraint informix.pktbl_error_id_map_01) violated.


is found.

1st Found-In

6.0


Fixed-In

6.0(1.2120.1)

7.0(0.39000.6)

5.1(3.1111.1)




CSCsk99713 Bug Details


Loader does not start until next schedule if it is detected running

Symptom:

CAR loader does not start until its next schedule time. If 'Continuous Loading 24/7' is

enabled and such timing/racing condition happens, loader will skip at most up

to 24 hours of a window for loading CDRs/CMRs. Hence new records will have a

delay to be loaded into CAR database for reporting.


Note: Besides "DailyCdrLoad", this condition can happen to: "DatabaseAlert" or

"DeleteReports" or "DatabaseMaintenance" or "TaskMonitor", although the chances

are less than "DailyCdrLoad" loader.


Conditions:

This is an interim case and should not happen very often. And tt's likely to happen

if we have 'Continuous Loading 24/7' enabled and running for days or weeks.


Workaround:

Simply restart 'CAR Scheduler' service, if one suspects a delay on CDR loading

caused by this issue.


Further Problem Description:

If waiting or delay is not an issue, the workaround can be simply do nothing,

and scheduler will reschedule things (repouplate schedules) again in midnight 00:00,

and loader will start off to load CDRs again every midnight continuously.

1st Found-In

6.1

5.0

5.1

6.0


Fixed-In

6.1(0.9901.430)

5.1(3.9901.22)

6.1(1.1000.11)


Hope this helps!

Rob

Actions

This Discussion