Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Invalid Objects

Re: Invalid Objects

From: J Huntley Palmer <jhp_at_dontspam.spam>
Date: Tue, 09 May 2006 17:44:51 -0400
Message-ID: <12623b38uetd606@news.supernews.com>


Thanks much takesiro!

takesiro wrote:

> Probably....
> 
> 1)Shutdown and then startup migrate(?)
> 2) re-run catpatch.sql (located at $ORACLE_HOME/rdbms/admin)
> 3) re-create olap_user roles and give necessary privileges :
> 4) Assign the OLAP_USER role to any users that need to access the Oracle 
> OLAP
> catalog.
> 
> GRANT OLAP_USER to <user>;
> 
> 5) If the user requires special access to a particular select privs on the
> table (AW$...).
> 
> GRANT SELECT ON <AW$xxx> TO <user>;
> 
> regards.
> 
> 
> "J Huntley Palmer" <jhp_at_dontspam.spam> wrote in message 
> news:1261vg5q14e2d9d_at_news.supernews.com...

>> Once I add the priv to the upgrade user. How can I resolve this? Do I
>> have to rerun the catalog upgrade script?
>>
>> takesiro wrote:
>>> Please check below
>>> "The OLAP Catalog tables are owned by OLAPSYS. To create OLAP
>>> metadata in these tables, the user must have the OLAP_DBA role"
>>>
>>> Upgrade user didn't have OLAP_SYS when upgrade.
>>>
>>> Regards.
>>>
>>> "J Huntley Palmer" <jhp_at_dontspam.spam> wrote in message
>>> news:125vukqjcgqm4c4_at_news.supernews.com...
>>>> After the upgrade to 10.2.0.2 from 10.2.0.1 I was left with these
>>>> invalid objects that could not be recompiled:
>>>>
>>>>
>>>> Errors
>>>> Failed to compile: ORA-00980: synonym translation is no longer valid
>>>>
>>>> Any help appreciated.
>>>>
>>>> ALL_OLAP2_AW_CATALOGS SYNONYM INVALID
>>>> ALL_OLAP2_AW_CATALOG_MEASURES SYNONYM INVALID
>>>> ALL_OLAP2_AW_PHYS_OBJ SYNONYM INVALID
>>>> ALL_OLAP2_AW_PHYS_OBJ_PROP SYNONYM INVALID
>>>> ALL_OLAP2_AW_DIMENSIONS SYNONYM INVALID
>>>> ALL_OLAP2_AW_ATTRIBUTES SYNONYM INVALID
>>>> ALL_OLAP2_AW_CUBES SYNONYM INVALID
>>>> ALL_OLAP2_AW_CUBE_DIM_USES SYNONYM INVALID
>>>> ALL_AW_DIM_ENABLED_VIEWS SYNONYM INVALID
>>>> ALL_AW_CUBE_ENABLED_VIEWS SYNONYM INVALID
>>>> ALL_AW_CUBE_ENABLED_HIERCOMBO SYNONYM INVALID
>>>> ALL_OLAP2_AW_DIM_LEVELS SYNONYM INVALID
>>>> ALL_OLAP2_AW_DIM_HIER_LVL_ORD SYNONYM INVALID
>>>> ALL_OLAP2_AW_CUBE_MEASURES SYNONYM INVALID
>>>> ALL_OLAP2_AW_CUBE_AGG_SPECS SYNONYM INVALID
>>>> ALL_OLAP2_AW_CUBE_AGG_MEAS SYNONYM INVALID
>>>> ALL_OLAP2_AW_CUBE_AGG_LVL SYNONYM INVALID
>>>> ALL_OLAP2_AW_CUBE_AGG_OP SYNONYM INVALID
>>>> MRV_OLAP2_AW_DIMENSIONS SYNONYM INVALID
>>>> MRV_OLAP2_AW_ATTRIBUTES SYNONYM INVALID
>>>> MRV_OLAP2_AW_CUBES SYNONYM INVALID
>>>> MRV_OLAP2_AW_CUBE_MEASURES SYNONYM INVALID
>>>> OLAP_SYS_AW_ACCESS_CUBE_VIEW SYNONYM INVALID
>>>> OLAP_SYS_AW_ACCESS_DIM_VIEW SYNONYM INVALID
>>>> OLAP_SYS_AW_ENABLE_ACCESS_VIEW SYNONYM INVALID
>>>> CWM2_OLAP_OLAPAPI_ENABLE PACKAGE BODY INVALID
>>>> DBMS_AWM PACKAGE BODY INVALID
>>>> CWM2_OLAP_CUBE PACKAGE BODY
>>>

> Received on Tue May 09 2006 - 16:44:51 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US