Last updated on FEBRUARY 07, 2014
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 and laterInformation in this document applies to any platform.
Symptoms
You receive an ORA-07445 [ioc_get_IU_info] internal error, which produces a trace file. The database alert log provides the first appearance of the incident:
Thu Feb 3 09:43:26 2011
Errors in file /orcl/admin/appsprd/udump/appsprd_ora_13740.trc:
ORA-07445: exception encountered: core dump [ioc_get_IU_info()+820] [SIGBUS] [Invalid address alignment] [0x6E697665727369B4] [] []
When you examine the trace file specified in the alert log, you find that the offending SQL is a call to a packaged procedure within a PL/SQL anonymous code block.
Current SQL statement for this session:
begin ies_new_end_of_script_pkg.saveEndOfScriptData(:1); end;
----- PL/SQL Call Stack -----
object line object
handle number name
44a74a780 14 package APPS.XMLPARSERCOVER
43fef3d80 91 package body APPS.XMLPARSER
44a74b6c8 414 package body APPS.IES_NEW_END_OF_SCRIPT_PKG
44a74bdb0 1 anonymous block
The stack trace generated may contain a list of function names similar to the following:
ioc_get_IU_info iocbf_get_IU_info ioc_do_call joet_switched_env_callback ioct_get_IU_info jom_establish_schema_jom_shared_clint_ref
Changes
No changes have been made to the package.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