Good questions. We see the similar problmes here. It's ironic that I keep
hearing how the 3.1 drivers were tested up the wazoo, but it only took a few
minutes of using them on our configuration (with Oracle 8.1.7) for our
server to come to a screeching halt.
The other workaround to the errors showing up with cftransaction is to use
usernames and passwords in the cfadministrator instead of in the cfqueries.
That fixed it for those apps that couldn't move all transactional logic to
stored procs.
----- Original Message -----
From: "Dave Carabetta"
> 1) This problem never occurred until the Red Sky release, which is why
> all our production sites continue to use the 6.0 Updater 3+ drivers
> (connecting to an Oracle 8.1.7 database) even though we're using MX
> 6.1.
>
> 2) The TechNote refers to "Occasionally" whereas we only see it when
> we run a page that has a cftransaction on it. Have your engineers been
> able to replicate this in other areas? "Occasionally" is an awfully
> vague description of the frequency.
>
> 3) Another workaround would be to have the 6.0 Updater 3+ drivers
> available for download again. The clearing of the Maintain Connectons
> box is a ridiculous workaround, as it introduces a lot of additional
> overhead (CF has to re-instantiate a connection to the DB on every
> request). As I said before, we do not see this issue on the U3+
> drivers, only with the version released with the 6.1 updater.
>
> 4) Will there be a fix for this in the drivers that will be bundled in
> the 6.1 Service Pack slated for the fall?
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
