【故障解決】ORA-17630: Mismatch in the remote file protocol version client 2
【故障解決】ORA-17630: Mismatch in the remote file protocol version client 2 server 3
在 12.1.0.2 的 PDB 升級到 12.2.0.2 的時候,不能選用 DBLINK 遠端克隆的方式,因為源庫是 12.1.0.2 的版本,不能誇版本遠端克隆,否則報錯:
SYS@cdb1212> create pluggable database pdblhr3 from PDBPROD2@dbl_PDBLHR1 CREATE_FILE_DEST = '/u01/app/oracle/oradata';
create pluggable database pdblhr3 from PDBPROD2@dbl_PDBLHR1 CREATE_FILE_DEST = '/u01/app/oracle/oradata'
*
ERROR at line 1:
ORA-17630: Mismatch in the remote file protocol version client 2 server 3
參考: Creating a PDB Remote Clone from 12.1.0.2 to 12.2 Fails With ORA-17630 ( 文件 ID 2090019.1)
解決: Download and apply Patch 18633374 on the side that does not include the fix for Bug 18633374. The fix is included in 12.2 or later.
NOTE: Both sides must have the fix for Bug 18633374
|
Creating a PDB Remote Clone from 12.1.0.2 to 12.2 Fails With ORA-17630 (文件 ID 2090019.1) |
In this Document
|
Symptoms |
|
Changes |
|
Cause |
|
Solution |
|
References |
APPLIES TO:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Information in this document applies to any platform.
SYMPTOMS
Creating a PDB remote clone from 12.1.0.2 to 12.2 fails with:
SQL> create pluggable database MYDB from MYSEED@CDBMYSEED
file_name_convert=('/CDB12R1/','/CDB12R2/');
create pluggable database MYDB from MYSEED@CDBMYSEED
file_name_convert=('/CDB12R1/','/CDB12R2/')
*
ERROR at line 1:
ORA-17628: Oracle error 17630 returned by remote Oracle server
ORA-17630: Mismatch in the remote file protocol version client server
The error is shown in the alert.log file and in the generated trace file as follow:
alert.log
...
create pluggable database MYPDB from MYSEED@CDB12R1 file_name_convert=('/MYSEED/','/MYPDB/')
2015-12-11T17:48:30.353070+01:00
Errors in file /u01/app/oracle/diag/rdbms/cdb/CDB/trace/CDB_ora_4268_remote.trc:
ORA-17628: Oracle error 17630 returned by remote Oracle server
ORA-17630: Mismatch in the remote file protocol version client server
...
/u01/app/oracle/diag/rdbms/cdb/CDB/trace/CDB_ora_4268_remote.trc
...
*** 2015-12-11T17:48:30.352800+01:00 (CDB$ROOT(1))
ORA-17628
: Oracle error 17630 returned by remote Oracle server
ORA-17630
: Mismatch in the remote file protocol version client server
EXEC #0x7f34ee563838:c=76000,e=2344936,p=11,cr=279,cu=13,mis=0,r=0,dep=0,og=1,plh=0,tim=254798627784
ERROR #0x7f34ee563838:
err=17628
tim=254798627869
LOBTMPCREATE: type=TEMPORARY LOB,bytes=1,c=0,e=41,p=0,cr=0,cu=0,tim=254798628632
LOBWRITE: type=TEMPORARY LOB,bytes=93,c=0,e=111,p=0,cr=0,cu=7,tim=254798628845
...
CHANGES
CAUSE
Unpublished Bug 22289708 - ORA-17630 WHILE TRYING TO REMOTE CLONE A PDB, closed as duplicate of:
- COPYING ACROSS REMOTE SERVERS: ASMCMD-8016, ORA-17628, ORA-17630, ORA-06512,
The error is a result of looking for a particular protocol version instead of a set of protocol versions. In this case, the 12.2 client is sending both V1 & V2 as protocol versions and 12.1.0.2 (the remote side in this case) is expecting a single version not both.
SOLUTION
Download and apply on the side that does not include the fix for . The fix is included in 12.2 or later.
NOTE: Both sides must have the fix for
If no patch exists for your environment, please contact Oracle Support for a backport request.
Check for any conflicting Patches using
Document 1317012.1
- How To Use MOS Patch Planner To Check And Request The Conflict Patches?
REFERENCES
- COPYING ACROSS REMOTE SERVERS: ASMCMD-8016, ORA-17628, ORA-17630, ORA-06512
NOTE:18633374.8
- Bug 18633374 - Error copying across remote servers with ASMCMD CP command (ASMCMD-8016, ORA-17628, ORA-17630, ORA-6512)
About Me
........................................................................................................................ ● 本文作者:小麥苗,部分內容整理自網路,若有侵權請聯絡小麥苗刪除 ● 本文在itpub( http://blog.itpub.net/26736162 )、部落格園( http://www.cnblogs.com/lhrbest )和個人weixin公眾號( xiaomaimiaolhr )上有同步更新 ● 本文itpub地址: http://blog.itpub.net/26736162 ● 本文部落格園地址: http://www.cnblogs.com/lhrbest ● 本文pdf版、個人簡介及小麥苗雲盤地址: http://blog.itpub.net/26736162/viewspace-1624453/ ● 資料庫筆試面試題庫及解答: http://blog.itpub.net/26736162/viewspace-2134706/ ● DBA寶典今日頭條號地址: ........................................................................................................................ ● QQ群號: 230161599 (滿) 、618766405 ● weixin群:可加我weixin,我拉大家進群,非誠勿擾 ● 聯絡我請加QQ好友 ( 646634621 ) ,註明新增緣由 ● 於 2018-12-01 06:00 ~ 2018-12-31 24:00 在魔都完成 ● 最新修改時間:2018-12-01 06:00 ~ 2018-12-31 24:00 ● 文章內容來源於小麥苗的學習筆記,部分整理自網路,若有侵權或不當之處還請諒解 ● 版權所有,歡迎分享本文,轉載請保留出處 ........................................................................................................................ ● 小麥苗的微店 : ● 小麥苗出版的資料庫類叢書 : http://blog.itpub.net/26736162/viewspace-2142121/ ● 小麥苗OCP、OCM、高可用網路班 : http://blog.itpub.net/26736162/viewspace-2148098/ ● 小麥苗騰訊課堂主頁 : https://lhr.ke.qq.com/ ........................................................................................................................ 使用 weixin客戶端 掃描下面的二維碼來關注小麥苗的weixin公眾號( xiaomaimiaolhr )及QQ群(DBA寶典)、新增小麥苗weixin, 學習最實用的資料庫技術。
........................................................................................................................ |
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26736162/viewspace-2284342/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- [20150415]tmux:protocol version mismatchUXProtocol
- 錯誤:Dx unsupported class file version 52.0(解決)
- remote client copyREMclient
- Failed to initialize NVML: Driver/library version mismatchAI
- hive metastore異常 org.apache.thrift.protocol.TProtocolException: Missing version in readMessageBegin, old clientHiveASTApacheProtocolExceptionclient
- Docker啟動故障問題 no such file or directory解決方法Docker
- java.lang.IllegalArgumentException: Unsupported class file major version xx解決之道JavaException
- https Java SSL Exception protocol_versionHTTPJavaExceptionProtocol
- Internet Protocol version 4 (IPv4)Protocol
- adb server version (31) doesn’t match this client (36); killing… 的解決方法Serverclient
- 【故障解決】12c中的APEX,ORA-65346: The PDB version is lower and components
- 解決The given version [xx] is not supported, only version 1 to 10 is supported in this buildUI
- NFS故障解決NFS
- 解決 'PLAN_TABLE' is old version
- Client does not support authentication protocol requested by server; consider upgrading MySQL clientclientProtocolServerIDEMySql
- Script to generate AWR report from remote sql clientREMSQLclient
- cassandra0.5 remote client access configureREMclient
- navicat本地連線mysql出現1251--Client does not support authentication protocol requested by server的解決方法MySqlclientProtocolServer
- 詳解REMOTE_ADDR,HTTP_CLIENT_IP,HTTP_X_FORWARDED_FORREMHTTPclientForward
- 故障解決法(摘抄)
- 解決 Lumen 中 client charset is not supportedclient
- 原來是它(Oracle.ManagedDataAccess.Client)——再說ORA-12516故障解決Oracleclient
- remote_listener引發的故障分析REM
- Navicat 遠端連線docker容器中的mysql 報錯1251 - Client does not support authentication protocol 解決辦法DockerMySqlclientProtocol
- No input file specified 解決方法
- 解決Project facet Java version 1.8 is not supported.ProjectJava
- error in ./src/components/form/Editor.vue Module build failed: Error:Vue packages version mismatchErrorORMVueUIAIPackage
- 【故障處理】ORA-28040: No matching authentication protocolProtocol
- ORA-39358: Export dump file version 12.1.0 not compatible with target version 11Export
- 【故障解決】OGG-00446 錯誤解決
- 總結”解決Windows XP SP2帶來的網路故障”解決辦法薦Windows
- ConfigureGC.pl,version SUNWprivate_1.1 not defined in file libjvm.so with link time reference問題解決GCJVM
- REMOTE HOST IDENTIFICATION HAS CHANGED 問題解決REMIDE
- Cocoapods fatal: Remote branch #{s.version} not found in upstream originREM
- gitbook no such file or directory 怎麼解決Git
- flume file channel 異常解決
- MYSQL(解決方法):Client does not support authentication(轉)MySqlclient
- 故障分析 | MySQL : slave_compressed_protocol 導致 crashMySqlProtocol