ORA-600 [13011] when trying to delete a row-28184.1

rongshiyuan發表於2013-01-23
delete
ORA-600 [13011] "Problem occurred when trying to delete a row" [ID 28184.1]
 
Note: For additional ORA-600 related information please read Note:146580.1 PURPOSE: This article represents a partially published OERI note. It has been published because the ORA-600 error has been reported in at least one confirmed bug. 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: #helpWin {position:absolute; width:400; visibility:hidden; background-color:#f7f7e7; padding:20px; border-width:2px; border-left-color:#336699; border-top-color:#336699; border-right-color:#336699; border-bottom-color:#336699; border-style.:solid; margin-top:70px; margin-left:330px; }
Help text goes here.

Format: ORA-600 [13011] [a] [b] [c] [d] [e]
 
VERSIONS:
  versions 7.3 and above
 

ARGUMENTS:

  The number of arguments and their meaning vary depending on the 
  object types relating to the error.

3 Argument format
=================

This format relates to Oracle 8.0.3 and above for deletes from Views or Index Only Tables (IOT)

  Arg [a] Passcount (5000)
  Arg [b] Object Name
  Arg [c] Code

5 Argument format
=================

  Arg [a] Data Object ID
  Arg [b] Tablespace Decimal Relative DBA (RDBA) of block containing the row to be deleted
  Arg [c] Row slot number.
  Arg [d] Decimal RDBA of block being updated (Typically same as [b]). 
  Arg [e] Code


SUGGESTIONS:        

  Run ANALYZE INDEX  VALIDATE STRUCTURE;
  on any indices involved.  Drop and recreate if needed.

  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:

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



NBBugFixedDescription
1024525911.2.0.2.BP03, 11.2.0.3, 12.1.0.0PARALLEL INSERT with +NOAPPEND hint or if PARALLEL INSERT plan is executed in SERIAL corrupts index and causes wrong results V11020001 V11020002 CORR/IND ERROR OERI PQO WRONGRES
733628011.1.0.7.8, 11.2.0.1ORA-600[13009] / ORA-600[13011] on column added with DEFAULT value NOT NULL V11010006 V11010007 OERI RMAN
700792410.2.0.5, 11.2.0.1Wrong results using bitmap index V09020008 V10010005 V10020002 V10020003 V10020004 V11010006 V11010007 BITMAP OERI WRONGRES
5331867.3.4.5, 8.0.4.0ORA-1499 / OERI:13011 after UPDATE of an inline view CORR/IND ERROR OERI
  • '*' against a bug indicates that an alert exists for that issue.
  • '+' indicates a particularly notable bug.
  • '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].








References
 BUG:189281 - ORA-00600 [13011], [5001], [3], [603981631], [0], [603981631],
 BUG:427969 - ORA-600[13013 WHILE UPDATING IN A TABLE WITH TRIGGERS
 BUG:452224 - ORA 600 [13011] ON DELETE STATEMENT WITH 2 SUBSELECTS
NOTE:146580.1 - What is an ORA-600 Internal Error?
NOTE:533186.8 - Bug 533186 - ORA-1499 / OERI:13011 after UPDATE of an inline view
NOTE:7007924.8 - Bug 7007924 - Wrong results using bitmap index
NOTE:7336280.8 - Bug 7336280 - ORA-600[13009] / ORA-600[13011] on column added with DEFAULT value NOT NULL
NOTE:10245259.8 - Bug 10245259 - PARALLEL INSERT with +NOAPPEND hint or if PARALLEL INSERT plan is executed in SERIAL corrupts index and causes wrong results

			
			
                                                            

                    

                                                    來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/17252115/viewspace-753118/，如需轉載，請註明出處，否則將追究法律責任。
                                            


                




相關文章