Book a Demo

Author Topic: Arithmetic Overflow Error adding Tagged Value  (Read 4705 times)

Rakesh

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Arithmetic Overflow Error adding Tagged Value
« on: November 07, 2012, 09:11:39 am »
I have a large EA Project in MS SQL Server, with 700+ Requirements and have been using Tagged Values to add additional attributes to manage these.  However have not got to a stage when adding a Tagged Value get the following error:

"Microsoft  OLE DB Provider for SQL Server [-2147217833]
Arithmetic Overflow error converting IDENTITY to data type int"

Enterprise Architect 9.1.910 build (910)  Corporate Edition
Database version: 7.0
Version Date: Jan-31-2004
MS SQL: 2008 R2 Standard, build 10.50.1617

If a run the following SQL can see that the PropertyID & ObjectId have large numbers, even though there are only 10,000 records in the table:


SELECT  
a = Max(t_objectproperties.PropertyID)
, b = Min(t_objectproperties.PropertyID)
, c = Max(t_objectproperties.Object_ID)
, d = Min(t_objectproperties.Object_ID)
, e = Count(*)
FROM t_objectproperties

a = 2147483647      
b = -2146703681      
c = 2143811339      
d = -2141479829      
e = 10499

Is there a way to fix this ?

Thanks in advance


qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Arithmetic Overflow Error adding Tagged Value
« Reply #1 on: November 07, 2012, 08:36:20 pm »
I'd try to export the whole model as XMI and import it into a fresh repository. That will start over the object IDs from the beginning. Not sure whether it will solve the problem, but worth a try.

Note that you have to transport reference data additionally via Project/Model Im-/Export/Export Reference Data

However, you should send an official bug report (link at bottom of this page).

q.
« Last Edit: November 07, 2012, 08:38:05 pm by qwerty »

Rakesh

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Arithmetic Overflow Error adding Tagged Value
« Reply #2 on: November 08, 2012, 07:16:12 am »
Thanks have attempted this on a local EAP repository and the ID's were renumbered.  Will now do as a SQL Server Repository.

Only downside is that the auditing history is lost.

Have also logged this as a bug.