Last updated on MAY 09, 2017
Applies to:
Oracle OLAP - Version 10.2.0.4 and laterInformation in this document applies to any platform.
Symptoms
The problem described here may occur under these circumstances:
- Attempt to apply a patch that affects the OLAP option (for instance a Critical Patch Update)
- Attempt to (re-)install the OLAP option on an existing RDBMS instance
- OLAP may be partially installed on a 10g Standard Edition RDBMS
Errors may be generated in several places:
- RDBMS alert.log
- A trace file
- an OPatch log (transcript)
- Output during execution of a SQL script like olap.sql
- Log file in Universal installer
Example of an entry in the alert.log file:
[ACCESS_VIOLATION][_xspgReducePool+3171]
[PC:0x2983D47] [ADDR:0x208] [UNABLE_TO_WRITE] []
Example of a trace file entry:
Current SQL statement for this session:
BEGIN dbms_aw_build.build('EXPRESS', FALSE); END;
----- 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
1
_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
ERROR:
ORA-03114: not connected to ORACLE
Important:
Errors like the following indicate a different issue:
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.
Changes
The following circumstances can lead to this issue:
- A Patch installation is attempted on a non-operational OLAP option
For example, see <Note 556194.1> Use Of Database Templates with Standard Edition Cause
Problems With OLAP
- A Critical Patch Update (CPU) is applied to an instance where the OLAP option is installed.
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_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):
-------- ------------------------------ ------------ --------
APS OLAP Analytic Workspace 10.2.0.3.0 VALID
XOQ Oracle OLAP API 10.2.0.3.0 VALID
AMD OLAP Catalog 10.2.0.3.0 VALID
If you receive no rows, then the OLAP components are not installed and this note does not apply to this instance.
- Installation of the OLAP option on an existing RDBMS 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.
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