| How validate OLAPSYS schema objects after transferring Database from windows 2003 32 bit to 2008 64 [message #504042] |
Thu, 21 April 2011 04:07  |
MIFI
Messages: 256
Registered: February 2008
Location: U.K.
|
Senior Member |
|
|
Hi,
We transferred our Oracle database 11.1.0.7 from windows 2003 enterprise edition 32 bit to windows 2008 enterprise edition server 64 bit.
Database is working fine but we have 53 uncompiled objects which are related to OLAPSYS and public as follows
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_LVL VIEW
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_MEAS VIEW
OLAPSYS MRAC_OLAP2_AW_DIMENSIONS_V VIEW
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_OP VIEW
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_SPECS VIEW
OLAPSYS ALL$OLAP2_AW_DIM_LEVELS VIEW
OLAPSYS ALL$AW_CUBE_ENABLED_HIERCOMBO VIEW
OLAPSYS ALL$OLAP2_AW_CUBE_MEASURES VIEW
OLAPSYS ALL$OLAP2_AW_DIM_HIER_LVL_ORD VIEW
OLAPSYS OLAP_SYS_AW_ENABLE_ACCESS_VIEW VIEW
OLAPSYS OLAP_SYS_AW_ACCESS_CUBE_VIEW VIEW
OLAPSYS DBMS_AWM PACKAGE BODY
OLAPSYS CWM2_OLAP_OLAPAPI_ENABLE PACKAGE BODY
OLAPSYS OLAP_SYS_AW_ACCESS_DIM_VIEW VIEW
OLAPSYS MRAC_OLAP2_AW_CUBES_V VIEW
OLAPSYS MRAC_OLAP2_AW_ATTRIBUTES_V VIEW
OLAPSYS CWM2_OLAP_METADATA_REFRESH PACKAGE BODY
OLAPSYS MRAC_OLAP2_AW_CUBE_MEASURES_V VIEW
OLAPSYS ALL$AW_CUBE_ENABLED_VIEWS VIEW
OLAPSYS ALL$OLAP2_AW_CUBES VIEW
OLAPSYS ALL$OLAP2_AW_PHYS_OBJ VIEW
OLAPSYS ALL$OLAP2_AW_CUBE_DIM_USES VIEW
OLAPSYS ALL$OLAP2_AW_DIMENSIONS VIEW
OLAPSYS ALL$OLAP2_AW_PHYS_OBJ_PROP VIEW
OLAPSYS ALL$OLAP2_AW_ATTRIBUTES VIEW
OLAPSYS ALL$OLAP2_AW_CATALOG_MEASURES VIEW
OLAPSYS ALL$AW_DIM_ENABLED_VIEWS VIEW
OLAPSYS ALL$OLAP2_AW_CATALOGS VIEW
PUBLIC MRV_OLAP2_AW_ATTRIBUTES SYNONYM
PUBLIC OLAP_SYS_AW_ENABLE_ACCESS_VIEW SYNONYM
PUBLIC ALL_OLAP2_AW_CATALOGS SYNONYM
PUBLIC MRV_OLAP2_AW_DIMENSIONS SYNONYM
PUBLIC MRV_OLAP2_AW_CUBES SYNONYM
PUBLIC ALL_OLAP2_AW_CATALOG_MEASURES SYNONYM
PUBLIC OLAP_SYS_AW_ACCESS_CUBE_VIEW SYNONYM
PUBLIC OLAP_SYS_AW_ACCESS_DIM_VIEW SYNONYM
PUBLIC MRV_OLAP2_AW_CUBE_MEASURES SYNONYM
PUBLIC ALL_OLAP2_AW_PHYS_OBJ SYNONYM
PUBLIC ALL_OLAP2_AW_PHYS_OBJ_PROP SYNONYM
PUBLIC ALL_OLAP2_AW_CUBE_DIM_USES SYNONYM
PUBLIC ALL_OLAP2_AW_DIM_HIER_LVL_ORD SYNONYM
PUBLIC ALL_OLAP2_AW_CUBE_MEASURES SYNONYM
PUBLIC ALL_OLAP2_AW_DIM_LEVELS SYNONYM
PUBLIC ALL_AW_CUBE_ENABLED_VIEWS SYNONYM
PUBLIC ALL_AW_DIM_ENABLED_VIEWS SYNONYM
PUBLIC ALL_AW_CUBE_ENABLED_HIERCOMBO SYNONYM
PUBLIC ALL_OLAP2_AW_CUBE_AGG_LVL SYNONYM
PUBLIC ALL_OLAP2_AW_CUBE_AGG_OP SYNONYM
PUBLIC ALL_OLAP2_AW_DIMENSIONS SYNONYM
PUBLIC ALL_OLAP2_AW_ATTRIBUTES SYNONYM
PUBLIC ALL_OLAP2_AW_CUBES SYNONYM
PUBLIC ALL_OLAP2_AW_CUBE_AGG_SPECS SYNONYM
PUBLIC ALL_OLAP2_AW_CUBE_AGG_MEAS SYNONYM
when i am trrying to recompile them getting Internal error in alert log like
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x1256E22E7] [PC:0x52B428E, _intel_fast_memcpy.A()+18]
Errors in file e:\app\oracle\diag\rdbms\c1\c1t\trace\c1t_ora_1644.trc (incident=41666):
in incident file it is showing as follows
========= Dump for incident 41666 (ORA 7445 [intel_fast_memcpy.A()+18]) ========
----- Beginning of Customized Incident Dump(s) -----
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x1256E22E7] [PC:0x52B428E, _intel_fast_memcpy.A()+18]
Oracle Database 11g Release 11.1.0.7.0 - 64bit Production
Process Id: 0x00000cc4 Thread Id : 0x0000066c Time : Wed Apr 20 18:00:30
Excp. Code: 0xc0000005 Excp. Type: ACCESS_VIO Flags: 0x00000000
------------------- Registers ----------------------------
ip=00000000052B428E sp=0000000025C22788 rp=0000000006AE0320
r1=0000000025C22840 r2=0000000000000004 r3=00000001256E22E7
r4=00000000256E22E8 r5=0000000025C22788 r6=0000000006AE0320 r7=00000001256E22E7
r8=0000000025C22840 r9=0000000000000020 r10=00000000229A8068 r11=00000000000071E8
r12=00000000229C0CA0 r13=000000002572CCE0 r14=0000000025C22934 r15=0000000025C22840
------------------- End of Registers ---------------------
*** 2011-04-20 18:00:30.736
----- Current SQL Statement for this session (sql_id=0000000000000) -----
CREATE OR REPLACE VIEW olapsys.ALL$AW_DIM_ENABLED_VIEWS AS
SELECT AW.AWOWNER as AW_OWNER,
AW.AWNAME as AW_NAME,
AW.COL1 as DIMENSION_NAME,
AW.COL2 as HIERARCHY_NAME,
AW.COL3 as SYSTEM_VIEWNAME,
AW.COL4 as USER_VIEWNAME
FROM
TABLE(CAST(OLAP_TABLE('SYS.AWMD duration query',
'olapsys.ALL_OLAP2_AW_METADATA_T',
'ACTIVE_CATALOG ''ALL_AW_DIM_ENABLED_VIEWS'' ''ALL''',
'MEASURE AWOWNER FROM SYS.AWMD!AWOWNER
MEASURE AWNAME FROM SYS.AWMD!AWNAME
MEASURE COL1 FROM SYS.AWMD!DIMENSION_NAME
MEASURE COL2 FROM SYS.AWMD!HIERARCHY_NAME
MEASURE COL3 FROM SYS.AWMD!VIEWNAME
MEASURE COL4 FROM SYS.AWMD!USERVIEWNAME
DIMENSION AWMDKEY FROM SYS.AWMD!AWMDKEY')
AS olapsys.ALL_OLAP2_AW_METADATA_T)) AW
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
_intel_fast_memcpy. 0000000000000000 000000000 000000000 000000000
A()+18 000000000
00000000256E22E0 CALL??? _intel_fast_memcpy. 0FFFFFFFF 005895BBA 000000000
A()+18 000000000
00000000FFFFFFFF CALL??? 00000000256E22E0 005895BBA 000000000 000000000
025668420
Our business objec is working fine and all other schema does not have any uncompiled objects.
How can we validate the OLAPSYS and PUBLIC schema
If we leave them as it is, what can be the future repercussions
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
