Counting Hold Times

Question

Hi:
I am trying to recreate something in Oracle I had done in SQL Server with a complex SQL statement (See end of post). I have two tables. First table ("CallDetail") holds one record per phone call. Two of the fields in this table that I want to update--they are "HoldTime" and "Times_On_Hold". So if a call was put on hold once for 30 seconds, and a second time for 15, HoldTime would be 45 seconds and "Times_On_Hold" would be 2.
The second table ("HoldEvents") contains hold events, with these fields:
Reporting_ID
CallEventName
CallEventTime
So the relationship is one to many here between the first table and the second on the Reporting_ID.
The 3 types of events in the "HoldEvents" table are "Call on Hold" "Hold Ended" and "Call Ended" . The trick is that there are anomolies:
1. Call On Hold and "Hold Ended" could appear at same time, both for previous hold, and for next hold. So records in this order may appear (there are no existing ordinals to take care of this):
Reporting_ID CallEventName CallEventTime
1 Call On Hold 9:45:43
1 Call On Hold 9:46:52
1 Hold Ended 9:46:52
1 Hold Ended 9:53:01
1 Call Ended 9:56:01
2. There may be no final Hold Ended event--a call might be put on hold and and just ended without a corresponding "Hold Ended": So might see these events for Reporting_ID 2:
Reporting_ID CallEventName CallEventTime
2 Call On Hold 9:46:43
2 Hold Ended 9:53:01
2 Call On Hold 9:55:43
1 Call Ended 10:01:01
When I try to run the code below in Toad, I get a missing right parentheses error, not sure why, they all seem to be there, but most likely it is just because of differences between T and PL/SQL. (The DATEDIFF function I have created in Oracle to mimic the way it was done before). Any ideas how to either modify the code below to get this to work, or a new approach altogether?
The code I used in TSQL:
UPDATE CallDetail SET Hold_Time = b.ElapsedSeconds, Times_On_Hold = b.TimesOnHold
FROM CallDetail a INNER JOIN
(SELECT Starting.Reporting_ID,
SUM(datediff('SS', Starting.HoldEventTime,
Ending.HoldEventTime)) as ElapsedSeconds,
count(*) as TimesOnHold
FROM (SELECT Reporting_ID,
HoldEventTime,
(select count(*) from HoldEvents as B
where B.CallEventName = 'Call On Hold'
and A.Reporting_ID = B.Reporting_ID
and A.HoldEventTime >= B.HoldEventTime) as Ordinal
FROM HoldEvents as A
WHERE CallEventName = 'Call On Hold') as Starting
JOIN (SELECT Reporting_ID,
HoldEventTime,
(select count(*) from HoldEvents as D
where D.CallEventName IN ('Hold Ended',
'Call Ended')
and C.Reporting_ID = D.Reporting_ID
and C.HoldEventTime >= D.HoldEventTime) as Ordinal
FROM HoldEvents as C
WHERE CallEventName IN ('Hold Ended', 'Call Ended')) as
Ending
ON Starting.Reporting_ID = Ending.Reporting_ID
AND Starting.Ordinal = Ending.Ordinal
GROUP BY Starting.Reporting_ID) b
ON a.Reporting_ID = b.Reporting_ID
Thanks!
Kayda

Answer 1

Your not the first and certinly not the last to have this issue. It seems that the hard dri've used on the Zen Micro and other players, such as my own, has this problem. The hard dri've is a Seagate ST dri've. And by the looks of it only the 5gb model is affected as I have yet to read of someone with a 4gb or a 6gb Micro with this problem.
If this problem is really that big, we should get a petition started to recall the players with these dri'ves, or offer FREE service to get the faulty dri've replaced. This would be similar to the headphone jack issue which affected soo many players that Creative is now offering free service to repair it.
This hard dri've problem is not just a few dozen or so, it is a BIG percentage of players given the number of posts over the course of almost a year with the Zen Micro and the Dell Pocket DJ which is built by Creative and uses the same 5GB Seagate ST dri've.
But I must say. This problem does NOT affect all 5GB Zen Micro's or Dell Pocket DJ's. Its only some. And it does not matter if your player has been under extreme care or been mishandled. Personally my player has been mishandled and suffers my daily commute to school which involves alot of shaking and other things which has been suggested time and time again not to do with a hard dri've player, such as running, working out, even mowing the lawn. And it has not skipped a beat ever, still works flawlessly just like the first day I got it. So I know first hand it doesn't affect all 5GB Seagate ST dri'ves.
I would love to hear a response from Creative regarding this issue. Or Seagate even.Message Edited by DM on -08-2005 0:5 AM