Which versions of DOA support BCB3?

[PColbert]

I have an old program written with Borland C++ Builder 3, that currently accesses Oracle 8.0.4 as well as Oracle 9, Oracle 10XE, and Oracle 10 Std. Edition, thanks to you and DOA.

The current problem is the program locking up (sometimes) when trying to delete a record from a data set. Thus far, it occurs only with Oracle 10, which makes debugging difficult. Due to operating system constraints, the computer that runs Builder 3 can't run Oracle 10, and vice versa. So it is very difficult to recreate the situation under debugger control, and thereby tell precisely where the problem lies.

I will look further at the problem. In the meantime, perhaps the problem has been solved in a later release of DOA. What version of DOA would you recommend for use with Builder 3?

 

[Marco Kalter]

Which Direct Oracle Access version are you using now?

 

[PColbert]

It is using 4.0.7.1.

 

[Marco Kalter]

Can you set the global variable NoQueryOptimize in the Oracle unit to true and try again?

 

[PColbert]

Yes. Am now setting that in constructor of FormMain (1st form to be constructed). Is that too late?

During work with Oracle 8.0.4, I get "ORA-00600: internal error code, arguments [15868], [51880812], [6], [], [], []". If memory serves, this is the same 8.0.4 error I got before setting it to true.

This isn't necessarily a DOA problem (program has lots of 3rd-party add-ons), but I never got it before upgrading from 3.4.3.

 

[PColbert]

Correction to error message:
"ORA-00600: internal error code, arguments [15868], [51880588], [51880812], [6], [], [], []".

 

[PColbert]

No problem with Oracle 9.2.

 

[Marco Kalter]

Could it be this Oracle bug? I found the following on Oracle MetaLink:

From: Oracle, Helen Schoone 18-Jun-02 20:27
Subject: Re : ORA-00600: internal error code, arguments: [15868], [2438291500], [2438291564], [1], [], [], [], []

There was an issue which effected earlier versions (bug 386983/690332) where this error could be signaled to SQL which had the same bind variable referenced more than once in the SQL statement. The bug had to do with loss of the bind metadata. However it should have been fixed in the 8.0.5.1 patch set release. These are the only known bugs related to this error and there are no reports of this error occurring after 8.0.5.x.

A potential workaround is to increase the size of the shared pool and pin commonly used packages, thus reducing shared pool contention.

Regards,
Helen
Oracle Support Services

 

[PColbert]

Thank you! That may well be the problem with 8.0.4. I will take a closer look at it when I get the chance. It may be tricky; I have other Oracle products (of similar vintage) using the same database, and I have no idea how they'd react to such an update.