风哥教程

培训 . 交流 . 分享
Make progress together!

关于Oracle数据库ORA-00600 [2103]报错的bug汇总

[复制链接]
内容发布:风哥| 发布时间:2014-2-21 11:17:27
关于oracle数据库ORA-00600 [2103]报错的bug汇总

关于Oracle ORA-00600[2103]报错的描述:
这个错误是说CONTROL FILE ENQUEUE等待超时,超时时间是900秒,也就是错误信息后面的参数,900秒杀15分钟,也就是说,在数据库解决这个队列冲突之前,RAC hang住了15分钟,这是一个比较长的时间,对业务系统来说非常致命,一个内部参数可以控制这个超时时间,这个参数是:_controlfile_enqueue_timeout,其缺省值是900秒。

以下内容来自Oracle ID 429943.1:
Error Description:

An ORA-600 [2103] is signaled by a session when it times out trying to acquire the CF enqueue. Holding the CF enqueue is required before performing IO against the database controlfiles (this locking ensures readers and writers see a consistent version of the controlfile contents).

The most common reasons for high CF enqueue contention leading to timeout errors are frequent logfile switches and IO contention.

Summary Of Bugs On ORA-00600 [2103] Error

Bug 4671216 (Unpublished)
Abstract : ASM operations on a file are blocked while it is resized
Versions affected : 10.0
Fixed Releases : 10.1.0.6, 10.2.0.2.

Details : Creating/deleting/resizing to a large ASM file may block other
ASM operations for an extented period of time and may cause
instances to crash with ORA-600 [2103] or ORA-600 [2116] errors.

Backportable: Yes

Symptoms :


1. When creating/dropping/resizing a large file,

2. Mounting or opening a database on DB instances or

3. ASM v$_ table queries are blocked for an extended period of time.

4. DB instance crash with [2103] or [2116].

Workaround :

None

Patch Details:

One-off patch available for few platforms on top of  10.1.0.4,10.1.0.5, 10.2.0.1
Check Metalink for  Patch 4671216  availability.





Bug 5134663

Abstract : OERI[2103] with ASM

Versions affected : 10.2

Fixed Releases :  10.1.0.6, 10.2.0.3, 10.0.0.0

Details : ASM may get to a GCS locking deadlock and cause the DB client to
crash with ORA-600 [2103]


Backportable:
Yes

Symptoms :

The macro symptom is that ASM hangs and cannot satisfy requests from the DB
client. DB may assert [2103]. The ASM systemstate dumps show one instance
waiting to escalate a lock from S to X and another instance waiting to open or
convert a lock from NL to X.

Workaround

Kill the ASM instance that is escalting the lock from S to X.

Patch Details:

One-off patch available for few platforms on top of 10.2.0.1, 10.2.0.2
Check Metalink for  Patch 5134663  availability.







Bug 5011019

Abstract : OERI[2103] on bystander standby during target standby failover

Versions affected :10.2

Fixed Releases :
10.2.0.3, 11.0.0.0

Details : During a failover of a standby database to a primary, other standby databases
may not accept redo from the new primary right away. The other standby
databases may experience a delay in accepting redo from the new primary due
to the connections these other standby databases have to the old primary.
This fix alleviates the delay in cases where the connections to the old
primary is preventing new connections to the new primary.


Backportable: Yes

Symptoms:

Depending on the timing, you may see ORA-600 with argument 2103 in the
alert log. However, typically, the bystander standby database does not have
any connections to the old primary by the time the new primary is created.


Workaround:

None

Patch Details:

One-off patch available for few platforms on top of  10.2.0.1, 10.2.0.2
Check Metalink for Patch 5011019 availability.






Bug 3187730

Abstract : Various hangs possible if process expecting SIGALRM does not get it

Versions affected :9.2

Fixed Releases : 9.2.0.7, 10.1.0.5, 10.2.0.1

Details : Processes may hang due to waiting for a SIGALRM signal to arrive before
it continues. This can lead to various hang symptoms such as:
ORA-600[2103]


Backportable: Yes but only to 9.2

Systemwide hang with sessions waiting for "library cache load lock"
Parallel queries hanging

Symptoms

Processes hang leading symptoms like

1) ORA-600[2103]
2) SYSTEM HANG DUE TO WAIT FOR LIBRARY CACHE LOAD LOCK. (bug:3187730)
3) QC AND SLAVES ARE WAITING FOR IDLE EVENT AND PARALLEL QUERY HANG
(Bug: 3861580).

After you have successfully used the workaround you can be sure that you are
hitting this issue.


Workaround:

Find the process which is hanging and manually send if SIGALRM (Unix only)

Patch Details:

One-off patch available for few platforms on top of    9.2.0.4, 9.2.0.5, 9.2.0.6, 10.1.0.4
Check Metalink for Patch 3187730 availability.







Bug 2950375

Abstract : OERI[2103] in RAC if LMD0 is producing a dump

Versions affected :  
9.2

Fixed Releases : 9.2.0.4, 10.0.0.0.

Details : LMD0 may stall for long period of time (in ksdxdmpproc) when dumping
diagnostic information. This can lead to an ORA-600 [2103] error
causing instance crash.


Backportable: Yes but have some internal exceptions.

Symptoms:

If lmd0 was stall for long period of time in ksdxdmpproc, it may be the cause
of the problem.

Workaround:

set distributed_lock_timeout to 59.

Patch Details:

One-off patch available for few platforms on top of  9.2.0.3
Check metalink for patch availibility using following link Patch 2950375









Bug 3724485

Abstract : Enqueue waits may occur with no obvious holder in RAC

Versions affected : 9.2

Fixed Releases : 9.2.0.6, 10.1.0.4, A.2.0.1

Details : This problem is specific to RAC environments.
When a process requesting an enqueue gets an error and resignals, the enqueue
might not be cleaned up properly. This can result in enqueue requests for that
enqueue blocking but there being no apparent holder from systemstate dumps.
If the enqueue happens to be the CF enqueue then this can result in ORA-600 [2103]
and an instance crash.


Backportable: Yes

Sumptoms:

The global enqueue doesn't exist from all the systemstates and it might be
able to show the problem from the in-memory traces from the owning processes.

Workaround

No workaround.

Patch Details:

One-off patch available for few platforms on top of  9.2.0.4, 9.2.0.5, 10.1.0.3
Check Metalink for availibility of patch using link Patch 3724485







Bug 2872299 (Unpublished)

Abstract : OERI:2103 / instance crash can occur if foreground hits data/index internal error

Versions affected : 9.2

Fixed Releases : 9.2.0.4, 10.0.0.0

Details : Instance may crash with ORA-600 [2103] in a RAC environment if
a session hits an data/index/txn layer internal error.
If a foreground runs into a data/index/txn layer internal error it
first tries to dump the redo from all online threads in a RAC cluster
and then raise the internal error. Dumping redo from all logs will
cause the foreground to hold the controlfile enqueue CF [0] [0] while
the routine that is scanning the log for the specific redo records.

This can cause background processes like LGWR/SMON that are waiting to get
the CF enqueue in X mode to get blocked and time out after 15 minutes
crashing the instance with ORA 600[2103]


Backportable: Yes

Symptoms:

if foreground dumping redo for any internal error indirectly cause ORA600[2103]

Workaround:

None

Patch Details:

One-off patch available for few platforms on top of 9.2.0.2, 9.2.0.3
Check Metalink for  Patch 2872299 availability.







Bug 3342182

Abstract : Instance hang on startup possible in RAC

Versions affected : 9.2

Fixed Releases :
9.2.0.5, 10.1.0.3, 10.2.0.1

Details :
After startup in a RAC environment LGWR may hang waiting for a
GES operation and user logins may also hang. This is a rare
scenario.
For this problem LGWR waits on one of the following:
o "ges inquiry response"
o "wait for scn from all nodes"
o "enqueue"
o "DFS lock handle"
o "wait for master scn"


Backportable: Yes

Symptoms:


1. RAC + UDP
2. Oracle release 10.2
3. Send timeouts
4. trace suggests that an active connection was mistakenly cleaned up, eg:
"WARN: acconn .... getting closed. inactive: threshold: 0x0
WARN: potential problem in keep alive connection protocol"

Workaround:

Restart each instance within 24 days to prevent the problem.

Patch Details:

One-off patch available for few platforms on top of 9.2.0.3, 9.2.0.4, 8.1.7.4
Check Metalink for Patch 3342182 availability.






Bug 4047167 (Unpublished)

Abstract : RAC hang possible processing synchronized dump request

Versions affected : 10.2

Fixed Releases : 9.2.0.8, 10.2.0.1

Details :
There is no workaround for the hang scenario but it may be
possible to avoid the synchronized dump itself by addressing
whatever error led to the dump being invoked.


Backportable:
Yes

Symptoms:

A process may hang on a synchronized dump request in a RAC
environment due to an inter-dependency between IPC and the
wait facility. This only occurs when the dump request is
made from the IPC layer.
If a process hangs and contains the following in the call stack,
you are likely to experience this problem.
ksarcr
ksbwco
kjzddmp
ksxpsrvdt
ksxpwait

Workaround:

There is no workaround for the hang scenario but it may be
possible to avoid the synchronized dump itself by addressing
whatever error led to the dump being invoked.

Patch Details:

One-off patch available for few platforms on top of 9.2.0.7, 10.1.0.4
Check Metalink for Patch 4047167 availability.






Bug 3885499

Abstract : ASM hang possible

Versions affected : 10.1

Fixed Releases :10.1.0.6, 10.2.0.3, 11.0.0.0

Details : A database session may hang in the middle of an alias scan,
either through RMAN, dbms_file_transfer, ASM PL/SQL fixed package,
or XDB/FTP, causing an ASM instance hang.
if DB_BLOCK_CHECKING is enabled.


Backportable: Yes

Symptoms:

If a DB instance hanging in the middle of an alias scan, either through RMAN,
dbms_file_transfer, ASM PL/SQL fixed package, or XDB/FTP, and the ASM
instance hangs as a result, then we have the bug. This problem is seen in
LRG hangs in rare instances.



Workaround:

Manually kill the slave background of the DB-instance process that is hung.
This operation will release the ASM foreground's resources.

Patch Details:

One-off patch available for few platforms on top of  10.2.0.2
Check Metalink for  Patch 3430832  availability.






Bug 4164021

Abstract : OERI [2103] during BACKUP CONTROLFILE to TRACE

Versions affected : 9.2

Fixed Releases : 9.2.0.8, 10.1.0.5, 10.2.0.2, 11.0.0.0

Details : Under rare circumstances an "alter database backup controlfile to trace"
can cause a deadlock between the foreground, the log writer and the
CR server process, causing an ORA-600[2103] in log writer in RAC
environments.

Various internal errors in queries using old connect by.

Error stack has qerix and connect by rowsources.


Backportable: Yes

Workaround

Avoid backing up the controlfile to trace when the instance is mounted
shared.

Patch Details:

One-off patch available for few platforms on top of 9.2.0.6, 9.2.0.7,10.1.0.4
Check Metalink for availibility of patch using link Patch 4164021








Bug 3253153

Abstract : RFS may error starting managed recovery

Versions affected : 9.2

Fixed Releases : 9.2.0.5, 10.0.0.0

Details : When starting up managed recovery, the RFS process reports the following
in the alert.log:
Mon Nov 10 11:58:08 2003
RFS: Forced Shutdown due to RFS_ERROR state
Mon Nov 10 12:11:49 2003
RFS: controlfile enqueue unavailable
Possible invalid cross-instance archival configuration
Mon Nov 10 12:11:57 2003
RFS: controlfile enqueue unavailable
Possible invalid cross-instance archival configuration
Mon Nov 10 12:14:26 2003
Media Recovery Log /oracle/PRD/saparch/PRDarch1_270139.dbf
Mon Nov 10 12:16:57 2003
RFS: Error State mode '8'


Backportable: Yes

Symptoms:

Mon Nov 10 11:58:08 2003
RFS: Forced Shutdown due to RFS_ERROR state
Mon Nov 10 12:11:49 2003
RFS: controlfile enqueue unavailable
Possible invalid cross-instance archival configuration
Mon Nov 10 12:11:57 2003
RFS: controlfile enqueue unavailable
Possible invalid cross-instance archival configuration
Mon Nov 10 12:14:26 2003
Media Recovery Log /oracle/PRD/saparch/PRDarch1_270139.dbf
Mon Nov 10 12:16:57 2003
RFS: Error State mode '8'

Workaround

None

Patch Details:

One-off patch available for few platforms on top of  9.2.0.4
Check Metalink for Patch 3253153 availability.








Bug 4029799

Abstract : Generate alert messages for enqueue timeouts

Versions affected : 9.2

Fixed Releases :10.1.0.5, 10.2.0.1

Details : Generate alert messages for enqueue timeouts.
(eg: CF timeouts)


Backportable:
Yes

Symptoms:

Generate alert messages for enqueue timeouts.
(eg: CF timeouts)


Workaround:

No workarounds

Patch Details:

One-off patch available for few platforms on top of  10.1.0.4
Check Metalink for availability of patch using link Patch 4029799









Bug 3400979

Abstract : Dump of FILE_HDRS may hang or error (can result in OERI [2103])

Versions affected : 9.2

Fixed Releases : 9.2.0.6, 10.1.0.4, 10.2.0.1

Details : Using the diagnostic FILE_HDRS dump a process may hang or get
an IO error. In the case of a hang this process could be holding
the CF enqueue and so can lead to ORA-600 [2103] errors and
and instance crash.


Backportable: Yes

Workaround

Do not issues FILE_HDRS dumps.

Patch Details:

Currently one off patches are not avaiable for Bug 3400979.







Bug 3394085 (Unpublished)

Abstract : CRS may hang after node hard shutdown / node disconnect

Versions affected :  10.1
Fixed Releases : 10.1.0.3, 10.2.0.1

Details : Cluster ready services (CRS) may hang after node
hard shutdown / node disconnect.


Backportable: Yes

Symptoms:

Do a hard reset of one of the machines in the cluster. CRSDs will hang in
prom_rpc call.

Workaround:

Kill and restart CRSDs.

Patch Details:

One-off patch available for few platforms on top of 10.1.0.2
Check Metalink for Patch 3394085  availability.





Bug 5181800 (Unpublished)

Abstract : Async LNS holds CF enqueue while issuing network calls rfsopen/rfsclose

Versions affected : 10.2

Fixed Releases : 10.2.0.3, 11.0.0.0

Details : A primary may be affected due to network hangs between primary and
standby with async LNS in operation in that it may hold the CF
enqueue longer than desired.


Backportable: Yes

Symptoms:

Look for situations where primary is affected due to network hangs
between primary and standby with async lns in operation.

Workaround:

No workaround available

Patch Details:

One-off patch available for few platforms on top of  10.2.0.1
Check Metalink for availability of patch using link Patch 5181800






Bug 4074603

Abstract : RMAN backup of primary with a standby using FAL may omit archivelogs

Versions affected : 9.2

Fixed Releases : 9.2.0.7, 10.1.0.5

Details : This problem is introduced in 9.2.0.6 by the fix for bug 3533351 .
The fix for bug 3533351 can cause silent loss of archivelogs
in the backup sets when using RMAN to backup the primary if
the situation in bug 3533351 arises.
This occurs as that fix marks the archive log as DELETED on
the primary which then affects any subsequent RMAN backup as
RMAN will ignore DELETED archive logs.


Backportable: Yes

Symptoms:

Look for non-shared logs, and FAL being performed by one instance
(the one which doesn't have access to the file), which marks the
log's CF entry as DELETED.

Workaround:

Make sure archive logs are available from all nodes. This can be
achieved by either having the archive logs in shared locations, or
by having local copies of all logs.
Another workaround is to fix the gap manually.
A third workaround is to copy deleted logs to the FAL serving instance,
and register them.

Patch Details:

One-off patch available for few platforms on top of 9.2.0.6, 10.1.0.4
Check Metalink for availibility of patch using link Patch 4074603






Bug 4997470 (Unpublished)

Abstract : CSS startup terminates when another node comes up during reconfig

Versions affected :
10.2

Fixed Releases : 10.2.0.3, 11.1.0.0

Details : CSS startup incorrectly terminates when another node comes up during reconfig


Backportable: Yes

Symptoms:

Workaround:

No workaround available

Patch Details:

One-off patch available for few platforms on top of 10.2.0.2
Check Metalink for Patch 3430832 availability.



上一篇:关于Oracle出现WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK!的分析过程
下一篇:Linux AS6安装Oracle 11g使用runcluvfy.sh验证过程中出现Verification cannot proceed
专业提供Oracle/MySQL/NoSQL/Linux数据库培训与技术支持服务,QQ号:113257174
关注风哥教程微信公众号itpux_com  ,了解本站最新技术资料的分享.

欢迎加QQ群,提供超多高质量Oracle/Unix/Linux技术文档与视频教程的下载。

Oracle/MySQL/Linux群4-5:189070296  150201289  
Oracle/MySQL/Linux群6-8:244609803   522261684   522651731
备注:请勿重复加群,另请注明 from itpux
回复

使用道具 举报

1框架
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

热门文章教程

  • 风哥Oracle数据库巡检工具V1.0(附2.6网页
  • Oracle 12cR2 九大新功能全面曝光_详解云数
  • 实战PHP与MySQL权威指南PDF电子书下载
  • 大数据技术与应用入门培训教程(电子版下载
  • Oracle OCP认证考试IZ0-053题库共712题数据
  • MySQL5权威指南(第3版)PDF电子版下载
快速回复 返回顶部 返回列表