We're getting this error in a Delphi 5 DOA 3.4.5 ISAPI app connect to an 8.1.6 database. It's sporadic, and we don't use explicit LOB locators anywhere--just TOracleDataset and TOracleQuery. The database has some LONGs but they only ever receive plain text. The latest instance of this error was preceded shortly before by an ORA-0600 12333. All this we gleaned from the ALERT log crash dumps.
If it matters, we manage our own pool of TOracleSessions, assigning users to them in a round robin fashion, so any given session could be supporting five or six users running a variable mix of queries and updates. The TOracleSessions are marked threadsafe, with DOA's pooling as spNone. If one loses its connection we gracefully euthanize its users and reset it.
The other thing (perhaps) of note is that we are now seeing a reappearance of the orageneric8.dll AV error, which we thought was fixed by our connection pooling strategy. It seemed to occur when too many TOracleSessions tried to log on or off at the same time, so we consolidated our session components into 11 shared ones. This error does not necessarily appear in connection with the LOB error, though.
Help! It's a mission critical customer app (aren't they all) and we have egg on our face. The especially yummy part is that when we get the error, the web server locks up with CPU going nuts, necessitating a reboot. Mmm-mmm good...
If it matters, we manage our own pool of TOracleSessions, assigning users to them in a round robin fashion, so any given session could be supporting five or six users running a variable mix of queries and updates. The TOracleSessions are marked threadsafe, with DOA's pooling as spNone. If one loses its connection we gracefully euthanize its users and reset it.
The other thing (perhaps) of note is that we are now seeing a reappearance of the orageneric8.dll AV error, which we thought was fixed by our connection pooling strategy. It seemed to occur when too many TOracleSessions tried to log on or off at the same time, so we consolidated our session components into 11 shared ones. This error does not necessarily appear in connection with the LOB error, though.
Help! It's a mission critical customer app (aren't they all) and we have egg on our face. The especially yummy part is that when we get the error, the web server locks up with CPU going nuts, necessitating a reboot. Mmm-mmm good...
