My Oracle Support Banner

Receiving Ora-07445 Core Dump Hok2beg Refreshing Materialized View Using Dg4odbc and IBM iSeries ODBC Driver (Doc ID 1310704.1)

Last updated on APRIL 09, 2020

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.2]
Information in this document applies to any platform.


Using Database Gateway for ODBC (DG4ODBC) to refresh a materialized view using the IBM iSeries ODBC driver to tables on an AS400 causes an ORA-7445 error -

ORA-07445: exception encountered: core dump [hok2beg()+191] [SIGSEGV] [ADDR:0x0] [PC:0x6695323] [Address not mapped to object] []

This happens when running the materialized view refresh as a job and the job trace file shows the following -

dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x3, level=3, mask=0x0)
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0x251d0e178 84 package body SYS.DBMS_SNAPSHOT
0x251d0e178 1808 package body SYS.DBMS_SNAPSHOT
0x251d0e178 2519 package body SYS.DBMS_SNAPSHOT
0x251d0e178 2771 package body SYS.DBMS_SNAPSHOT
0x251d0e178 2740 package body SYS.DBMS_SNAPSHOT
0x251e0e9f8 34 package body REFRESH_PACKAGE_NAME
0x251e0e9f8 11 package body REFRESH_PACKAGE_NAME
0x252176ba8 1 anonymous block

----- Call Stack Trace -----

ksedst1 <- ksedst <- dbkedDefDump <- ksedmp <- ssexhd
<- restore_rt <- hok2beg <- hok2pc <- hogdre <- npixfc
<- k2rbeg <- npibeg <- npidr0 <- npikgl <- opikgl
<- opiodr <- PGOSF141_rpidrus <- skgmstack <- rpiswu2 <- rpidrv
<- rpikgl <- kqlrlk <- kqlrhdld <- kqlhdlod <- kqllod
<- kglLoadOnLock <- kgllkal <- kglLock <- kglget


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.