[ID 744125.1] Connections Fail with ORA-12640 or ORA-21561 due to Windows Desktop heap sizing issue.
最近 DB 常常出現 ORA-12640, 查了 alert log 沒有異常，查了一些文章說要改 sqlnet.ora
AUTHENTICATION_SERVICES= (NONE), 原本是設定 NTS , DB 也正常的運作好幾年了, 該不會是一個 Bug 吧? 查了 Metalink [ID 750457.1] 說明如下 :
Cause
This problem is due to unpublished Bug 5114330 AUTHENTICATION ADAPTER INITIALIZATION FAILED IS OS-USER IS NOT ADMIN
Solution
The unpublished Bug 5114330 is fixed in 10.1.0.6, 10.2.0.3. 9.2.0.8 database versions
所以就照著改好了, 改完沒多久變成出現 ORA-21561. 查詢 Metalink [ID 744125.1]如下, 在照改就 OK 了.
Connections Fail with ORA-12640 or ORA-21561 [ID 744125.1]
Modified 12-MAY-2010 Type PROBLEM Status MODERATED
In this Document
Symptoms
Cause
Solution
Platforms: 1-914CU;
AUTHENTICATION_SERVICES= (NONE), 原本是設定 NTS , DB 也正常的運作好幾年了, 該不會是一個 Bug 吧? 查了 Metalink [ID 750457.1] 說明如下 :
Cause
This problem is due to unpublished Bug 5114330 AUTHENTICATION ADAPTER INITIALIZATION FAILED IS OS-USER IS NOT ADMIN
Solution
The unpublished Bug 5114330 is fixed in 10.1.0.6, 10.2.0.3. 9.2.0.8 database versions
所以就照著改好了, 改完沒多久變成出現 ORA-21561. 查詢 Metalink [ID 744125.1]如下, 在照改就 OK 了.
Connections Fail with ORA-12640 or ORA-21561 [ID 744125.1]
Modified 12-MAY-2010 Type PROBLEM Status MODERATED
In this Document
Symptoms
Cause
Solution
Platforms: 1-914CU;
|
This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review. |
Applies to:
Oracle Net Services - Version: 10.2.0.1 and later [Release: 10.2 and later ]
Generic Windows
Microsoft Windows
Symptoms
Connections to database fail, reporting the error code ORA-12640 Authentication adapter initialization failed. SQLNET.AUTHENTICATION_SERVICES is set to NTS in the SQLNET.ORA file. Changing SQLNET.AUTHENTICATION_SERVICES=NONE and connections the fail with the error code ORA-21561 OID generation failed.
Seen for connections using third party applications and oracle tools such as recovery manager (RMAN). Connections have also been reported to be restricted to 64.
A typical Oracle Net level 16 client trace of RMAN failure shows following:
Cause
Windows Desktop heap sizing issue.
Solution
Desktop heap size is required to be increased in the registry for the database server. It can be found in the following location.
\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems\
At this location the following set of values can be seen 1024,3072,512.The third value (512) is the size of the desktop heap for each desktop that is associated with a "noninteractive" window station.
Increase of the third value to 1024, so the values are now listed as 1024, 3072, 1024 resolved the problem.
If this value is not present, the size of the desktop heap for noninteractive window stations will be same as the size specified for interactive window stations (the second SharedSection value).
Changing registry values is critical and and backup of the registry should be taken prior to amending these values.Oracle also recommends any such changes should be checked with Windows System administrator before attempting such a change.
全站熱搜
留言列表
