2011-11-25

ORA-07445: exception encountered: core dump [_intel_fast_memcpy.A()+10] [SIGSEGV] [Address not mapped to object]

This error can occur , when you migrated from 32bit to 64 bit :
The solution can be found in
DB CONVERSION: 32 bit -->64 Bit Broke OLAP OPTION [ID 386990.1]

Applies to:

Oracle OLAP - Version: 10.2.0.2 and later   [Release: 10.2 and later ]
Information in this document applies to any platform.

Symptoms


You receive the following error when you try to create new AW or attach exsisting AW:
SQL> conn zpb/zpb
Connected.
SQL> exec dbms_aw.execute('aw attach ZPBANNOT rw');
BEGIN dbms_aw.execute('aw attach ZPBANNOT rw'); END;

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

Alert.log has following errors:

Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr:
0x2b98387d77, PC: [0x2a9582f260, _intel_fast_memcpy.A()+10]
OR
ORA-07445: exception encountered: core dump [_intel_fast_memcpy.A()+10]
[SIGSEGV] [Address not mapped to object] [0x2B98387D77] [] [] 

Changes

Database was upgraded from 32bit to 64bit 

Cause

The problem is that the 64-bit compiler pads structures containing ub8s differently than the 32-bit version of the compiler

Solution

1. Remove OLAP:
At the system prompt 'cd' to the ORACLE_HOME/olap/admin directory then:
SQL> @?/olap/admin/catnoamd.sql
SQL> @?/olap/admin/catnoaps.sql 
SQL> @?/olap/admin/catnoxoq.sql
SQL> @?/olap/admin/olapidrp.plb

2. Add OLAP

Add the OLAP option to an existing Enterprise Edition Database
Assuming that you created your database manually or via DBCA, Enterprise
Edition in Oracle Database 10g:

SQL> connect SYS as SYSDBA
SQL> Spool olap.log

SQL> @?/olap/admin/olap.sql SYSAUX TEMP;

3. Recompile any invalid objects:

SQL> @?/rdbms/admin/utlrp

4. Check for any invalid OLAPSYS objects:

SQL> select owner, object_name, object_type, status from dba_objects where status = 'INVALID' and OWNER = 'OLAPSYS' ;
5. Check OLAP components in the  DBA_REGISTRY.


SQL> column comp_name format a35 
SQL> SELECT comp_name, status, substr(version,1,10) as version from dba_registry;
SQL> Spool Off
 NOTE: If you are getting the above error only on existing AWs, but you can create new AWs, you do not need to remove OLAP. You only need to recreate the affected AWs.

NOTE: You need to export your 32 bit AWs prior to upgrading to 64 bit.
See Metalink Note:  352306.1  for more information.

Niciun comentariu:

Trimiteți un comentariu