[20230327]19c sqlnet.ora disable_oob引數 ora-12637.txt
--//前幾天同事反映如果使用19c的客戶端連接19c資料庫會出現,出現ora_12637錯誤(在連接配置界面上).其它版本沒有問題.
--//我仔細問一下服務器版本19.12,客戶端版本19.3.
--//補充:同事測驗修改有效!!
$ oerr ora 12637
12637, 00000, "Packet receive failed"
// *Cause: A process was unable to receive a packet from another process.
// Possible causes are:
// 1. The other process was terminated.
// 2. The machine on which the other process is running went down.
// 3. Some other communications error occurred.
// *Action: If the cause is not obvious, contact Oracle Customer Support.
--//檢索發現如下鏈接:http://blog.chinaunix.net/uid-20687159-id-5858993.html=>ORA-12637 與 OOB 的關系
--//建議在sqlnet.ora檔案中設定DISABLE_OOB=ON.
--//https://support.oracle.com/knowledge/Oracle%20Database%20Products/2662778_1.html
My Oracle Support Banner
Oracle 19c Client returns ORA-12637 when connecting to a 19c Database. Does not reproduce when using an older client
version. (Doc ID 2662778.1)
Symptoms
Sqlplus using a Version 19c client yield ORA-12637 when trying to connect to a 19c database.
...
Changes
New Feature added to 19c. Client will trigger the server to test for OOB availability at connect time. If it fails the
error is reported.
--//翻譯:新功能添加到19c,客戶端將觸發服務器在連接時測驗OOB的可用性,如果失敗,將報告錯誤,
--//注解:我的理解即使報ora-12637錯誤,還是可以使用的,當然我沒有測驗,
--//http://blog.chinaunix.net/uid-20687159-id-5858993.html
資料例外或中斷是 Oracle NET 中的一個功能,它允許在事務完成之前將其中斷,它將客戶端和服務器回傳到可以繼續的狀態,諸如
Ctrl-c 之類的中斷可以作為正常資料流(帶內)的一部分發送,也可以作為單獨的異步訊息(帶外)發送,帶外中斷要快得多并且會中斷數
據流,
如果底層協議支持發送緊急資料,則默認啟用帶外中斷 (OOB) ,
如果引數 DISABLE_OOB設定為 OFF,則它使 Oracle Net 能夠使用底層協議提供的緊急資料發送和接收"中斷"訊息,
如果打開,則禁用使用底層協議提供的緊急資料發送和接收"中斷"訊息的能力,
--//注:英文的邏輯負負得正,不小心很容易亂,DISABLE_OOB=OFF,支持OOB,DISABLE_OOB=ON,不支持OOB,
--//OOB 表示 out-of-band breaks
帶外中斷是發生在底層網路級別的通信中斷,有時,這些中斷資料包會導致客戶端和服務器行程不同步,通過設定 DISABLE_OOB=ON,您
可以強制客戶端和服務器使用帶內中斷,
Oracle TWO_TASK 層具有中斷/重置邏輯以確保客戶端和服務器同步,如果作業系統支持 OOB(帶外中斷),中斷/重置邏輯將有效作業,否
則可能會出現 TWO_TASK 錯誤,然后是 ORA-3113,
因此,設定引數 DISABLE_OOB=ON 以避免上述情況下的這些 TWO_TASK/ORA-3113 錯誤是有道理的,
DISABLE_OOB 在 sqlnet.ora 檔案中設定,有關此引數的更多資訊,請參閱注釋 67983.1,
--//實際上講的通熟一點,就是設定DISABLE_OOB=ON,客戶端忽略URG終端.
--//我找來兩臺機器測驗看看,os=linux.
1.環境:
[email protected]:1521/orcldg> @ pr
==============================
PORT_STRING : x86_64/Linux 2.4.xx
VERSION : 19.0.0.0.0
BANNER : Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
BANNER_FULL : Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
BANNER_LEGACY : Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
CON_ID : 0
PL/SQL procedure successfully completed.
--//version 19.3. 這是一臺dg資料庫.
--//我的測驗在這個版本下使用19c的相同版本客戶端沒有任何問題.也就是我的測驗沒有遇到前面的問題.
2.修改服務端sqlnet.ora:
--//加入disable_oob = ON
[email protected]:1521/orcldg> @ spid
SID SERIAL# PROCESS SERVER SPID PID P_SERIAL# C50
---------- ---------- ------------------------ --------- ------ ------- ---------- --------------------------------------------------
222 31147 33907 DEDICATED 120029 101 9489 alter system kill session '222,31147' immediate;
[email protected]:1521/orcldg> select count(*) from dba_source,all_objects;
select count(*) from dba_source,all_objects
*
ERROR at line 1:
ORA-01013: user requested cancel of current operation
--//按ctrl+C出現如上提示,沒有任何影響,可以繼續執行任何陳述句的執行.
[email protected]:1521/orcldg> select sysdate from dual ;
SYSDATE
-------------------
2023-03-27 09:22:41
[email protected]:1521/orcldg> select count(*) from dba_source,all_objects;
--//在192.168.100.237上執行:
$ kill -URG 120029
--//你可以發現sql陳述句沒有出現中斷,而是繼續執行.也就是忽略URG的中斷信號,
3.修改服務端sqlnet.ora,注解disable_oob = ON:
--//預設disable_oob = off.
--//session 1:
[email protected]:1521/orcldg> @ spid
SID SERIAL# PROCESS SERVER SPID PID P_SERIAL# C50
---------- ---------- ------------------------ --------- ------ ------- ---------- --------------------------------------------------
364 52618 34014 DEDICATED 125668 45 4622 alter system kill session '364,52618' immediate;
[email protected]:1521/orcldg> select count(*) from dba_source,all_objects;
select count(*) from dba_source,all_objects
*
ERROR at line 1:
ORA-01013: user requested cancel of current operation
--//按ctrl+C出現如上提示,沒有任何影響,可以繼續執行任何陳述句的執行.
[email protected]:1521/orcldg> select sysdate from dual ;
SYSDATE
-------------------
2023-03-27 09:28:53
[email protected]:1521/orcldg> select count(*) from dba_source,all_objects;
--//在192.168.100.237上執行,注23=URG,可以通過kill -l確定.
$ kill -URG 125668
--//或者
$ kill -23 125668
--//session 1:
[email protected]:1521/orcldg> select count(*) from dba_source,all_objects;
select count(*) from dba_source,all_objects
*
ERROR at line 1:
ORA-01013: user requested cancel of current operation
--//中斷sql陳述句運行,說明可以接收URG中斷.
[email protected]:1521/orcldg> select sysdate from dual ;
SYSDATE
-------------------
2023-03-27 09:32:59
--//可以預設情況下(disable_oob = off)下,對應行程可以接收URG信號.
4.ALTER SYSTEM CANCEL SQL測驗,disable_oob = ON:
--//突然想起12c支持運行時取消正在運行的sql陳述句,補充測驗看看,
--//修改服務端sqlnet.ora:
--//加入disable_oob = ON
--//session 1:
[email protected]:1521/orcldg> @ spid
SID SERIAL# PROCESS SERVER SPID PID P_SERIAL# C50
---------- ---------- ------------------------ --------- ------ ------- ---------- --------------------------------------------------
54 16475 46350 DEDICATED 95789 121 1743 alter system kill session '54,16475' immediate;
[email protected]:1521/orcldg> select count(*) from dba_source,all_objects;
select count(*) from dba_source,all_objects
*
ERROR at line 1:
ORA-01013: user requested cancel of current operation
--//session 2:
--//ALTER SYSTEM CANCEL SQL 'SID, SERIAL;
--//ALTER SYSTEM CANCEL SQL 'SID, SERIAL, SQL_ID';
--//ALTER SYSTEM CANCEL SQL 'SID, SERIAL, @INST_ID, SQL_ID';
--//說明:ALTER SYSTEM CANCEL SQL支持3種格式,選擇第1種格式測驗看看,
[email protected]:1521/orcldg> alter system cancel sql '54,16475' ;
System altered.
--//OK.沒有問題.我估計使用的不是URG資訊.
6.客戶端上設定呢?
--//修改服務端sqlnet.ora:
--//注解disable_oob = ON,預設disable_oob = OFF,
--//修改客戶端sqlnet.ora:
--//加入disable_oob = ON,看看兩端是如何協調的,
[email protected]:1521/orcldg> @ spid
SID SERIAL# PROCESS SERVER SPID PID P_SERIAL# C50
---------- ---------- ------------------------ --------- ------ ------- ---------- --------------------------------------------------
377 56959 46419 DEDICATED 97826 105 9552 alter system kill session '377,56959' immediate;
[email protected]:1521/orcldg> select count(*) from dba_source,all_objects;
--//在192.168.100.237上執行
$ kill -URG 97826
--//可以看出僅僅其中一放設定disable_oob = ON.當然這樣的情況僅僅影響一個連接.
--//修改客戶端sqlnet.ora:
--//注解disable_oob = ON,看看兩端是如何協調的,
[email protected]:1521/orcldg> @ spid
SID SERIAL# PROCESS SERVER SPID PID P_SERIAL# C50
---------- ---------- ------------------------ --------- ------ ------- ---------- --------------------------------------------------
377 18810 4251 DEDICATED 98463 105 9553 alter system kill session '377,18810' immediate;
[email protected]:1521/orcldg> select count(*) from dba_source,all_objects;
select count(*) from dba_source,all_objects
*
ERROR at line 1:
ORA-01013: user requested cancel of current operation
--//在192.168.100.237上執行
$ kill -URG 98463
--//這樣相當于兩邊都是disable_oob = OFF.
7.補充一點:
--//如果你使用windows的客戶端,視乎windows的OS忽略了URG信號,無論如何設定不起作用,而且在windows下按ctrl+c直接退出sqlplus程
--//序.
--//我感覺出現這樣的情況,估計oracle的某些版本做了一些嘗試,才會出現這樣的情況.
轉載請註明出處,本文鏈接:https://www.uj5u.com/shujuku/548861.html
標籤:Oracle
上一篇:為什么建議主鍵整型自增?