Msg 3628 - Floating Point Exception

Question

Msg 3628 - Floating Point Exception

Jeffsmith_NH

Old Hand

Points: 348
More actions
March 13, 2003 at 2:56 pm

#79740

One of our databases has a problem when we run a simple script that returns an exception Msg 3628 - A floating point exception occurred in the user process. Current transaction is canceled. The table does not have any floating data types. I also get this when I view the data thru enterprise manager of other tables not used in the same SQL. The problem randomly occurs on other databases on the same server. If I delete the original db with the error, then the remaining db's work fine. We are using SQL Server 2000 sp3. It fails on SP2 as well.
Help !
March 17, 2003 at 8:00 am

This was removed by the editor as SPAM

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

Jeffsmith_NH Old Hand Points: 348 More actions · Answer 1

Additional Info:

Tried dbcc checkdb, reorg indexes, backup/restore, etc. DTS'd all data to another sql server db - same problem. DTS'd to a Sybase db and no problem. DTS'd back to A different SQL Server and get problem again. Problem seems to affect other databases as well - perhaps corrupting the master db ?

Jeffsmith_NH Old Hand Points: 348 More actions · Answer 2

Additional Info:

We loaded data into an empty database one table at a time. We narrowed the problem down to one specific table.

guarddata SSCertifiable Points: 6583 More actions · Answer 3

This may not be your problem - but when we experienced something similar we found (after days of testing) that there was actually a bad sector on the disk.

Just a thought

Guarddata-

Jeffsmith_NH Old Hand Points: 348 More actions · Answer 4

We narrowed down the problem to this:

When we created a primary key clustered index on one specific table (regardless of columns) we received the error. Our work around was to make the primary key index non-clustered and the problem went away.

We will be reporting this to Microsoft.

rinkusethi SSC Enthusiast Points: 100 More actions · Answer 5

Hi,

I am facing very similar problems. My queries,tables also donot have any floating point or any other related datatypes.

Were you able to pinpoint the problem? I cannot remove the clustered index on the tables as they are critical to the performance, but if nothing else comes up, then I guess I will have to.

Any more information on this problem would be highly appreciated.

Thanks in advance.

5409045121009-7368 SSCoach Points: 15740 More actions · Answer 6

5409045121009-7368

SSCoach

Points: 15740

July 2, 2003 at 5:22 pm

#463988

See http://dbforums.com/t757720.html

rinkusethi SSC Enthusiast Points: 100 More actions · Answer 7

Thanks very much for the information. But it is not helping. Any further information would be of much help. I am facing problems on production and therefore need some help urgently.

PS - I even removed the clustered index on all tables just to see what happens and I am still getting the same error.

thebeast Mr or Mrs. 500 Points: 549 More actions · Answer 8

Hi all,

perhaps I found the reason. I experienced the same problem: somethimes querying the table I had a "floating point exception" and a "Number out of range" message. Looking at the table from entrprise manager I could see that some rows had a "-1.#IND" value instead of a float number. Creating another table with the same fields but with decimal(34,9) instead of float type I noticed that my procedure counldn't insert those rows. The reason was because I tried to insert the result of a zero-by-zero division in that column: well, if the column was a float type the value inserted was "-1.#IND" (that is, not deterministic). Fixing the procedure resulted in fixing all my problems.

Bye