Bug 696913

Summary: Satellite 5.4 - ORA600 Error Messages
Product: Red Hat Satellite 5 Reporter: Francisco Lopez <flopezyg>
Component: OtherAssignee: Jan Pazdziora <jpazdziora>
Status: CLOSED NOTABUG QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 540CC: cperry, kabbott
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-21 06:34:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 462714    

Description Francisco Lopez 2011-04-15 08:52:28 UTC
Description of problem:
After patching the satellite [oracle RDBMS]
The error message ORA600 apeared in the logs - two times per day.
Version-Release number of selected component (if applicable):
5.4

How reproducible:
always

Steps to Reproduce:

1. Status: Satellite 5.4 on Oracle 11.2.0.1.0 
Then daily at about 22:00 an ORA 7445 occured. The offered solution was to patch Oracle RDBMS

2. Status: Satellite 5.4 on Oracle 11.2.0.2.0
Then daily at about 22:00 an ORA 600: internal error code, arguments: [kopuigpfx1], [13], [], [], [], [], [], [], [], [], [], [] occures

root cause analysis showed us this command leads into the ORA 600

SELECT /* DS_SVC */ /*+ cursor_sharing_exact dynamic_sampling(0) no_sql_tune no_monitoring optimizer_features_enable(default) */ SUM(C1)
  FROM (SELECT /*+ qb_name("innerQuery") NO_INDEX_FFS( "PUAC#1")  */ 1 AS C1
          FROM (SELECT SYS_OP_NOEXPAND("NP_PE"."EVR") "ITEM_1","NP_PE"."SYS_NC00006$" "ITEM_2","NP_PE"."SYS_NC00007$" "ITEM_3","NP_PE"."SYS_NC00008$" "ITEM_4","NP_NP"."NAME_ID" "ITEM_5","NP_NP"."PACKAGE_ARCH_ID" "ITEM_6","NP_NP"."CHANNEL_ID" "ITEM_7",MAX("NP_PE"."EVR") "ITEM_8"
                  FROM "RHNPACKAGEEVR" "NP_PE","RHNCHANNELNEWESTPACKAGE" "NP_NP"
                 WHERE "NP_PE"."ID"="NP_NP"."EVR_ID"
                 GROUP BY SYS_OP_NOEXPAND("NP_PE"."EVR"),"NP_PE"."SYS_NC00006$","NP_PE"."SYS_NC00007$","NP_PE"."SYS_NC00008$","NP_NP"."NAME_ID","NP_NP"."PACKAGE_ARCH_ID","NP_NP"."CHANNEL_ID") "VW_GBC_9#3",
                "RHNPACKAGEUPGRADEARCHCOMPAT" "PUAC#1"
          WHERE ("PUAC#1"."PACKAGE_UPGRADE_ARCH_ID"="VW_GBC_9#3"."ITEM_6")
       ) innerQuery


looking deeper into this we identified this part as the trigger:
SELECT SYS_OP_NOEXPAND("NP_PE"."EVR") "ITEM_1","NP_PE"."SYS_NC00006$" "ITEM_2","NP_PE"."SYS_NC00007$" "ITEM_3","NP_PE"."SYS_NC00008$" "ITEM_4","NP_NP"."NAME_ID" "ITEM_5","NP_NP"."PACKAGE_ARCH_ID" "ITEM_6","NP_NP"."CHANNEL_ID" "ITEM_7",MAX("NP_PE"."EVR") "ITEM_8"
  FROM "RHNPACKAGEEVR" "NP_PE","RHNCHANNELNEWESTPACKAGE" "NP_NP"
 WHERE "NP_PE"."ID"="NP_NP"."EVR_ID"
 GROUP BY SYS_OP_NOEXPAND("NP_PE"."EVR"),
          "NP_PE"."SYS_NC00006$",
          "NP_PE"."SYS_NC00007$",
          "NP_PE"."SYS_NC00008$",
          "NP_NP"."NAME_ID",
          "NP_NP"."PACKAGE_ARCH_ID",
          "NP_NP"."CHANNEL_ID";

with this command we can reproduce the ORA-600 at will

Actual results:


Expected results:


Additional info:

These are direct informations from the orafaq 


Oracle Documentation - ORA 600 
°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°

ORA-600 is an internal error generated by the generic kernel code of the Oracle RDBMS software. It is different from other Oracle errors in many ways. The following is a list of these differences:

1. An ORA-600 error may or may not be displayed on the screen. Therefore, screen output should not be relied on for capturing information on this error. Information on ORA-600 errors are found in the database alert and trace files. We recommend that you check these files frequently for database errors. (See the Alert and Trace Files section for more information.)

2. Each ORA-600 error comes with a list of arguments They usually enclosed in square brackets and follow the error on the same line for example:

ORA-00600 [14000][51202][1][51200][][]

Each argument has a specific meaning which can only be interpreted by an Oracle support analyst. The arguments may also change meaning from version to version therefore customers are not advised to memorize them.

3. Every occurrence of an ORA-600 should be reported to Oracle Support. Unlike other errors, you can not find help text for these errors. Only Oracle technical support should diagnose and take actions to prevent or resolve damage to the database.

4. Each ORA-600 error generates a database trace file. 

°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
Possible causes

Possible causes include:

    * time-outs,
    * file corruption,
    * failed data checks in memory, hardware, memory, or I/O messages,
    * incorrectly restored files
    * a SELECT FROM DUAL statement in PL/SQL within Oracle Forms (you have to use SELECT FROM SYS.DUAL instead!) 
°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
Check adrci - which ships with the oracle database software. (ora 11) 
Check adr  - also (ora 11) 


°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°

http://www.orafaq.com/wiki/ADR
http://www.orafaq.com/wiki/Adrci
http://www.orafaq.com/wiki/ORA-00600

Comment 1 Jan Pazdziora 2011-04-15 09:56:58 UTC
(In reply to comment #0)
> Description of problem:
> After patching the satellite [oracle RDBMS]
> The error message ORA600 apeared in the logs - two times per day.
> Version-Release number of selected component (if applicable):
> 5.4
> 
> How reproducible:
> always
> 
> Steps to Reproduce:
> 
> 1. Status: Satellite 5.4 on Oracle 11.2.0.1.0 
> Then daily at about 22:00 an ORA 7445 occured. The offered solution was to
> patch Oracle RDBMS
> 
> 2. Status: Satellite 5.4 on Oracle 11.2.0.2.0
> Then daily at about 22:00 an ORA 600: internal error code, arguments:
> [kopuigpfx1], [13], [], [], [], [], [], [], [], [], [], [] occures

As this is clearly an external Oracle RDBMS, please proceed by following the recomendation in the Oracle documentation:

> 3. Every occurrence of an ORA-600 should be reported to Oracle Support. Unlike
> other errors, you can not find help text for these errors. Only Oracle
> technical support should diagnose and take actions to prevent or resolve damage
> to the database.

Thank you,

Jan