oracle 未找到dr0,ORA-27041 unable to open file

[Kgghash()+428] [Access_violation] REPORTED IN ALERT LOG [ID 732550.1]

Applies to:

Oracle Server - Enterprise Edition - Version: 11.1.0.6 to 11.1.0.7 - Release: 11.1 to 11.1

Information in this document applies to any platform.

Oracle Server Enterprise Edition - Version: 11.1.0.6 to 11.1.0.7

Symptoms

This article is written specifically for 7445[kgghash()] when seen in conjunction with the following

symptoms :-

a) Message in alert log will be similar to :-

ORA-07445: exception encountered: core dump [kgghash()+428]

[ACCESS_VIOLATION] [ADDR:0xE180000][PC:0x5CA3D60]

[UNABLE_TO_READ] []

b) Stack will be similar to :-

Function List (to Full stack) (to Summary stack)

kgghash

c) In the trace we see :-

_kkocsCreateBindSet CALLrel _kgghash()+0 xxxxxx 1F40 xxxxxx

1F40 is a key value here

Cause

If the above symptoms are seen unpublished Bug 7352414 is the likely cause but to make

this conclusion other bugs need to be referred to.

Solution

Bug 6650766 reports :-

It appears that we are passing in 8000 (1F40) when the buffer length is less (4000).

bnd.kxsbplen is 8000 and is avl.

A trace file can be searched for the 'current cursor' and then the bind values for that

cursor can be reviewed :-

Bind#2

oacdty=01 mxl=4001(4672) mxlc=00 mal=00 scl=00 pre=00

oacflg=13 fl2=206001 frm=01 csi=31 siz=4000 off=0

kxsbbbfp=0e17ed10 bln=4000 avl=8000 flg=09

value="660PRO

gt;052P_0108/11/2008

09:02A000006779E66EC91DC43EBB06DC2F6FA17AA75<

;/User>Ce"...

So in summary if we see ORA-7445[KGGHASH] where 1F40 is seen in the call from kkocsCreateBindSet and we see a bind showing bln=4000 avl=8000

we are likely to be facing this bug.

It should be noted that analysis on Bug 6650766 comes to a halt but similar symptoms

were filed under Bug 7343776  which was confirmed to be a duplicate of

unpublished Bug 7352414.

It was initially mentioned under Bug 6650766  that some diagnostics patch would

need to be written but this position has changed.

unpublished Bug 7352414

This issue is fixed in 11.2.0.1 (Base Release)

11.1.0.7.1 (Patch Set Update)

11.1.0.7 Patch 2 on Windows Platforms

11.1.0.7 Generic Recommended Patch Bundle

Note that this fix has been superseded by the fix in unpublished Bug 8763922

unpublished Bug 8763922

This issue is fixed in 12.1 (Future Release)

11.2.0.2 (Server Patch Set)

11.2.0.1 Bundle Patch 9 for Exadata Database

11.1.0.7.5 (Patch Set Update)

11.1.0.7 Patch 23 on Windows Platforms

This fix is really just an extension to the fix for  to also cover the same scenario for RAW binds.

Solution

Apply the patch 8763922 if available

OR

Try the following workaround:

Disabling bind peeking.

This would be enabled via setting :-

_optim_peek_user_binds=false

References

BUG:7343776 - INTERMITTENT 7445[KGGHASH] THAT SEEMS TO LINK TO BUG:6650766

BUG:6650766 - ORA-07445: EXCEPTION ENCOUNTERED: CORE DUMP [KGGHASH()+428] [ACCESS_V