My Oracle Support Banner

ORA-07445 [kocdsup()+350] Reported During Startup (after Bundle Patch Rollback) (Doc ID 1942244.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version and later
Microsoft Windows x64 (64-bit)


 The following errors reported while starting an Oracle database on Windows:

    ORA-03113: end-of-file on communication channel

Error reported in alert.log:

    ORA-07445: exception encountered: core dump [kocdsup()+350] [ACCESS_VIOLATION] [ADDR:0x0] [PC:0x11EE53C] [UNABLE_TO_READ] []


 Call stack in trace file written by the error:

    kocdsup <- kokgugi <- ksmuin <- ksucre <- ksucresg
       <- kpolna <- kpoauth <- opiodr <- sageCacheAllocateSt <- ats
        <- opitsk <- ck <- opiino <- opiodr <- opidrv
         <- sou2o

Also the following messages are reported in incident trace file:

    ---------- messages from pre-loading .sym files:
    Symbol file D:\u01\app\oracle\product\11.2.0\RDBMS\ADMIN\oraclient11.SYM does not match binary.
    Symbol TimeStamp=4eb215e6, Module TimeStamp=52381405 are different
    Symbol file D:\u01\app\oracle\product\11.2.0\RDBMS\ADMIN\oracommon11.SYM does not match binary.
    Symbol TimeStamp=4eb215cc, Module TimeStamp=523813f7 are different
    Symbol file D:\u01\app\oracle\product\11.2.0\RDBMS\ADMIN\orageneric11.SYM does not match binary.
    Symbol file D:\u01\app\oracle\product\11.2.0\RDBMS\ADMIN\OCI.SYM does not match binary.
    Symbol TimeStamp=4eb212ea, Module TimeStamp=5088d40e are different
    ----------- end of messages from pre-loading .sym files
    ----- Call Stack Trace -----
    calling              call     entry                argument values in hex      
    location             type     point                (? means dubious value)    
    -------------------- -------- -------------------- ----------------------------
    Symbol file D:\u01\app\oracle\product\11.2.0\BIN\oraclient11.SYM does not match binary.
    Symbol TimeStamp=4eb215e6, Module TimeStamp=52381405 are different


Customer rolled back BP (Bundle Patch) 28. After this change the database startup failed due to above mentioned exceptions.


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.