ca.portal.admin

""Loss of significance"" Error

Discussion created by ca.portal.admin on Dec 23, 2008
Latest reply on Dec 23, 2008 by ca.portal.admin
One of our java programs sometimes gets a ""Loss of significance"" error
when attempting to store records to IDMS. Sometimes the record stores
fine and other times it gets the error. The developer says that she has
had it work and then not work. When I tried it it failed the first
couple of times (see error message below), then it started working for
no apparent reason and it worked fine the rest of the day. I can't
figure out if this is a connection issue with IDMS or something else.
The program opens and closes the database connection each time a record
is stored. When the record stores successfully the IDMS log shows the
transaction, when it fails IDMS shows nothing. ""Loss of significance""
appears to be related to certain arithmetic operations, but the
developer says that she does not do any of those in her program. Any
ideas on how to debug this would be appreciated. =20

From the web server log:


CREATE_ID VALUE : 018645
IDMS INSERT, SSN: 123456789
java.sql.SQLException: DB001001 T391 C-4M322: Loss of
significance
at
ca.idms.jdbc.IdmsJdbcObject.getSQLException(IdmsJdbcObject.java)
at
ca.idms.jdbc.IdmsStatement.getSQLException(IdmsStatement.java)
at
ca.idms.jdbc.IdmsJdbcObject.getSQLException(IdmsJdbcObject.java)
<<<<<<<<<<<<<<<<snip>>>>>>>>>>
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:
675)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:683)
at java.lang.Thread.run(Thread.java:810)
error DB001001 T391 C-4M322: Loss of significance IDMS INSERT SUCCESS
VALUE: 0
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
"Re: ""Loss of significance"" Error"
"The IDMS Log might be more revealing - depending on how you are
connecting there ought to be an IDMS JDBC Server Log on the midrange
and/or some information in the DC/LOG. If your JDBC connection is
through TCP/IP into IDMS then everything you want should be in the one
spot (in the IDMS/DC Log) - one of the advantages of taking advantage of
the new driver for JDBC Connections - hth - cheers - Gary


Gary Cherlet
Justice Technology Services
Department of Justice, SA Government
Telephone +61 (0)8 8226 5199
Facsimile +61 (0)8 8226 5311
Mobile +61 (0)41 333 1613
MailTo:cherlet.gary@saugov.sa.gov.au

This e-mail message and any attachments are qualified as follows:
Addressing: If you have received this e-mail in error, please advise by
reply e-mail to the sender. Please also destroy the original
transmission and its contents. Confidentiality: This e-mail may contain
confidential information which also may be legally privileged. Only the
intended recipient(s) may access, use, distribute or copy this e-mail.
Individual Views: Unless otherwise indicated, the views expressed are
those of the sender, not Justice Technology Services. Computer Viruses:
It is the recipient's responsibility to check the e-mail and any
attached files for viruses.

Outcomes