piotr.wisniewski

Hello,

I wonder if someone else has seen problems like described below.

Ingres version:
valid 9568 1 II 2.6/0305 (su4.us5/00)


Problem description
-----------------------------
We have a vision application in which a db procedure is called for every
processed
instruction to check if this instruction breaks a saving scheme. During
tests a user
reports that this procedure returns 0, when it should return nonzero.
When that happens I run a test to see what the db procedure returns for
given set of parameters.
I also get 0 on every invocation.
Then I recreate (drop & create) the procedure from a script file, which has
not been changed since it was
last saved in the database. If I repeat the test after reacreating I get
proper nonzero value.
This situation happend at least 3 times since yesterday. It looks like the
db procedure is somehow
changed to wrong when it is stored in the db proc. cache.
Please tell me how I can find out what is the cause of this error.


Piotr Wi¶niewski

mike lay

Just a thought:

How many servers are you running? We have noted occasional problems
where the procedure is only updated in the cache of the server through
which it is piped.


--
Mike Lay - Clinical Trial Service Unit
"I can barely speak for myself, let alone the CTSU"
w: http://www.ctsu.ox.ac.uk/
e: michael dot lay at ctsu (with an ox, an ac, and an uk on the end).