Oracle ORA-07445 [evaopn3 () + 384] Error Analysis

1. OS and DB versions

Oracle Version: 11.2.0.2

Operation System: HP-UXItanium 11.31

2. Alert log Information

Tue Oct 22:27:31 2012

Exception [type: SIGSEGV, Address not mapped to object] [ADDR: 0xC00000000] [PC: 0x400000000631B880, evaopn3 () + 384] [flags: 0x0, count: 1]

Errors in file/oracle/app/oracle/diag/rdbms/wzpartdb/trace/wzpartdb_j004_19591.trc (incident = 56673 ):

ORA-07445: predictionencountered: core dump [evaopn3 () + 384] [SIGSEGV] [ADDR: 0xC00000000] [PC: 0x400000000631B880] [Address not mapped to object] []

Incident details in:/oracle/app/oracle/diag/rdbms/wzpartdb/incident/incdir_56673/wzpartdb_j004_19591_i56673.trc

Use ADRCI or Support Workbench to packagethe incident.

See Note 411.1 at My Oracle Support forerror and packaging details.

Tue Oct 22:27:56 2012

Dumping diagnostic data indirectory = [cdmp_20121016222756], requested by (instance = 1, osid = 19591 (J004), summary = [incident = 56673].

Tue Oct 22:27:58 2012

Sweep [inc] [56673]: completed

Sweep [inc2] [56673]: completed

3. Problem locating

Errors related to ORA-7445 are mostly related to bugs. Generally we need to pay attention to the type of the first parameter, here is evaopn3. Here is a special article on MOS. For details, refer:

ORA-7445 [evaopn3] (Doc ID 860969.1)

Here is an error with us:

ORA-07445: predictionencountered: core dump [evaopn3 () + 384] [SIGSEGV] [ADDR: 0xC00000000] [PC: 0x400000000631B880] [Address not mapped to object] []

It may be related to encryptedcolumns, function-based index, and Xquery. Some known bugs are as follows:

Bug 13369579-dump on evaopn3 withfunction base index and order by (Doc ID 13369579.8)

Bug 12724375-ORA-7445 [evaopn3] fromXQuery with group by (Doc ID 12724375.8)

Bug 12672969-Assorted Dumps withaggregate expression in order by (Doc ID 12672969.8)

Bug 13817586-Dump on evaopn3 withEncrypted Columns (Doc ID 13817586.8)

After troubleshooting, I am using bug 12672969.

Bug 12672969-Assorted Dumps withaggregate expression in order by (Doc ID 12672969.8)

Check the trace and confirm that an SQL statement uses the aggregation function in order. An error that triggers the ORA-7445 when you execute this SQL statement.

You can perform the following verification:

Create table test1 (col1 number, col2number );

Insert into test1 values (1, 1 );

Commit;

Select count (*)

From (select col2

From test1

Group by col2 order by (sum (col2) + 1 ));

Rediscovery Notes:

1. ORA-7445 in aggregation evaluation function including evaopn3

2. Order by elimination is saved med

3. Set function exists in the middle of theoperator tree in order

Clause

4. The fix for bug 8772028 is present

4. Solution

The solution on MOS is to modify parameters:

Alter sessionset "_ optimizer_order_by_elimination_enabled" = false;

However, this is an implicit parameter. modification may cause other problems. Oracle contention provides Patch: 12672969 for this bug.

After the Patch is applied, run the SQL statement that triggers the bug to confirm the bug fix.