ORA-00600 internal error code, arguments [1265]和ORA-00603 ORACLE server session terminated by fatal

晚上收到数据报警：
Errors in file /app/oracle/admin/xxxxx/udump/xxxxx_ora_22467.trc:
ORA-00600: internal error code, arguments: [1265], [0xADE975850], [], [], [], [], [], []
Tue Jun 24 22:00:45 CST 2014
Errors in file /app/oracle/admin/xxxxx/udump/xxxxx_ora_22467.trc:
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [1265], [0xADE975850], [], [], [], [], [], []
查看trace发现查找的的其他用户的表。
解决方法是让oracle解决。或升级到11g。我的库是10205，是访问远程表的bug，出现在10点多点的时候。
这有又是个ora 600错误。是个bug。
下面的文档供参考：

ORA-00600: [1265] and ORA-00600 [18194] When Querying a Remote View (文档 ID 1377939.1)

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 Database - Enterprise Edition - Version 10.2.0.4 and later
Information in this document applies to any platform.
***Checked for relevance on 01-Jul-2013***
SYMPTOMS

Alert log shows following errors when querying a remote view:

ORA-00600: internal error code, arguments: [1265], [0x69C990EC0], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [18194], [0x6884B9680], [0x000000000], [], [], [], [],
 
The call stack trace for the ORA-00600 [1265] error shows:

kgeriv <- kgeasi <- ksuprc <- k2send <- k2serv <- opiodr <- ttcpip <- opitsk
CAUSE

The error ORA-600 [1265] relates to the distributed transactional area or remote SQL involving dblinks.

This is
Bug 8209133 - ORA-600 [1265] WHEN QUERYING A REMOTE VIEW
closed as duplicate of unpublished Base
Bug 5655419 - AQ: ORA-00600[K2SCHKSESS_1] AND [K2SCHKSESS_2] DURING AW2 TEST
which is fixed in Oracle RDBMS release 11.1.

SOLUTION

Upgrade to RDBMS release 11.1 or higher in which unpublished Bug 5655419 is fixed

- OR -

Apply Patch 5655419 if available for your platform and RDBMS release
REFERENCES

BUG:8209133 - ORA-600 [1265] WHEN QURYING A REMOTE VIEW
NOTE:1270798.1 - Diagnostic steps for ORA-600 [1265]
NOTE:5655419.8 - Bug 5655419 - Distributed transaction hits ORA-600:[1265] or ORA-600:[k2gget: downgrade] in 10.2
BUG:11804223 - ORA-600 [1265]/[18194] INTERMITTENTLY

 

Bug 5655419 - Distributed transaction hits ORA-600:[1265] or ORA-600:[k2gget: downgrade] in 10.2 (文档 ID 5655419.8)

Bug 5655419  Distributed transaction hits ORA-600:[1265] or ORA-600:[k2gget: downgrade] in 10.2

 This note gives a brief overview of bug 5655419.
 The content was last updated on: 14-AUG-2012
 Click here for details of each of the sections below.
Affects:

Product (Component)  Oracle Server (Rdbms)
Range of versions believed to be affected  Versions BELOW 11.1
Versions confirmed as being affected 
10.2.0.5
10.2.0.4
Platforms affected  Generic (all / most platforms affected)
Fixed:

This issue is fixed in 
11.1.0.6 (Base Release)
Symptoms:

Related To:

ORA-600 [1265]
ORA-600 [k2gget: downgrade]
Database Link / Distributed
Job Queues
Description

Distributed transaction may get ORA-600:[1265] or ORA-600:[k2gget: downgrade].
This problem can happen at the time maintenance window changes or job process
fails.
 
Rediscovery Notes:
If ORA-600:[1265] or ORA-600:[k2gget: downgrade] is signaled on 10.2,
it might be duplicate this problem.
And, if above internal errors are signaled at the time scheduler windows
changes, most likely duplicate of this problem.
In 10.2, default maintenance window is created as WEEKNIGHT_WINDOW
which begins 22:00 every weekday and ends 06:00, several customers
see this problem at 22:00.
 
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:5655419 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article

 

ORA-600 [1265] (文档 ID 138374.1)

Note: For additional ORA-600 related information please read Document:1092832.1

  This article represents a partially published OERI note.

  It has been published because the ORA-600 error has been reported
  in at least one documented bug and/or confirmed Support Related Article.

  Therefore, the SUGGESTIONS section of this article may help
  in terms of identifying the cause of the error.

  This specific ORA-600 error may be considered for full publication
  at a later date. If/when fully published, additional information
  will be available here on the nature of this error.

ERROR:

  Format: ORA-600 [1265] [a]

SUGGESTIONS:

  Ensure all EVENTS are set correctly if ORA-600 has no additional
  arguments and retry the operation.

  If the Known Issues section below does not help in terms of identifying
  a solution, please submit the trace files and alert.log to Oracle
  Support Services for further analysis.

  Known Issues:

Related Articles
  Note:1270798.1    Diagnostic steps for ORA-600 [1265]

Known Bugs
You can restrict the list below to issues likely to affect one of the following versions by clicking the relevant button:

NB Bug Fixed Description
5655419 11.1.0.6 Distributed transaction hits ORA-600:[1265] or ORA-600:[k2gget: downgrade] in 10.2
'*' indicates that an alert exists for that issue.
'+' indicates a particularly notable issue / bug.
'I' indicates an install issue / bug included for completeness.
'P' indicates a port specific bug.
Fixed versions use "BPnn" to indicate Exadata bundle nn.
"OERI:xxxx" may be used as shorthand for ORA-600 [xxxx].

 

Diagnostic steps for ORA-600 [1265] (文档 ID 1270798.1)

APPLIES TO:

Oracle Database - Enterprise Edition - Version 8.1.7.4 and later
Information in this document applies to any platform.
***Checked for relevance on 27-Jun-2013***
GOAL

The purpose of this article is to provide Customers and Support engineers with general information about ORA-600 [1265],
to list known resolved and unresolved issues and what diagnostic steps to follow when hitting this error witout being able to match situation with any resolved known issue.

SOLUTION

General information

ORA-600 [1265] can be seen in two different formats.

ORA-600 [1265] without any additional argument is mainly reported in releases prior RDBMS 10g, and is often due to inappropriate settings of event 10146.

ORA-600 [1265] [] with one additional argument, mainly focused on in this article, relates to the distributed transactional area or remote SQL involving dblinks, and is most commonly seen in RAC environments.

There are many defects raised for ORA-600 [1265] [] though few have reached a resolution due to its complicated nature requiring diagnostic events to be set and a diagnostic patch to get installed. Many problems reported occur only once, where the necessary information cannot get collected.

Impact

The impact is normally session failure.

Known Issue in 10.2

If you are facing ORA-600 [1265] in 10.2.0.4, it is likely due to unpublished base Bug 5655419:

Bug Fixed Description Support Article
Bug 5655419 11.1 Hitting ORA-600:[1265] in 10.2, you are potentially hitting this problem.

Problem occurs at 22.00pm, due to that the default maintenance window is created as WEEKNIGHT_WINDOW begins 22:00 every weekday and ends 06:00, causing several customers to see this problem at 22:00.
See Support Article for more details related to this specific problem. 1377939.1
Title:
ORA-00600: [1265] and ORA-00600 [18194] When Querying a Remote View
    
      
Diagnostic steps

The resolution of ORA-600 [1265] depends on reproducibility.
Please consider below diagnostic steps when hitting ORA-600 [1265]:

1. When problem reproduces more than once, submit the following information to Oracle Support for investigation by raising a Service Request:

    a) ALERT log
    b) ORA-600 [1265] trace files
    c) opatch lsinventory -detail
    d) Information about the client application and objects involved in failing SQL.
    e) Is there any noticeable pattern for when the error is occurring?
    f) Provide information about actions taken at the time of the error (backups, scheduled jobs, SQL etc).

2. If the function ksuprc is in the call stack trace the following events are useful and might be requested by Oracle Support:

    event="10422 trace name context forever, level 4"
    event="10786 trace name context forever, level 1000"
    _trace_buffers="FGS:512;BGS:512"

Note:
These events should be set with care and removed once ORA-600 [1265] is no longer investigated.
The events will add a minor overhead when collecting trace information into in-memory circular buffers which will be dumped out in the ORA-600 [1265] trace.
If possible test the impact of setting these events in a test environment first.

3. Consider applying a diagnostic patch?

If the problem appears frequently enough and a defect has been raised with development, the resolution of this problem requires a diagnostic patch to be installed.
A diagnostic patch collects more information about the situation and is known to be RAC rolling installable, controlled by an event.

REFERENCES

BUG:11804223 - ORA-600 [1265]/[18194] INTERMITTENTLY

BUG:8209133 - ORA-600 [1265] WHEN QURYING A REMOTE VIEW
BUG:8758842 - ORA-600 [1265] FROM DBLINK
BUG:9802732 - ORA-600[1265] OCCUR
BUG:9928341 - ORA-600 [1265] FAILURES ON JOBS USING DBLINK TO GL DATABASE
NOTE:1377939.1 - ORA-00600: [1265] and ORA-00600 [18194] When Querying a Remote View
NOTE:138374.1 - ORA-600 [1265]

如需转载，请注明出处：http://blog.csdn.net/nanaranran/article/details/34417439