Error "ORA-28040: No matching authentication protocol" When Using SQLNET.ALLOWED_LOGON_VERSION (Doc
![To Bottom To Bottom](https://support.oracle.com/epmos/ui/images/quicklink_smlarrowdown_enabled.gif)
![](https://support.oracle.com/epmos/adf/images/t.gif)
JDBC - Version 10.1.0 to 10.2.0.5
Information in this document applies to any platform.
SYMPTOMS
When using the property "SQLNET.ALLOWED_LOGON_VERSION=10" set in the file sqlnet.ora on the server side, a 10g JDBC thin driver connecting to this 10g oracle database, fails with following errors:
The Network Adapter could not establish the connection
....
ORA-28040: No matching authentication protocol
.
Configuring SQLNET.ORA on the server side.
CAUSEBUG 6051243 - ORA-28040: WHEN LISTENER USES SQLNET.ALLOWED_LOGON_VERSION
A 10.2 thin jdbc driver is identifying itself as 8.1.5 client and hence the connection is failing with error ORA-28040: No matching authentication protocol
To resolve the above issue you may implement any one of the following :-
- Change the entry in sqlnet.ora file on the server machine:
from:
SQLNET.ALLOWED_LOGON_VERSION=10
to:
SQLNET.ALLOWED_LOGON_VERSION=8
OR
- Use the OCI driver instead of the THIN driver. The OCI driver identifies itself correctly as a 10.2 client and thus the connection succeeds.
OR
- If you are using 10.2.0.4 version of the driver then, you may download Patch:6779501 from My Oracle Support.
OR
- If you are using 10.1.0.5.0 version of the driver then, you may download Patch:6505927 from My Oracle Support.
OR
- Use JDBC 11g THIN driver.
终极解决方案: Invalid character found in the request target. The valid characters are defined in RFC 3986 25-Aug-2018 11:27:27.
Oracle连接sqlplus时连接不上,报如下错误: ORA-12705: Cannot access NLS data files or invalid environment specified 解决方案: 如报错所示,很明显是字符集的问题。
prudentwoo 10g/11g OCP 11g OCM,ITPUB和CSDN专家及专家讲师;有着多年数据库从业经验,资深Oracle数据库专家,现就职于北京海量数据技术股份有限公司担任高级dba职务,为央视,银行,电信等各行业及企业提供过技术支持服务
相关文章
- 解决error while loading shared libraries: libXXX.so.X: cannot open shared object file: No such file
- Google Earth Engine(GEE)——ImageCollection (Error)遍历影像集合产生的错误
- Linux 有问必答:如何在Linux 中修复“fatal error: x264.h: No such file or directo
- python 'libinstall' failed [libinstall] Error 1 解决办法
- 编译openwrt时报错:FMCGenericError.h:34:27: fatal error: libxml/parser.h: No such file or directory
- nginx: [error] open() "/usr/local/nginx/logs/nginx.pid" failed (2: No such file or directory)
- 解决Error: undefined reference to `__android_log_print'
- configure:error no SDL library found
- jenkins出现故障,报错HTTP ERROR 403 No valid crumb was included in the request
- 安装wsl的必备操作——开启CPU虚拟化——WslRegisterDistribution failed with error_ 0x8007019e 0x800701b 0x80370102 请启用虚拟机平台
- Maven报错 解决方案。ERROR: No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id
- fatal error C1083: Cannot open include file: 'qttreepropertybrowser.moc': No such file or directory
- 编译boost python模块遇到的错误:../../libraries/boost_1_44_0/boost/python/detail/wrap_python.hpp:75:24: fatal error: patchlevel.h: No such file or directory
- docker镜像无法删除 Error:No such image:xxxxxx
- [symonfy] An error occurred when executing the "'cache:clear --no-warmup'"
- ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1
- Maven报错 解决方案。ERROR: No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id
- Solve error: Cannot open include file: 'X11/Xlocale.h': No such file or directory
- Linux下安装redis常见错误server.c:3318:16: error: ‘struct redisServer‘ has no member named ‘loading‘
- 解决 ERROR oslo_service.periodic_task AttributeError: ‘ComputeNode‘ object has no attribute ‘nodename‘
- nginx 启动出现 [error] open() "/usr/local/nginx/logs/nginx.pid" failed (2: No such file or directory)