duplicate PRIMARY KEY

Tom Bilan ( tom@tdi.net )
Fri, 02 May 1997 20:00:23 -0400

I'm getting an error on radius about duplicate primary keys. This is
because the key isn't unique, there's entries from back in March that
are identical to the constraints.

How do I fix this. I REALLY don't want to delete historical calls.
I thought maybe it would be ok to add the date/time as a 5th element
that makes up the key but I'm wondering about the consequences.

I saw serveral posts about this a month ago and I re-read every one of
them but none really said you need to do etc. etc. to fix it.

I have USR TC chassis. I know the AcctSessionID is generated there but
is there a way in Emerald/RadiusNT to work around this problem?