Platform = NT4SP6a
DOA version = 3.4.6
Tool chain = Delphi 4 Update 3
The application is threaded, with transaction spawning a thread which instantiates a data module containing a session and several query objects. Most of the queries are set up design time, but I keep one around for more dynamic use. That's the one troubling me.
We did a new build the other day and a few hours after it started running I got "ORA-01036: illegal variable name/number." Here's the thing: There are 8 possible transaction types that go through that query object. None of them are especially rare, so it's odd that after running for hours it suddenly errored. Odder is that I've gone over the routines that set the query up multiple times. I've had other people look and come to the same conclusion. I'm not declaring any variables that aren't referenced in the SQL.
Any other thoughts? I can't use the OracleMonitor tool because we don't know of a reliable way to reproduce what happened in a test environment and OM slows transaction down too much to leave it running in production.
G
DOA version = 3.4.6
Tool chain = Delphi 4 Update 3
The application is threaded, with transaction spawning a thread which instantiates a data module containing a session and several query objects. Most of the queries are set up design time, but I keep one around for more dynamic use. That's the one troubling me.
We did a new build the other day and a few hours after it started running I got "ORA-01036: illegal variable name/number." Here's the thing: There are 8 possible transaction types that go through that query object. None of them are especially rare, so it's odd that after running for hours it suddenly errored. Odder is that I've gone over the routines that set the query up multiple times. I've had other people look and come to the same conclusion. I'm not declaring any variables that aren't referenced in the SQL.
Any other thoughts? I can't use the OracleMonitor tool because we don't know of a reliable way to reproduce what happened in a test environment and OM slows transaction down too much to leave it running in production.
G
