Norbert S.
Member
Hi,
we have problems in merely all applications using either the old DOA (v3.4.6.1 for Delphi 6), or in newer Delphi 2005 programs (DOA v4.0.7.1).
At some point of execution the programs throws a windows exception at adress 0000000.
I've isolated the failure to a reproducable error in one of the programs, where a user table is dropped by an external procedure, then created and filled with new data, and then queried in a report linked to a TDataSet.
The first try (drop,create,fill,select) is working as expected, but if you do the same again, the final select fails.
I've read in other threads in this forum, that this is a bug.
We are using Oracle Server 11.2.0.3, and different Oracle Clients (9.2-11.2), and this was never a problem in the old 9.2 database.
Can you confirm, that this is an oracle bug? If so, is it the server, or the oracle client?
Is there no other chance to get the old behaviour, than modifying the TDataSet property and setting optimize:=false?
Do you know perhaps a parameter for setting in sqlnet.ora or tnsnames.ora at client side to get rid of the exceptions?
I'm seaching for an attempt to solve this problem, without modifying all our Delphi Programs. (There are many, and about a hundreds of datasets to change)
If you've got any helpful solution, I would be very glad.
regards,
Norbert
we have problems in merely all applications using either the old DOA (v3.4.6.1 for Delphi 6), or in newer Delphi 2005 programs (DOA v4.0.7.1).
At some point of execution the programs throws a windows exception at adress 0000000.
I've isolated the failure to a reproducable error in one of the programs, where a user table is dropped by an external procedure, then created and filled with new data, and then queried in a report linked to a TDataSet.
The first try (drop,create,fill,select) is working as expected, but if you do the same again, the final select fails.
I've read in other threads in this forum, that this is a bug.
We are using Oracle Server 11.2.0.3, and different Oracle Clients (9.2-11.2), and this was never a problem in the old 9.2 database.
Can you confirm, that this is an oracle bug? If so, is it the server, or the oracle client?
Is there no other chance to get the old behaviour, than modifying the TDataSet property and setting optimize:=false?
Do you know perhaps a parameter for setting in sqlnet.ora or tnsnames.ora at client side to get rid of the exceptions?
I'm seaching for an attempt to solve this problem, without modifying all our Delphi Programs. (There are many, and about a hundreds of datasets to change)
If you've got any helpful solution, I would be very glad.
regards,
Norbert