Patch Application or OLAP installation Causes Errors ORA-07445, ORA-03113, ORA-03114

(Doc ID 465902.1)

Last updated on MAY 09, 2017

Applies to:

Oracle OLAP - Version and later
Information in this document applies to any platform.


The problem described here may occur under these circumstances:

Errors may be generated in several places:

Example of an entry in the alert.log file:

ORA-07445: exception encountered: core dump
 [PC:0x2983D47] [ADDR:0x208] [UNABLE_TO_WRITE] []

Example of a trace file entry:

ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_xspgReducePool+3171] [PC:0x2983D47] [ADDR:0x208] [UNABLE_TO_WRITE] []
Current SQL statement for this session:
----- PL/SQL Call Stack -----
object line object
handle number name
9383404C 51 package body SYS.DBMS_AW
9383404C 143 package body SYS.DBMS_AW
8DF6AC6C 99 package body SYS.DBMS_AW_BUILD
8DEFA4F4 1 anonymous block
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
_xspgReducePool+317 00000000
_xspgShrinkPool+776 CALLrel _xspgReducePool+0 2 36 6D
_xspgpoolExit+3 CALLrel _xspgShrinkPool+0
_xsExit+295 CALLrel _xspgpoolExit+0
_xsRun+783 CALLrel _xsExit+0 215CB960
_xsRunLN+34 CALLrel _xsRun+0 215CC4E4 215CBA90 215CBAA4

Example of an OPatch log transcript:


ERROR at line 1:
ORA-03113: end-of-file on communication channel 

ORA-03114: not connected to ORACLE 


Errors like the following indicate a different issue:

ORA-07445: exception encountered: core dump [xsUpdSessionNLSLanguage()+148] [SIGBUS] [Invalid address alignment] [0x43100000009] [] []

This error usually indicates a possible problem with the patch itself (e.g. applied a patch for a different platform, files within the patch may be corrupted/broken), etc.

In this case, collect the installation and post-installation logs, alert log and trace files and report the issue to Oracle Support to determine the cause and workaround.


The following circumstances can lead to this issue:

Note it is sometimes not obvious that the OLAP option has been installed. Use the following SQL commands while connected as SYSDBA to find out:

SQL> col comp_id format a8
SQL> col comp_name format a30
SQL> col version format a12
SQL> col status format a8
SQL> select comp_id, comp_name, version, status from dba_registry where comp_name like '%OLAP%';

Output similar to the following indicates that the OLAP option is installed (even if status and/or version are showing different values):

COMP_ID  COMP_NAME                      VERSION      STATUS
-------- ------------------------------ ------------ --------
APS      OLAP Analytic Workspace   VALID
XOQ      Oracle OLAP API         VALID
AMD      OLAP Catalog            VALID

If you receive no rows, then the OLAP components are not installed and this note does not apply to this instance.

The steps to use the script are described in: How To Manually Install Oracle OLAP In 9i, 10g Or 11g Database After The DB Has Been Created (Doc ID 296187.1). The issue described here may also occur if you use Universal Installer to add the OLAP option.


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