Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
862
Views
0
Helpful
7
Replies

activities of calls are not recorded in HDS

Georges Hajj Moussa
Level 1
Level 1

‎12-20-2011 02:37 AM - edited ‎03-14-2019 09:04 AM

Hi,

We have icm 8.0(3) installed.

For some reason, the activities of calls are not recorded in the HDS. It was working before.

Did anyone have faced a similar issue?

Regards,

Georges

Labels:
0 Helpful
7 Replies 7

geoff
Level 10
Level 10

‎12-20-2011 05:29 AM

Use ICMDBA and check the "Space Used Summary" - look at this on the Logger and on the HDS and confirm that the tables are out of date. Check that the replication process on the HDS is connecting and requesting the updates - turn up the trace and watch what's happening there.

Regards,

Geoff

0 Helpful

Georges Hajj Moussa
Level 1
Level 1
In response to geoff

‎12-20-2011 06:02 AM

Hi Geoff,

when i tried to open the ICMDBA on the HDS server, i get the attached warrning.

is it a normal behavior?

And I realized, from the webview page, that some old call types ( that I have deleted from 2 weeks ago) are still there.

is it mean anything for you?

thanks for your support

Georges

0 Helpful

geoff
Level 10
Level 10
In response to Georges Hajj Moussa

‎12-20-2011 06:40 AM 

when i tried to open the ICMDBA on the HDS server, i get the attached warrning.
is it a normal behavior?

No it's not normal behaviour, but it's not a big deal - I have it on one of my servers too!

It's something to do with the inability to see the other SQL servers in the ICM Domain, but you can always add them manually. If you press OK, it probably opens ICMDBA OK on the HDS. You have to enter the SQL Server hostname to manually to reach (say) the logger.

Regards,

Geoff

0 Helpful

geoff
Level 10
Level 10
In response to geoff

‎12-20-2011 06:42 AM

Bump up the trace in Replication through the registry and just watch it for a bit. You should see messages every second or so as it requests table updates from the Logger. Let's just make sure you are seeing those happen.

Regards,

Geoff

0 Helpful

Georges Hajj Moussa
Level 1
Level 1
In response to geoff

‎12-21-2011 12:00 AM

Hi Geoff,

It is like the hds is just synchronized with loggerA that is not synchronized with LoggerB’s one.

I am attaching the “Space Used Summary” of each database and a screenshot for the window of “icmdba” of the HDS.

Should I add the LoggerA and LoggerB servers to the “icmdba” of hds?

Thanks in advance

Georges

hds

t_Agent_Event_Detail30.031095Aug 16 2011Aug 16 2011 2:15PM0
t_Agent_Logout10.021095Aug 16 2011Aug 16 2011 2:15PM0
t_Agent_Skill_Group_Logout100.031095Aug 16 2011Aug 16 2011 2:15PM0
t_Network_Trunk_Group_Half_Hou229922.071095Jul 30 2011Dec 13 2011 4:00PM136
t_Physical_Controller_Half_Hou76870.571095Jul 30 2011Dec 13 2011 4:00PM136
t_Route_Call_Detail160.031095Oct 11 2011Dec 13 2011 4:30PM63
t_Route_Call_Variable160.031095Oct 11 2011Dec 13 2011 4:30PM63
t_Route_Half_Hour140873.291095Jul 30 2011Dec 13 2011 4:00PM136
t_Routing_Client_Five_Minute9225633.261095Jul 30 2011Dec 13 2011 4:25PM136
t_Termination_Call_Detail160.031095Oct 11 2011Dec 13 2011 4:30PM63
t_Termination_Call_Variable320.031095Oct 11 2011Dec 13 2011 4:30PM63
t_Trunk_Group_Half_Hour230042.171095Jul 30 2011Dec 13 2011 4:00PM136

loggerA

EventTmp220.0914Dec 13 2011Dec 13 2011 4:31PM0
t_Application_Event496705.9514Dec 13 2011Dec 13 2011 4:30PM0
t_Event535006.4814Dec 13 2011Dec 13 2011 4:31PM0
t_Logger_Meters70.0214Dec 13 2011Dec 13 2011 4:25PM0
t_Network_Trunk_Group_Half_Hou60.0214Dec 13 2011Dec 13 2011 4:00PM0
t_Physical_Controller_Half_Hou30.0214Dec 13 2011Dec 13 2011 4:00PM0
t_Route_Call_Detail100.0214Dec 13 2011Dec 13 2011 4:30PM0
t_Route_Call_Variable100.0214Dec 13 2011Dec 13 2011 4:30PM0
t_Route_Half_Hour30.0214Dec 13 2011Dec 13 2011 4:00PM0
t_Routing_Client_Five_Minute130.0914Dec 13 2011Dec 13 2011 4:25PM0
t_Termination_Call_Detail100.0214Dec 13 2011Dec 13 2011 4:30PM0
t_Termination_Call_Variable200.0214Dec 13 2011Dec 13 2011 4:30PM0
t_Trunk_Group_Half_Hour60.0214Dec 13 2011Dec 13 2011 4:00PM0

loggerB

Agent_Event_DetailTmp220.0214Dec 21 2011Dec 21 2011 10:30AM0
Agent_LogoutTmp130.0214Dec 21 2011Dec 21 2011 10:27AM0
Agent_Skill_Group_LogoutTmp2100.0214Dec 21 2011Dec 21 2011 10:27AM0
Application_EventTmp140.0214Dec 21 2011Dec 21 2011 10:31AM0
Application_EventTmp220.0214Dec 21 2011Dec 21 2011 10:31AM0
EventTmp140.0914Dec 21 2011Dec 21 2011 10:31AM0
EventTmp220.0914Dec 21 2011Dec 21 2011 10:31AM0
Logger_MetersTmp210.0214Dec 21 2011Dec 21 2011 10:25AM0
Network_Trunk_Group_Half_HTmp160.0214Dec 21 2011Dec 21 2011 10:00AM0
Physical_Controller_Half_HTmp120.0214Dec 21 2011Dec 21 2011 10:00AM0
Route_Call_DetailTmp220.0214Dec 21 2011Dec 21 2011 10:31AM0
Route_Call_VariableTmp120.0214Dec 21 2011Dec 21 2011 10:31AM0
Route_Half_HourTmp130.0214Dec 21 2011Dec 21 2011 10:00AM0
Routing_Client_Five_MinuteTmp130.0214Dec 21 2011Dec 21 2011 10:25AM0
Termination_Call_DetailTmp110.0214Dec 21 2011Dec 21 2011 10:31AM0
Termination_Call_VariableTmp120.0214Dec 21 2011Dec 21 2011 10:31AM0
Trunk_Group_Half_HourTmp160.0214Dec 21 2011Dec 21 2011 10:00AM0
t_Agent_Event_Detail1430.0414Dec 8 2011Dec 21 2011 10:27AM13
t_Agent_Logout210.0214Dec 8 2011Dec 21 2011 10:27AM13
t_Agent_Skill_Group_Logout1080.0314Dec 8 2011Dec 21 2011 10:27AM13
t_Application_Event35413042.3214Dec 7 2011Dec 21 2011 10:31AM14
t_Event1243280153.5814Dec 7 2011Dec 21 2011 10:31AM14
t_Logger_Meters41490.4514Dec 7 2011Dec 21 2011 10:25AM14
t_Network_Trunk_Group_Half_Hou41460.5114Dec 7 2011Dec 21 2011 10:00AM14
t_Physical_Controller_Half_Hou13840.1314Dec 7 2011Dec 21 2011 10:00AM14
t_Route_Call_Detail4420.1214Dec 7 2011Dec 21 2011 10:31AM14
t_Route_Call_Variable4400.0514Dec 7 2011Dec 21 2011 10:31AM14
t_Route_Half_Hour20730.4514Dec 7 2011Dec 21 2011 10:00AM14
t_Routing_Client_Five_Minute146437.0714Dec 7 2011Dec 21 2011 10:25AM14
t_Termination_Call_Detail5640.3714Dec 7 2011Dec 21 2011 10:31AM14
t_Termination_Call_Variable9660.1314Dec 7 2011Dec 21 2011 10:31AM14
t_Trunk_Group_Half_Hour41460.4514Dec 7 2011Dec 21 2011 10:00AM14

0 Helpful

geoff
Level 10
Level 10
In response to Georges Hajj Moussa

‎12-21-2011 06:40 AM

So why are the loggers not synchronized? That's a problem and I would concentrate on that. The HDS uploads from the logger its connected to. When you have two HDS, one connected to loggerA and one connected to loggerB, they are updated independently. Because the loggers are normally synchronized, the HDS end up with the same data - but the HDS don't talk to each other.

Looking at the RCD tables, loggerA was last updated on Dec 13 but loggerB has Dec 21. These should be identical (of course) so you need to check loggerA and figure out why it's not being updated.

ICMDBA does not do this - it's just a SQL tool.

Regards,

Geoff

0 Helpful

Georges Hajj Moussa
Level 1
Level 1
In response to geoff

‎12-21-2011 06:59 AM

thanks Geoff. i will check the setup of LoggerA. i will rerun the stup for this logger.

regards,

Geogres

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents