J00 Trace Files Generated After 11g Upgrade With Bind Mismatch Messages (Doc ID 1229793.1)

Last updated on AUGUST 05, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2 and later
Information in this document applies to any platform.
***Checked for relevance on 06-Aug-2016***

Symptoms


Jox Trace files being generated that contains message like the following:

Current Cursor Sharing Diagnostics Nodes:
Child Node: 7 ID=34 reason=Rolling Invalidate Window Exceeded(2) size=0x0
already processed:
Child Node: 7 ID=34 reason=Rolling Invalidate Window Exceeded(3) size=2x4
invalidation window(kglobitm): 1282721383
ksugctm(): 1282798941
Child Node: 8 ID=34 reason=Rolling Invalidate Window Exceeded(3) size=2x4
invalidation window(kglobitm): 1282723664
ksugctm(): 1282798941
Child Node: 12 ID=40 reason=Bind mismatch(22) size=4x4
bind position: 27
original oacflg: 24
original oacmxl: 128
upgradeable new oacmxl: 32

OR

status=(pst=SUCCESS)
**************************************************************
Execution Statistics
Exec count: 1
CR gets: 979
CU gets: 0
Disk Reads: 0
Disk Writes: 0
IO Read Requests: 0
IO Write Requests: 0
Bytes Read: 0
Bytes Written: 0
Bytes Exchanged with Storage: 0
Bytes Exchanged with Disk: 0
Bytes Simulated Read: 0
Bytes Simulated Returned: 0
Elapsed Time: 31 (ms)
CPU Time: 20 (ms)
User I/O Time: 0 (us)
status=(pst=ERROR)
status=(pst=SUCCESS)
**************************************************************

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms