Bug 8869647 - ORA-600 [krslint.9] in PRIMARY database. Standby fails to fetch gap sequence [ID 8869647.8]

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

修改時間 03-JUN-2010 型別 PATCH 狀態 PUBLISHED
Bug 8869647 ORA-600 [krslint.9] in PRIMARY database. Standby fails to fetch gap sequence
This note gives a brief overview of bug 8869647.
The content was last updated on: 27-MAY-2010
Click here for details of each of the sections below.

Affects:
Product (Component) Oracle Server (Rdbms)
Range of versions believed to be affected Versions < 11.1.0.7
Versions confirmed as being affected •10.2.0.4

Platforms affected Generic (all / most platforms affected)

Fixed:
This issue is fixed in •11.1.0.7 (Server Patch Set)

Symptoms: Related To:
•Internal Error May Occur (ORA-600)
•ORA-600 [krslint.9]
•Physical Standby Database / Dataguard

Description
ORA-600 [krslint.9] in a Primary database when using LGWR ASYNC transport.
Standby fails to fetch gap sequence.

Under extremely rare circumstances, when using LGWR ASYNC, the LNS process
can terminate unexpectedly due to an internal error. This can cause the
standby database to stop applying redo until the next log switch.

Workaround

Manually resolve the gap by physically moving the archivelog from Primary to
Standby. Alternatively, use the ARCH transport, rather than LGWR ASYNC.

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. Always consult with Oracle Support for advice.

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

ORA-600 [krslint.9] in PRIMARY database

相關文章