本文介绍了Coldfusion 9.0.1 Standard 64bit 和 Oracle 11g 64bit ODBC 连接导致“架构不匹配"的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个新构建的 64 位 Windows Server 2008 R2 机器,我已经在上面安装了 64 位 Coldfusion 9 Standard.我已将其升级并修补到最新版本的 CF.我还在盒子上安装了 64 位 Oracle 11g (11.1.0.7.0) 客户端.我在Windows下使用64位ODBC数据源管理器创建了一个System DSN,可以成功测试数据源的连接.

I have a freshly built 64-bit Windows Server 2008 R2 box that I have installed 64-bit Coldfusion 9 Standard on. I've upgraded and hotfixed it up to the most current version of CF. I also had 64-bit Oracle 11g (11.1.0.7.0) Client installed on the box. I've created a System DSN using the 64-bit ODBC Data Source Administrator in Windows and can successfully test the connection of the data source.

所有这些安装都很顺利,但是,当我在 Coldfusion Administrator 中添加数据源时,我收到错误:

All of these installations went smoothly, however, when I went to add a datasource in the Coldfusion Administrator I receive the error:

数据源的连接验证失败:myDatabaseName

java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket] 内部错误:指定的 DSN 包含驱动程序和应用程序之间的架构不匹配根本原因是: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket] 内部错误:指定的 DSN 包含驱动程序和应用程序之间的架构不匹配

java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and ApplicationThe root cause was that: java.sql.SQLException: [Macromedia][SequeLink JDBC Driver][ODBC Socket]internal error: The specified DSN contains an architecture mismatch between the Driver and Application

我很难准确地理解这种架构不匹配的来源,因为这个盒子完全是 64 位的.我在查看所有正在运行的进程时看到,一些相关的 CF 进程正在 32 位(与 Verity 相关的进程、SOLR 和 CFDotNetSVC)中运行.我不确定这些是否会导致此问题,但我无法解释这种不匹配是否来自其他方面.

I am having a hard time understanding exactly where this architecture mismatch is coming from since the box is entirely 64-bit. I see while looking at all the processes that are running, some related CF processes are running in 32-bit (Verity related processes, SOLR and CFDotNetSVC). I am not sure if those could cause this issue but I am at a loss to explain were this mismatch would come from otherwise.

有人有什么想法吗?

推荐答案

我相信您需要 降级到32位驱动,或者使用原生JDBC驱动连接Oracle成功.我的建议是走 JDBC 路线,并通过使用数据源屏幕上的其他"选择直接通过本机 Oracle JDBC 驱动程序连接.这样您将获得更好的性能,并通过 ColdFusion 更好地控制您的连接.

I believe you need to either step down to the 32-bit drivers, or use native JDBC drivers to connect to Oracle successfully. My suggestion would be to go the JDBC route, and connect directly through a native Oracle JDBC driver by using the "other" selection on the Datasource screen. You'll get better performance that way, and have more control over your connection via ColdFusion.

连接到 Oracle ColdFusion Livedocs 中的信息.

Connecting to Oracle information in ColdFusion Livedocs.

这篇关于Coldfusion 9.0.1 Standard 64bit 和 Oracle 11g 64bit ODBC 连接导致“架构不匹配"的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-27 17:19