合【MOS】数据库挂起由于 LANGUAGE_MISMATCH 的 High Version Count 导致 'cursor：mutex X' 争用 (Doc ID 2577528.1) (Doc ID 2542447.1)

2024年4月16日

0 247 1

Tags： Oracle Mos 版本数高(High Version Count)LANGUAGE_MISMATCH cursor：mutex X

👉 本文共约1184个字，系统预计阅读时间或需5分钟。

适用于:
症状
更改
原因
解决方案
Description
References

Database Hang With 'cursor: mutex X' Contention Due To High Version Count Under LANGUAGE_MISMATCH (Doc ID 2542447.1)

数据库挂起由于 LANGUAGE_MISMATCH 的 High Version Count 导致 'cursor：mutex X' 争用 (Doc ID 2577528.1)

数据库挂起由于 LANGUAGE_MISMATCH 的 High Version Count 导致 'cursor：mutex X' 争用 (Doc ID 2577528.1)

适用于:

Oracle Database - Enterprise Edition - 版本 12.1.0.2 和更高版本
Generic (Platform Independent)

症状

由于 'cursor：mutex X' 争用，数据库挂起
由于 LANGUAGE_MISMATCH 导致 SQL 语句的 High Version Count
刷新共享池可以暂时缓解互斥锁争用
Version Count 显示的值超过了_cursor_obsolete_threshold 的值

更改

从应用程序更改 NLS 设置。

由于 NLS 设置不同而导致 LANGUAGE_MISMATCH 的示例代码：

SQL> conn / as sysdba
Connected.

SQL> VAR B1 VARCHAR2(32);
SQL> EXEC :B1 := '';

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO
---------------------------------------------------------------------------

SQL> select SQL_ID,ADDRESS,CHILD_ADDRESS,CHILD_NUMBER,LANGUAGE_MISMATCH from v$sql_shared_cursor where sql_id='a9x5sbz88kmfh';

SQL_ID ADDRESS CHILD_ADDRESS CHILD_NUMBER L
------------- ---------------- ---------------- ------------ -
a9x5sbz88kmfh 0000000067968598 000000006EB0DD48 0 N

SQL> alter session set nls_language='DUTCH';

Sessie is gewijzigd.

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO
---------------------------------------------------------------------------

SQL> select SQL_ID,ADDRESS,CHILD_ADDRESS,CHILD_NUMBER,LANGUAGE_MISMATCH from v$sql_shared_cursor where sql_id='a9x5sbz88kmfh';

SQL_ID ADDRESS CHILD_ADDRESS CHILD_NUMBER L
------------- ---------------- ---------------- ------------ -
a9x5sbz88kmfh 0000000067968598 000000006EB0DD48 0 N
a9x5sbz88kmfh 0000000067968598 000000006B8CAC30 1 Y

SQL> alter session set nls_language='FRENCH';

Session modifiee.

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO
---------------------------------------------------------------------------

SQL> alter session set nls_territory='BELGIUM';

Session modifiee.

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO
---------------------------------------------------------------------------

SQL> select SQL_ID,ADDRESS,CHILD_ADDRESS,CHILD_NUMBER,LANGUAGE_MISMATCH from v$sql_shared_cursor where sql_id='a9x5sbz88kmfh';

SQL_ID ADDRESS CHILD_ADDRESS CHILD_NUMBER L
------------- ---------------- ---------------- ------------ -
a9x5sbz88kmfh 0000000067968598 000000006EB0DD48 0 N
a9x5sbz88kmfh 0000000067968598 000000006B8CAC30 1 Y
a9x5sbz88kmfh 0000000067968598 000000006B8CAAB0 2 Y
a9x5sbz88kmfh 0000000067968598 000000006F29A308 3 Y

SQL> conn / as sysdba

Connected.

SQL> VAR B1 VARCHAR2(32);

SQL> EXEC :B1 := '';

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO

---------------------------------------------------------------------------

SQL> select SQL_ID,ADDRESS,CHILD_ADDRESS,CHILD_NUMBER,LANGUAGE_MISMATCH from v$sql_shared_cursor where sql_id='a9x5sbz88kmfh';

SQL_ID ADDRESS CHILD_ADDRESS CHILD_NUMBER L

------------- ---------------- ---------------- ------------ -

a9x5sbz88kmfh 0000000067968598 000000006EB0DD48 0 N

SQL> alter session set nls_language='DUTCH';

Sessie is gewijzigd.

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO

---------------------------------------------------------------------------

SQL> select SQL_ID,ADDRESS,CHILD_ADDRESS,CHILD_NUMBER,LANGUAGE_MISMATCH from v$sql_shared_cursor where sql_id='a9x5sbz88kmfh';

SQL_ID ADDRESS CHILD_ADDRESS CHILD_NUMBER L

------------- ---------------- ---------------- ------------ -

a9x5sbz88kmfh 0000000067968598 000000006EB0DD48 0 N

a9x5sbz88kmfh 0000000067968598 000000006B8CAC30 1 Y

SQL> alter session set nls_language='FRENCH';

Session modifiee.

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO

---------------------------------------------------------------------------

SQL> alter session set nls_territory='BELGIUM';

Session modifiee.

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO

---------------------------------------------------------------------------

SQL> select SQL_ID,ADDRESS,CHILD_ADDRESS,CHILD_NUMBER,LANGUAGE_MISMATCH from v$sql_shared_cursor where sql_id='a9x5sbz88kmfh';

SQL_ID ADDRESS CHILD_ADDRESS CHILD_NUMBER L

------------- ---------------- ---------------- ------------ -

a9x5sbz88kmfh 0000000067968598 000000006EB0DD48 0 N

a9x5sbz88kmfh 0000000067968598 000000006B8CAC30 1 Y

a9x5sbz88kmfh 0000000067968598 000000006B8CAAB0 2 Y

a9x5sbz88kmfh 0000000067968598 000000006F29A308 3 Y

使用 CURSOR_SHARING = FORCE 时未发现语言不匹配，如下所示：


SQL> conn / as sysdba

SQL> alter session set cursor_sharing=force;

Session altered.

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO
---------------------------------------------------------------------------

SQL> alter session set nls_language='FRENCH';

Session modifiee.

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO
---------------------------------------------------------------------------

SQL> alter session set nls_territory='BELGIUM';

Session altered.

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO
---------------------------------------------------------------------------

SQL> select sql_id, open_versions, sql_text from v$sql where sql_text like 'SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1%';

SQL_ID OPEN_VERSIONS SQL_TEXT
------------- ------------- --------------------------------------------------------------------------------
32mcj6mff82su 1 SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,:"SYS_B_0"),:"SYS_B_1"),TO_CHAR(SYSTIME
STAMP, :"SYS_B_2")) AT TIME ZONE :"SYS_B_3" FROM SYS.DUAL

SQL> select SQL_ID,ADDRESS,CHILD_ADDRESS,CHILD_NUMBER,LANGUAGE_MISMATCH from v$sql_shared_cursor where sql_id='32mcj6mff82su';

SQL_ID ADDRESS CHILD_ADDRESS CHILD_NUMBER L
------------- ---------------- ---------------- ------------ -
32mcj6mff82su 00000000620175A8 0000000063758060 0 N

SQL> conn / as sysdba

SQL> alter session set cursor_sharing=force;

Session altered.

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO

---------------------------------------------------------------------------

SQL> alter session set nls_language='FRENCH';

Session modifiee.

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO

---------------------------------------------------------------------------

SQL> alter session set nls_territory='BELGIUM';

Session altered.

SQL> SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO_CHAR(SYSTIMESTAMP, 'TZR')) AT TIME ZONE 'GMT' FROM SYS.DUAL;

FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1,'YYYYMMDDHH24MISS'),'YYYYMMDDHH24MISS'),TO

---------------------------------------------------------------------------

SQL> select sql_id, open_versions, sql_text from v$sql where sql_text like 'SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1%';

SQL_ID OPEN_VERSIONS SQL_TEXT

------------- ------------- --------------------------------------------------------------------------------

32mcj6mff82su 1 SELECT FROM_TZ(TO_TIMESTAMP(TO_CHAR(:B1 ,:"SYS_B_0"),:"SYS_B_1"),TO_CHAR(SYSTIME

STAMP, :"SYS_B_2")) AT TIME ZONE :"SYS_B_3" FROM SYS.DUAL

SQL> select SQL_ID,ADDRESS,CHILD_ADDRESS,CHILD_NUMBER,LANGUAGE_MISMATCH from v$sql_shared_cursor where sql_id='32mcj6mff82su';

SQL_ID ADDRESS CHILD_ADDRESS CHILD_NUMBER L

------------- ---------------- ---------------- ------------ -

32mcj6mff82su 00000000620175A8 0000000063758060 0 N

本人提供Oracle(OCP、OCM)、MySQL(OCP)、PostgreSQL(PGCA、PGCE、PGCM)等数据库的培训和考证业务，私聊QQ646634621或微信dbaup66，谢谢！

原因

V$SQL_SHARED_CURSOR 显示LANGUAGE_MISMATCH 背后的原因是 NLS 设置不同。

SQL> select DBMS_LOB.SUBSTR(REASON,4000,1) from v$sql_shared_cursor where sql_id='a9x5sbz88kmfh';
...
<ChildNode><ChildNumber>3</ChildNumber><ID>45</ID><reason>NLS Settings(2)</reason><size>2x568</size><NLS_TERRITORY>'THE NETHERLANDS'->'BELGIUM'</NLS_TERRITORY><NLS_ISO_CURRENCY>'THE NETHERLANDS'->'BELGIUM'</NLS_ISO_CURRENCY></ChildNode>
<ChildNode><ChildNumber>4</ChildNumber><ID>45</ID><reason>NLS Settings(2)</reason><size>2x568</size><NLS_TERRITORY>'BELGIUM'->'THE NETHERLANDS'</NLS_TERRITORY><NLS_ISO_CURRENCY>'BELGIUM'->'THE NETHERLANDS'</NLS_ISO_CURRENCY></ChildNode>
...
<ChildNode><ChildNumber>2</ChildNumber><ID>45</ID><reason>NLS Settings(2)</reason><size>2x568</size><NLS_LANGUAGE>'FRENCH'->'DUTCH'</NLS_LANGUAGE><NLS_DATE_LANGUAGE>'FRENCH'->'DUTCH'</NLS_DATE_LANGUAGE><NLS_SORT>'FRENCH'->'DUTCH'</NLS_SORT></ChildNode>
<ChildNode><ChildNumber>7</ChildNumber><ID>45</ID><reason>NLS Settings(2)</reason><size>2x568</size><NLS_LANGUAGE>'FRENCH'->'DUTCH'</NLS_LANGUAGE><NLS_DATE_LANGUAGE>'FRENCH'->'DUTCH'</NLS_DATE_LANGUAGE><NLS_SORT>'FRENCH'->'DUTCH'</NLS_SORT></ChildNode>
...
<ChildNode><ChildNumber>96</ChildNumber><ID>45</ID><reason>NLS Settings(2)</reason><size>2x568</size><NLS_TIMESTAMP_FORMAT>'DD-MM-RRRR HH24:MI.SSXFF'->'DD-MM-RRRR HH24:MI:SSXFF'</NLS_TIMESTAMP_FORMAT><NLS_TIMESTAMP_TZ_FORMAT>'DD-MM-RRRR HH24.MI.SSXFF TZR'->'DD-MM-RRRR HH24:MI:SSXFF TZR'</NLS_TIMESTAMP_TZ_FORMAT></ChildNode>
<ChildNode><ChildNumber>84</ChildNumber><ID>45</ID><reason>NLS Settings(2)</reason><size>2x568</size><NLS_TIMESTAMP_FORMAT>'DD-MM-RRRR HH24:MI:SSXFF'->'DD-MM-RRRR HH24:MI.SSXFF'</NLS_TIMESTAMP_FORMAT><NLS_TIMESTAMP_TZ_FORMAT>'DD-MM-RRRR HH24:MI:SSXFF TZR'->'DD-MM-RRRR HH24.MI.SSXFF TZR'</NLS_TIMESTAMP_TZ_FORMAT></ChildNode>
...

SQL> select DBMS_LOB.SUBSTR(REASON,4000,1) from v$sql_shared_cursor where sql_id='a9x5sbz88kmfh';

...

<ChildNode><ChildNumber>3</ChildNumber><ID>45</ID><reason>NLS Settings(2)</reason><size>2x568</size><NLS_TERRITORY>'THE NETHERLANDS'->'BELGIUM'</NLS_TERRITORY><NLS_ISO_CURRENCY>'THE NETHERLANDS'->'BELGIUM'</NLS_ISO_CURRENCY></ChildNode>

<ChildNode><ChildNumber>4</ChildNumber><ID>45</ID><reason>NLS Settings(2)</reason><size>2x568</size><NLS_TERRITORY>'BELGIUM'->'THE NETHERLANDS'</NLS_TERRITORY><NLS_ISO_CURRENCY>'BELGIUM'->'THE NETHERLANDS'</NLS_ISO_CURRENCY></ChildNode>

...

<ChildNode><ChildNumber>2</ChildNumber><ID>45</ID><reason>NLS Settings(2)</reason><size>2x568</size><NLS_LANGUAGE>'FRENCH'->'DUTCH'</NLS_LANGUAGE><NLS_DATE_LANGUAGE>'FRENCH'->'DUTCH'</NLS_DATE_LANGUAGE><NLS_SORT>'FRENCH'->'DUTCH'</NLS_SORT></ChildNode>

<ChildNode><ChildNumber>7</ChildNumber><ID>45</ID><reason>NLS Settings(2)</reason><size>2x568</size><NLS_LANGUAGE>'FRENCH'->'DUTCH'</NLS_LANGUAGE><NLS_DATE_LANGUAGE>'FRENCH'->'DUTCH'</NLS_DATE_LANGUAGE><NLS_SORT>'FRENCH'->'DUTCH'</NLS_SORT></ChildNode>

...

<ChildNode><ChildNumber>96</ChildNumber><ID>45</ID><reason>NLS Settings(2)</reason><size>2x568</size><NLS_TIMESTAMP_FORMAT>'DD-MM-RRRR HH24:MI.SSXFF'->'DD-MM-RRRR HH24:MI:SSXFF'</NLS_TIMESTAMP_FORMAT><NLS_TIMESTAMP_TZ_FORMAT>'DD-MM-RRRR HH24.MI.SSXFF TZR'->'DD-MM-RRRR HH24:MI:SSXFF TZR'</NLS_TIMESTAMP_TZ_FORMAT></ChildNode>

<ChildNode><ChildNumber>84</ChildNumber><ID>45</ID><reason>NLS Settings(2)</reason><size>2x568</size><NLS_TIMESTAMP_FORMAT>'DD-MM-RRRR HH24:MI:SSXFF'->'DD-MM-RRRR HH24:MI.SSXFF'</NLS_TIMESTAMP_FORMAT><NLS_TIMESTAMP_TZ_FORMAT>'DD-MM-RRRR HH24:MI:SSXFF TZR'->'DD-MM-RRRR HH24.MI.SSXFF TZR'</NLS_TIMESTAMP_TZ_FORMAT></ChildNode>

...

这是由于每次执行 SQL 时，因为 NLS 设置的不同则 version count 随 LANGUAGE_MISMATCH 的增加而增加。因为NLS 设置的不同在执行期间而创建新子游标。有各种不同的 NLS 参数，如 NLS_TERRITORY，NLS_LANGUAGE，NLS_DATE_LANGUAGE，NLS_SORT，NLS_TIMESTAMP_FORMAT，NLS_TIMESTAMP_TZ_FORMAT，NLS_ISO_CURRENCY 等，在不同组合中导致了NLS参数的变化。

每当有不同的 NLS 设置在执行中以不同的组合进行更改时，它会使用 LANGUAGE_MISMATCH 创建新的子游标。此NLS设置更改来自应用程序端。这是预期的行为。

解决方案

如果 version count 超过阈值，则手动清除父cursor，以减轻对 'cursor：mutex X' 或 'cursor：mutex S' 的争用

 SQL> select address,hash_value,version_count from v$sqlarea where sql_id='a9x5sbz88kmfh';

ADDRESS HASH_VALUE VERSION_COUNT
---------------- ---------- -------------
000000006BFFAC00 3498659280 2

SQL> exec dbms_shared_pool.purge('<address,hash_value>','C');
Ex:
SQL> exec dbms_shared_pool.purge('000000006BFFAC00,3498659280','C');

PL/SQL procedure successfully completed.

SQL> select address,hash_value,version_count from v$sqlarea where sql_id='a9x5sbz88kmfh';

ADDRESS HASH_VALUE VERSION_COUNT

---------------- ---------- -------------

000000006BFFAC00 3498659280 2

SQL> exec dbms_shared_pool.purge('<address,hash_value>','C');

Ex:

SQL> exec dbms_shared_pool.purge('000000006BFFAC00,3498659280','C');

PL/SQL procedure successfully completed.

将 _cursor_obsolete_threshold 设置为 100 ，以便当父 cursor 具有超过这个设置时，父 cursor 将被废弃。但是，由于不会立即从共享池中删除过时的 cursor（需要共享池刷新），因此会出现Version Count 显示的值超过了_cursor_obsolete_threshold 的值的情况，这是正常的。

注意：设置参数 _cursor_obsolete_threshold 需要重新启动实例。

Bug 25054064 - Cursor Has High Version Count In PDB Whose Character Set Is Different From CDB$ROOT (Doc ID 25054064.8)

Description

A cursor may show very high version count due to "LANGUAGE MISMATCH" in a CDB environment when the character set of a PDB differs from that of the ROOT CDB. Rediscovery Notes If high cursor version count is seen and the reason for non-sharing is LANGUAGE_MISMATCH, it could be this bug if the following additional conditions are also satisfied. BOTH these conditions are required: - The database version is 12.2.0.1 or higher - The character set of the PDB where this problem is seen is different from that of CDB$ROOT. (eg. CDB$ROOT character set is AL32UTF8, and PDB is JA16SJIS) To check the character set of the PDB, run following query: alter session set container=<pdb_name>; select * from v$nls_parameters where parameter like 'NLS_CHARACTERSET'; Workaround NONE
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
A cursor may show very high version count due to "LANGUAGE MISMATCH"
in a CDB environment when the character set of a PDB differs from that of
the ROOT CDB.

Rediscovery Notes
If high cursor version count is seen and the reason for non-sharing is
LANGUAGE_MISMATCH, it could be this bug if the following additional conditions
are also satisfied. BOTH these conditions are required:

- The database version is 12.2.0.1 or higher
- The character set of the PDB where this problem is seen is different from that of CDB$ROOT.
(eg. CDB$ROOT character set is AL32UTF8, and PDB is JA16SJIS)

To check the character set of the PDB, run following query:

alter session set container=<pdb_name>;
select * from v$nls_parameters where parameter like 'NLS_CHARACTERSET';

Workaround
NONE

Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support.

References

Bug:25054064 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article

打赏赞(1)

标签： Oracle Mos 版本数高(High Version Count)LANGUAGE_MISMATCH cursor：mutex X

小麦苗

学习或考证，均可联系麦老师，请加微信db_bao或QQ646634621

发表回复取消回复

要发表评论，您必须先登录。

合【MOS】数据库挂起由于 LANGUAGE_MISMATCH 的 High Version Count 导致 'cursor：mutex X' 争用 (Doc ID 2577528.1) (Doc ID 2542447.1)

数据库挂起由于 LANGUAGE_MISMATCH 的 High Version Count 导致 'cursor：mutex X' 争用 (Doc ID 2577528.1)

适用于:

症状

更改

原因

解决方案

Bug 25054064 - Cursor Has High Version Count In PDB Whose Character Set Is Different From CDB$ROOT (Doc ID 25054064.8)

Description

References

相关文章

您可能还喜欢...

发表回复取消回复

网站公告

网站寄语

本站其它工具

搜索本网站

标签云☁

网站日历

网站归档

网站分类

2024 年 11 月
一	二	三	四	五	六	日
				1	2	3
4	5	6	7	8	9	10
11	12	13	14	15	16	17
18	19	20	21	22	23	24
25	26	27	28	29	30

合 【MOS】数据库挂起 由于 LANGUAGE_MISMATCH 的 High Version Count 导致 'cursor：mutex X' 争用 (Doc ID 2577528.1) (Doc ID 2542447.1)

数据库挂起 由于 LANGUAGE_MISMATCH 的 High Version Count 导致 'cursor：mutex X' 争用 (Doc ID 2577528.1)

适用于:

症状

更改

原因

解决方案

Bug 25054064 - Cursor Has High Version Count In PDB Whose Character Set Is Different From CDB$ROOT (Doc ID 25054064.8)

Description

References

相关文章

您可能还喜欢...

Oracle优化中的物化视图

Oracle数据泵expdp导出报ORA-01555和ORA-22924

在Oracle数据库中，什么是索引组织表（IOT）

发表回复 取消回复

网站公告

网站寄语

本站其它工具

搜索本网站

标签云☁

网站日历

网站归档

网站分类

合【MOS】数据库挂起由于 LANGUAGE_MISMATCH 的 High Version Count 导致 'cursor：mutex X' 争用 (Doc ID 2577528.1) (Doc ID 2542447.1)

数据库挂起由于 LANGUAGE_MISMATCH 的 High Version Count 导致 'cursor：mutex X' 争用 (Doc ID 2577528.1)

发表回复取消回复