Invalid synonyms

Hi all

This is the test case. JST downgraded my 10.2.0.5 11g database.

I have no valid synonnyms. How can I make as "VALID."

These are not achievable.

SQL > alter compilation synonym < synonym_name >;

SQL > alter compilation public synonym < synonym_name >;

SQL > @? / rdbms/admin/utlrp.sql;

SQL > select object_name, status, object_type, created from dba_objects where status = 'INVALID ';

OBJECT_NAME OBJECT_TYPE STATUS CREATED

------------------------------------------ ------- ------------------- ---------

MGMT_TARGET_BLACKOUTS 9 OCTOBER 15 INVALID SYNONYM

SETEMVIEWUSERCONTEXT 9 OCTOBER 15 INVALID SYNONYM

SYNONYM INVALID MGMT$ ALERT_CURRENT OCTOBER 9, 15

SYNONYM INVALID MGMT$ ALERT_HISTORY OCTOBER 9, 15

SYNONYM INVALID MGMT$ AVAILABILITY_CURRENT OCTOBER 9, 15

SYNONYM INVALID MGMT$ AVAILABILITY_HISTORY OCTOBER 9, 15

SYNONYM INVALID MGMT$ BLACKOUT_HISTORY OCTOBER 9, 15

SYNONYM INVALID MGMT$ CLUSTER_INTERCONNECTS 9 OCTOBER 15

SYNONYM INVALID MGMT$ CSA_CLIENTS OCTOBER 9, 15

SYNONYM INVALID MGMT$ CSA_HOST_COOKIES OCTOBER 9, 15

SYNONYM INVALID MGMT$ CSA_HOST_CPUS OCTOBER 9, 15

SYNONYM INVALID MGMT$ CSA_HOST_CUSTOM OCTOBER 9, 15

SYNONYM INVALID MGMT$ CSA_HOST_IOCARDS OCTOBER 9, 15

SYNONYM INVALID MGMT$ CSA_HOST_NICS OCTOBER 9, 15

SYNONYM INVALID MGMT$ CSA_HOST_OS_COMPONENTS OCTOBER 9, 15

SYNONYM INVALID MGMT$ CSA_HOST_OS_FILESYSTEMS OCTOBER 9, 15

SYNONYM INVALID MGMT$ CSA_HOST_OS_PROPERTIES OCTOBER 9, 15

SYNONYM INVALID MGMT$ CSA_HOST_SW OCTOBER 9, 15

SYNONYM INVALID MGMT$ DB_CONTROLFILES OCTOBER 9, 15

SYNONYM INVALID MGMT$ DB_DATAFILES OCTOBER 9, 15

SYNONYM INVALID MGMT$ DB_DBNINSTANCEINFO OCTOBER 9, 15

SYNONYM INVALID MGMT$ DB_FEATUREUSAGE OCTOBER 9, 15

SYNONYM INVALID MGMT$ DB_INIT_PARAMS OCTOBER 9, 15

SYNONYM INVALID MGMT$ DB_LICENSE OCTOBER 9, 15

SYNONYM INVALID MGMT$ DB_REDOLOGS OCTOBER 9, 15

SYNONYM INVALID MGMT$ DB_ROLLBACK_SEGS OCTOBER 9, 15

SYNONYM INVALID MGMT$ DB_SGA OCTOBER 9, 15

SYNONYM INVALID MGMT$ DB_TABLESPACES OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_COMPONENTS OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_COMPONENT_DETAILS OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_FS_MOUNT OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_HARDWARE OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_HOST_CONFIG OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_INIT OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_ONEOFF_PATCHES OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_ORACLE_HOME OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_OS_COMPONENTS OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_OS_COMP_DETAILS OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_OS_KERNEL_PARAMS OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_PATCHSETS OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_PATCHSET_DETAILS OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_VENDOR_SW OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_VIEW OCTOBER 9, 15

SYNONYM INVALID MGMT$ DELTA_VIEW_DETAILS OCTOBER 9, 15

SYNONYM INVALID MGMT$ ECM_CURRENT_SNAPSHOTS OCTOBER 9, 15

SYNONYM INVALID MGMT$ ECM_VISIBLE_SNAPSHOTS OCTOBER 9, 15

SYNONYM INVALID MGMT$ GROUP_DERIVED_MEMBERSHIPS OCTOBER 9, 15

SYNONYM INVALID MGMT$ GROUP_FLAT_MEMBERSHIPS OCTOBER 9, 15

SYNONYM INVALID MGMT$ GROUP_MEMBERS 9 OCTOBER 15

SYNONYM INVALID MGMT$ HA_BACKUP OCTOBER 9, 15

SYNONYM INVALID MGMT$ HA_FILES OCTOBER 9, 15

SYNONYM INVALID MGMT$ HA_INFO OCTOBER 9, 15

SYNONYM INVALID MGMT$ HA_INIT_PARAMS OCTOBER 9, 15

SYNONYM INVALID MGMT$ HA_MTTR OCTOBER 9, 15

SYNONYM INVALID MGMT$ HA_RMAN_CONFIG OCTOBER 9, 15

SYNONYM INVALID MGMT$ HW_NIC OCTOBER 9, 15

SYNONYM INVALID MGMT$ INTERFACE_STATS OCTOBER 9, 15

SYNONYM INVALID MGMT$ METRIC_COLLECTION OCTOBER 9, 15

SYNONYM INVALID MGMT$ METRIC_CURRENT OCTOBER 9, 15

SYNONYM INVALID MGMT$ METRIC_DAILY OCTOBER 9, 15

SYNONYM INVALID MGMT$ METRIC_DETAILS OCTOBER 9, 15

SYNONYM INVALID MGMT$ METRIC_HOURLY OCTOBER 9, 15

SYNONYM INVALID MGMT$ MISSING_TARGETS OCTOBER 9, 15

SYNONYM INVALID MGMT$ MISSING_TARGETS_IN_GROUPS OCTOBER 9, 15

SYNONYM INVALID MGMT$ OS_COMPONENTS OCTOBER 9, 15

SYNONYM INVALID MGMT$ OS_FS_MOUNT OCTOBER 9, 15

SYNONYM INVALID MGMT$ OS_HW_SUMMARY OCTOBER 9, 15

SYNONYM INVALID MGMT$ OS_KERNEL_PARAMS OCTOBER 9, 15

SYNONYM INVALID MGMT$ OS_PATCHES OCTOBER 9, 15

SYNONYM INVALID MGMT$ OS_SUMMARY OCTOBER 9, 15

SYNONYM INVALID MGMT$ RACDB_INTERCONNECTS OCTOBER 9, 15

SYNONYM INVALID MGMT$ SOFTWARE_COMPONENTS OCTOBER 9, 15

SYNONYM INVALID MGMT$ SOFTWARE_COMPONENT_ONEOFF OCTOBER 9, 15

SYNONYM INVALID MGMT$ SOFTWARE_COMP_PATCHSET OCTOBER 9, 15

SYNONYM INVALID MGMT$ SOFTWARE_DEPENDENCIES OCTOBER 9, 15

SYNONYM INVALID MGMT$ SOFTWARE_HOMES OCTOBER 9, 15

SYNONYM INVALID MGMT$ SOFTWARE_ONEOFF_PATCHES OCTOBER 9, 15

SYNONYM INVALID MGMT$ SOFTWARE_OTHERS OCTOBER 9, 15

SYNONYM INVALID MGMT$ SOFTWARE_PATCHES_IN_HOMES OCTOBER 9, 15

SYNONYM INVALID MGMT$ SOFTWARE_PATCHSETS OCTOBER 9, 15

SYNONYM 9 OCTOBER 15 MGMT$ TARGET INVALID

SYNONYM INVALID MGMT$ TARGET_COMPONENTS OCTOBER 9, 15

SYNONYM INVALID MGMT$ TARGET_COMPOSITE OCTOBER 9, 15

SYNONYM INVALID MGMT$ TARGET_PROPERTIES OCTOBER 9, 15

SYNONYM INVALID MGMT$ TARGET_TYPE 9 OCTOBER 15

SYNONYM INVALID MGMT$ E2E_1DAY OCTOBER 9, 15

SYNONYM INVALID MGMT$ E2E_HOURLY OCTOBER 9, 15

SYNONYM INVALID MGMT$ E2E_RAW OCTOBER 9, 15

SYNONYM INVALID MGMT$ TXN_PERF_RAW OCTOBER 9, 15

SYNONYM INVALID MGMT$ TXN_PERF_HOUR OCTOBER 9, 15

SYNONYM INVALID MGMT$ TXN_PERF_DAY OCTOBER 9, 15

SYNONYM INVALID MGMT$ STEPS 9 OCTOBER 15

SYNONYM INVALID MGMT$ STEP_GROUPS OCTOBER 9, 15

SYNONYM INVALID MGMT$ STEP_METRICS_RAW OCTOBER 9, 15

SYNONYM INVALID MGMT$ GRP_METRICS_RAW OCTOBER 9, 15

SYNONYM INVALID MGMT$ STEP_METRICS_HOURLY OCTOBER 9, 15

SYNONYM INVALID MGMT$ GRP_METRICS_HOURLY OCTOBER 9, 15

SYNONYM INVALID MGMT$ STEP_METRICS_DAILY OCTOBER 9, 15

SYNONYM INVALID MGMT$ GRP_METRICS_DAILY OCTOBER 9, 15

MGMT_VIEW_UTIL 9 OCTOBER 15 INVALID SYNONYM

MGMT_MESSAGES 9 OCTOBER 15 INVALID SYNONYM

MGMT_PAF_PROCS_LATEST 9 OCTOBER 15 INVALID SYNONYM

MGMT_PAF_JOBS 9 OCTOBER 15 INVALID SYNONYM

THE PROCEEDINGS INVALID SYNONYM $ MGMT_PAF OCTOBER 9, 15

MGMT_PAF INVALID SYNONYM $ INSTANCES 9 OCTOBER 15

SYNONYM INVALID MGMT_PAF$ STATES 9 OCTOBER 15

MGMT_PAF INVALID SYNONYM $ APPLICATIONS OCTOBER 9, 15

SYNONYM INVALID MGMT$ ECM_CONFIG_HISTORY OCTOBER 9, 15

SYNONYM INVALID MGMT$ ECM_CONFIG_HISTORY_KEY1 OCTOBER 9, 15

SYNONYM INVALID MGMT$ ECM_CONFIG_HISTORY_KEY2 OCTOBER 9, 15

SYNONYM INVALID MGMT$ ECM_CONFIG_HISTORY_KEY3 OCTOBER 9, 15

SYNONYM INVALID MGMT$ ECM_CONFIG_HISTORY_KEY4 OCTOBER 9, 15

SYNONYM INVALID MGMT$ ECM_CONFIG_HISTORY_KEY5 OCTOBER 9, 15

SYNONYM INVALID MGMT$ ECM_CONFIG_HISTORY_KEY6 OCTOBER 9, 15

MGMT_IP_TGT_GUID_ARRAY 9 OCTOBER 15 INVALID SYNONYM

115 selected lines.

DB: 10.2.0.5 on redhat

Synonyms are pointing to an object.

Dba_synonyms list of their names, and what schema and object, point out.

If these objects no longer exists, they will become invalid.

The fall of an object does NOT drop their synonyms.

Check if there are objects and solve this problem.

----------------

Sybrand Bakker

Senior Oracle DBA

Tags: Database

Similar Questions

ORA-00980 invalid synonym

Oracle 11.2.0.4.0
Talk to a mysql on heterogenuous services database called db and synonym error invalid link. but only in a procedure
Database1: select * from t1@mysql_link--cela works
Database1: create synonym user1.vw1 for t1@mysql_link
Database1:
base2: schema user2 has a db_link private linking as User1 to database1
base2: conn user2
base2: select * from vw1@database1--cela works
base2: but put that select statement in a procedure and it fails
User2@Database2 > select *.
2 of user1.vw1@database1
col1
------------------------
27432
Elapsed time: 00:00:05.84
User2@Database2: > declare
2 v_cnt number;
3. start
4 Select
5 in v_cnt
user1.vw1@database1 6
7 dbms_output.put_line (v_cnt);
8 end;
9.
Select *.
*
ERROR on line 4:
ORA-06550: line 4, column 11:
PL/SQL: ORA-00980: synonym translation is no longer valid
ORA-06550: line 4, column 11:
PL/SQL: SQL statement ignored

You get the same error message when you use a different Oracle database instead of the MySQL database and a basic link of database gateway. The root cause of the error message is a documented restriction: ORA-00980 when PL/SQL block uses the synonym of synonym to Table through Dblinks (Doc ID 453754.1) that happens because PL/SQL cannot load database Central (databas1) follow the link of data during the compilation phase.

-Klaus

Compile the invalid objects in ADADMIN

Hi all
EBS R12.2
RHEL 6.6
How to compile database objects invalid (synonymously, stored procedures, views, etc.) using ADADMIN?
I tried the following, but it ends immediately and seems not to check all database objects?
Thank you very much
MK

Hello

You use the script "utlrp.sql" of RDBMS $ORACLE_HOME/rdbms/admin.

Thank you

A H E E R X

Do I have to reapply for grants and synonyms. Edit rename them to another scheme
Hello

We follow the process to replace some tables in UAT/PROD with the new table structure.

Thus, for example, A table in a schema:

Step 1 - create a TableA_NEW with the necessary structure and walls.
Step 2-Insert into TableA_NEW select * from TableA.
Step 3-Alter Table TableA rename TableA_OLD - take backup from TableA
Step 4 - Alter Table TableA_NEW and rename the TableA - change the new ti from table Table of origin

Now should I reapply all grants and synonyms initially applied to TableA.
When I test in Dev, all grants and synonyms still stands. But I can't take any chances for UAT/PROD.

Also when I restore these changes and rename the tables back to the original table.
So should I reapply all grants and synonyms initially applied to TableA.

Please suggest...
user8941550 wrote:
Hello

We follow the process to replace some tables in UAT/PROD with the new table structure.

Thus, for example, A table in a schema:

Step 1 - create a TableA_NEW with the necessary structure and walls.
Step 2-Insert into TableA_NEW select * from TableA.
Step 3-Alter Table TableA rename TableA_OLD - take backup from TableA
Step 4 - Alter Table TableA_NEW and rename the TableA - change the new ti from table Table of origin

Now should I reapply all grants and synonyms initially applied to TableA.
When I test in Dev, all grants and synonyms still stands. But I can't take any chances for UAT/PROD.

Also when I restore these changes and rename the tables back to the original table.
So should I reapply all grants and synonyms initially applied to TableA.

Please suggest...

Step 1 - create a TableA_NEW with the necessary structure and walls. New table - has no subsidies
Step 2-Insert into TableA_NEW select * from TableA.
Step 3 - Alter Table TableA and rename TableA_OLD - take backup of TableA Renamed table maintains subsidies. At this point invalid synonym
Step 4 - Alter Table TableA_NEW and rename the TableA - changing new technology table original Table new table still has no subsidies, valid synonym now

Thus, subsidies disappear, but means will be valid at the end of the process.

Invalidation of the object
I have a synonym to which I applied the policy, when I apply it, it makes the PLSQL according to the same invalid synonym.
Why all these PLSQL objects become invalid?
Change/add/remove a policy on a synonym is updating the cache line and library cache entries corresponding to the synonym and it invalidates all dependent objects on the synonym. If the chain of dependence is not very deep, the problem can be ignored, the access depending on whether dependent objects are validated in a transparent manner.
To avoid this problem, you can apply policy directly on the base table.

Concerning
INAM Bukhari
http://dbmentors.blogspot.com

Invalid PUBLIC objects in the database

Hello

I have a 11.1.0.7.10 database running on one machine Linux EL5.

OWNER           OBJECT_NAME                    OBJECT_TYPE
--------------- ------------------------------ --------------------
SYS             INTERACTIONEXECUTE             FUNCTION
SYS             XOQ_VALIDATE                   PROCEDURE
PUBLIC          ALL_AW_LOAD_DIMENSIONS         SYNONYM
PUBLIC          ALL_AW_LOAD_DIM_FILTERS        SYNONYM
PUBLIC          ALL_AW_LOAD_CUBE_FILTERS       SYNONYM
PUBLIC          ALL_AW_LOAD_CUBE_MEASURES      SYNONYM
PUBLIC          ALL_AW_LOAD_DIM_PARMS          SYNONYM
PUBLIC          ALL_AW_LOAD_CUBE_DIMS          SYNONYM
PUBLIC          ALL_AW_LOAD_CUBES              SYNONYM
PUBLIC          ALL_AW_LOAD_CUBE_PARMS         SYNONYM
PUBLIC          ALL_LOAD_CUBE_SEGWIDTH         SYNONYM
PUBLIC          ALL_AW_CUBE_AGG_PLANS          SYNONYM
PUBLIC          ALL_AW_CUBE_AGG_MEASURES       SYNONYM
PUBLIC          ALL_AW_CUBE_AGG_LEVELS         SYNONYM
PUBLIC          ALL_AW_DIM_ENABLED_VIEWS       SYNONYM
PUBLIC          ALL_AW_CUBE_ENABLED_VIEWS      SYNONYM
PUBLIC          ALL_AW_CUBE_ENABLED_HIERCOMBO  SYNONYM
PUBLIC          DBMS_AWM                       SYNONYM

SQL> alter public synonym ALL_AW_LOAD_DIMENSIONS compile;
alter public synonym ALL_AW_LOAD_DIMENSIONS compile
*
ERROR at line 1:
ORA-00980: synonym translation is no longer valid

When I try to compile the synonyms, I get the above error. Could someone help me please here as to what needs to be done to get these fixed invalid synonyms?

Published by: 877343 on 5 March 2012 02:13

Its look like someone has voluntarily withdrawn your database OLAp option, but forgot to remove its synonyms :|

See the following note in MOS:
Remove invalid OLAP of SYS and [ID 565773.1] OLAPSYS schema objects

He explains after removing the OLAP option, you must remove all of its related synonyms. Look at step 3) this note:

3. All the objects listed in step 2 can be deleted, since they are used exclusively by the OLAP option.

To make this easier, use the following SQL script to determine all PUBLIC synonyms referring to objects in the OLAPSYS schema:
This will generate a script that drops the listed objects from the database.

SQL>spool olapdrop.sql
SQL> select 'drop public synonym ' || synonym_name || ';'
       from dba_synonyms
       where owner='PUBLIC' and table_owner='OLAPSYS';
SQL>spool off

Upgrade 10g (10.2.0.5) 9i (9.2.0.6) EBS database on Linux

Hello
I'm upgrading database EBS (11.5.10.2) 9i (9.2.0.6) to 10g (10.2.0.5) NON-RAC.
After the upgrade of the database to 10g, I found...
Status of the component Version hh
Server database Oracle VALID 10.2.0.5.0 00:44:35
JServer JAVA Virtual Machine VALID 10.2.0.5.0 00:06:40
Oracle XDK VALID 10.2.0.5.0 00:05:35
Oracle database Java packages VALID 10.2.0.5.0 00:00:20
Oracle Text VALID 10.2.0.5.0 00:01:31
The database Oracle XML VALID 10.2.0.5.0 00:01:32
Oracle Real Application Clusters INVALID 10.2.0.5.0 00:00:01
Oracle Data Mining VALID 10.2.0.5.0 00:00:25
OLAP Analytic Workspace VALIDATES 10.2.0.5.0 00:00:23
OLAP catalog VALID 10.2.0.5.0 00:01:25
Oracle OLAP API VALID 10.2.0.5.0 00:00:48
Oracle interMedia 10.2.0.5.0 VALID 00:04:45
10.2.0.5.0 INVALID space 00:03:42
So I ran utlrp.sql, INVALID objects here 235, what do I do now? I can leave it like that?
No error in catupgrd.log.
Thank you.
FYI...
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
APPS EDW_MRP_FORECAST_M_C INVALID BODY PACKAGE
APPS EDW_MRP_DM_CLS_M_C INVALID BODY PACKAGE
APPS EDW_HR_SERVICE_M_C INVALID BODY PACKAGE
APPS EDW_HR_RQN_VCNCY_M_C INVALID BODY PACKAGE
APPS EDW_HR_REC_ACT_M_C INVALID BODY PACKAGE
APPS EDW_HR_REASON_M_C INVALID BODY PACKAGE
APPS EDW_HR_PRSN_TYP_M_C INVALID BODY PACKAGE
APPS EDW_HR_POSITION_M_C INVALID BODY PACKAGE
APPS EDW_HR_MVMNT_TYP_M_C INVALID BODY PACKAGE
APPS EDW_HR_JOBS_M_C INVALID BODY PACKAGE
APPS EDW_HR_GRADE_M_C INVALID BODY PACKAGE
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
APPS EDW_HR_ASSGNMNT_M_C INVALID BODY PACKAGE
APPS EDW_HR_ASG_CHNG_M_C INVALID BODY PACKAGE
APPS EDW_HR_AGE_BAND_M_C INVALID BODY PACKAGE
APPS EDW_GEOGRAPHY_M_C INVALID BODY PACKAGE
APPS CS_WF_ACTIVITIES_PKG INVALID BODY PACKAGE
PJI_FP_ORGO_ET_WT_F_MV APPS MATERIALIZED VIEW INVALID
PJI_FP_ORGO_F_MV APPS MATERIALIZED VIEW INVALID
BIL_BI_FST_PG_MV APPS MATERIALIZED VIEW INVALID
BIL_BI_OP21_G_MV APPS MATERIALIZED VIEW INVALID
ENI_DBI_PRC_SUM1_MV APPS MATERIALIZED VIEW INVALID
BIL_BI_OP12_PG_MV APPS MATERIALIZED VIEW INVALID
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
BIL_BI_FST_G_MV APPS MATERIALIZED VIEW INVALID
BIL_BI_OPLDC_G_MV APPS MATERIALIZED VIEW INVALID
BIM_I_MKT_FCT_MV APPS MATERIALIZED VIEW INVALID
BIL_BI_OPLPC_G_MV APPS MATERIALIZED VIEW INVALID
ENI_RES_3_MV APPS MATERIALIZED VIEW INVALID
POA_BM_ITEM_S_MV APPS MATERIALIZED VIEW INVALID
POA_IDL_BS_MV APPS MATERIALIZED VIEW INVALID
POA_POD_BS_MV APPS MATERIALIZED VIEW INVALID
POA_MID_BS_MV APPS MATERIALIZED VIEW INVALID
POA_RTX_BS_MV APPS MATERIALIZED VIEW INVALID
FII_AP_LIA_KPI_MV APPS MATERIALIZED VIEW INVALID
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
BIM_I_CPB_CHNL_MV APPS MATERIALIZED VIEW INVALID
BIM_I_CPB_METS_MV APPS MATERIALIZED VIEW INVALID
BIM_MKT_LD_CCAT_MV APPS MATERIALIZED VIEW INVALID
BIM_MKT_LD_CHNL_MV APPS MATERIALIZED VIEW INVALID
BIM_MKT_LD_QUAL_MV APPS MATERIALIZED VIEW INVALID
BIM_I_CPB_REGN_MV APPS MATERIALIZED VIEW INVALID
BIM_MKT_CHNL_MV APPS MATERIALIZED VIEW INVALID
BIM_MKT_KPI_CNT_MV APPS MATERIALIZED VIEW INVALID
BIM_MKT_LD_SRC_MV APPS MATERIALIZED VIEW INVALID
BIM_MKT_REGN_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_033_MV APPS MATERIALIZED VIEW INVALID
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
OKI_SRM_035_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_031_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_032_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_034_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_038_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_036_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_039_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_037_MV APPS MATERIALIZED VIEW INVALID
ENI_RES_5_MV APPS MATERIALIZED VIEW INVALID
ENI_RES_2_MV APPS MATERIALIZED VIEW INVALID
APPS OPI_EDW_UOM_CONV_F_C INVALID BODY PACKAGE
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
APPS OPI_EDW_OPM_JOB_RSRC_F_C INVALID BODY PACKAGE
APPS OPI_EDW_OPM_JOB_DETAIL_F_C INVALID BODY PACKAGE
APPS OPI_EDW_OPMINV_DAILY_STAT_F_C INVALID BODY PACKAGE
APPS OPI_EDW_OPMCOGS_F_C INVALID BODY PACKAGE
APPS OPI_EDW_COGS_F_C INVALID BODY PACKAGE
APPS ISC_EDW_BOOK_SUM1_F_C INVALID BODY PACKAGE
APPS HR_EDW_WRK_CMPSTN_F_C INVALID BODY PACKAGE
APPS FII_PA_UOM_CONV_F_C INVALID BODY PACKAGE
APPS FII_PA_REVENUE_F_C INVALID BODY PACKAGE
APPS FII_PA_COST_F_C INVALID BODY PACKAGE
APPS FII_PA_BUDGET_F_C INVALID BODY PACKAGE
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
APPS FII_AR_TRX_DIST_F_C INVALID BODY PACKAGE
APPS FII_AR_E_REVENUE_F_C INVALID BODY PACKAGE
APPS FII_AP_SCH_PAYMTS_F_C INVALID BODY PACKAGE
APPS FII_AP_INV_PAYMTS_F_C INVALID BODY PACKAGE
APPS FII_AP_INV_ON_HOLD_F_C INVALID BODY PACKAGE
APPS FII_AP_INV_LINES_F_C INVALID BODY PACKAGE
APPS FII_AP_HOLD_DATA_F_C INVALID BODY PACKAGE
APPS EDW_POA_SPLRITEM_M_C INVALID BODY PACKAGE
APPS EDW_POA_LN_TYPE_M_C INVALID BODY PACKAGE
APPS EDW_ORGANIZATION_M_C INVALID BODY PACKAGE
APPS EDW_OPI_PRDL_M_C INVALID BODY PACKAGE
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
APPS EDW_OPI_OPRN_M_C INVALID BODY PACKAGE
APPS EDW_OPI_LOT_M_C INVALID BODY PACKAGE
APPS EDW_OPI_ACTV_M_C INVALID BODY PACKAGE
APPS EDW_MTL_INVENTORY_LOC_M_C INVALID BODY PACKAGE
APPS EDW_MRP_PLAN_M_C INVALID BODY PACKAGE
BIM_I_LD_REGN_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LP_GEN_SG_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LP_QUAL_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LP_SRC_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LP_REGN_MV APPS MATERIALIZED VIEW INVALID
BIM_OBJ_LD_QUAL_MV APPS MATERIALIZED VIEW INVALID
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
OKI_RS_GROUP_MV APPS MATERIALIZED VIEW INVALID
BIV_ACT_H_SUM_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LD_BASE_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LP_BASE_MV APPS MATERIALIZED VIEW INVALID
ENI_DBI_CO_ALL_MV APPS MATERIALIZED VIEW INVALID
HRI_DBI_SAL_SUPJOB_MV APPS MATERIALIZED VIEW INVALID
HRI_DBI_SAL_CTR_MV APPS MATERIALIZED VIEW INVALID
HRI_DBI_WMV_CIT_MV APPS MATERIALIZED VIEW INVALID
HRI_DBI_SAL_CIT_MV APPS MATERIALIZED VIEW INVALID
HRI_DBI_WMV_SUPJOB_MV APPS MATERIALIZED VIEW INVALID
HRI_DBI_WMV_CTR_MV APPS MATERIALIZED VIEW INVALID
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
BIM_I_LD_CHNL_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LD_CCAT_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LD_QUAL_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LD_GEN_SG_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LP_CCAT_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LD_SRC_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LP_CHNL_MV APPS MATERIALIZED VIEW INVALID
HRI_DBI_WMV_COUNT_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LD_AGE_QU_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LD_AGE_SG_MV APPS MATERIALIZED VIEW INVALID
BIM_I_LD_GENSG_T_MV APPS MATERIALIZED VIEW INVALID
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
IBE_BI_TOP_CUST_MV APPS MATERIALIZED VIEW INVALID
FII_AP_INV_B_MV APPS MATERIALIZED VIEW INVALID
IBE_BI_TOP_PROD_MV APPS MATERIALIZED VIEW INVALID
ISC_DBI_SCR_002_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_022_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_024_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_021_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_026_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_027_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_023_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_011_MV APPS MATERIALIZED VIEW INVALID
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
OKI_SRM_012_MV APPS MATERIALIZED VIEW INVALID
ISC_DBI_PM_0003_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_013_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_018_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_040_MV APPS MATERIALIZED VIEW INVALID
POA_PQC_BS_MV APPS MATERIALIZED VIEW INVALID
OPI_PGM_SUM_MV APPS MATERIALIZED VIEW INVALID
BIM_MKT_KPI_F_MV APPS MATERIALIZED VIEW INVALID
BIM_I_MKT_CPB_MV APPS MATERIALIZED VIEW INVALID
ENI_DBI_PRC_SUM2_MV APPS MATERIALIZED VIEW INVALID
BIL_BI_OP22_G_MV APPS MATERIALIZED VIEW INVALID
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
BIL_BI_OPLPC_GC_MV APPS MATERIALIZED VIEW INVALID
BIL_BI_OPLDC_GC_MV APPS MATERIALIZED VIEW INVALID
BIM_I_OBJ_METR_MV APPS MATERIALIZED VIEW INVALID
FII_AP_HHIST_I_MV APPS MATERIALIZED VIEW INVALID
FII_AP_HCAT_I_MV APPS MATERIALIZED VIEW INVALID
FII_GL_MGMT_PRD_MV APPS MATERIALIZED VIEW INVALID
FII_AP_IVATY_XB_MV APPS MATERIALIZED VIEW INVALID
FII_GL_MGMT_CCC_MV APPS MATERIALIZED VIEW INVALID
FII_AP_MGT_KPI_MV APPS MATERIALIZED VIEW INVALID
OKI_SRM_002_MV APPS MATERIALIZED VIEW INVALID
OPI_SCRAP_SUM_MV APPS MATERIALIZED VIEW INVALID
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
OPI_PTP_SUM_F_MV APPS MATERIALIZED VIEW INVALID
OPI_PGM_GRP_MV APPS MATERIALIZED VIEW INVALID
POA_PQC_BS_J2_MV APPS MATERIALIZED VIEW INVALID
BIX BIX_DM_GROUP_SUM_MTH_MV MATERIALIZED VIEW INVALID
BIX BIX_DM_AGENT_SUM4_MV MATERIALIZED VIEW INVALID
EDWREP OWB_LOCK INVALID BODY PACKAGE
PTG MYGEOCODER INVALID FUNCTION
EUL PUBLIC $FUNCTION_ARGUMENTS INVALID SYNONYM
EUL PUBLIC $FONCTIONS INVALID SYNONYM
EUL PUBLIC $EXPRESSION_DEPENDENCIES INVALID SYNONYM
EUL PUBLIC $EXPRESSIONS INVALID SYNONYM
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
EUL PUBLIC $EUL_USERS INVALID SYNONYM
EUL PUBLIC $DOMAIN_VALUES INVALID SYNONYM
EUL PUBLIC $DOMAINES INVALID SYNONYM
EUL PUBLIC $DATE_HIERARCHY_NODES INVALID SYNONYM
EUL PUBLIC $BA_BA_LINKS INVALID SYNONYM
EUL PUBLIC $JC_JOIN_LINKS INVALID SYNONYM
EUL PUBLIC $IG_EXP_LINKS INVALID SYNONYM
EUL PUBLIC $ID_SEQ INVALID SYNONYM
EUL PUBLIC $HIERARCHY_SEGMENTS INVALID SYNONYM
EUL PUBLIC $HIERARCHY_NODES INVALID SYNONYM
EUL PUBLIC $HIÉRARCHIES INVALID SYNONYM
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
EUL PUBLIC $GET_FOLDER_NAME INVALID SYNONYM
EUL PUBLIC $FUN_FC_LINKS INVALID SYNONYM
EUL PUBLIC $FUNCTION_CATEGORIES INVALID SYNONYM
EUL PUBLIC $VERSIONS INVALID SYNONYM
EUL PUBLIC $VBH_IT_LINKS INVALID SYNONYM
EUL PUBLIC $SUMMARY_TABLE_DEFINITIONS INVALID SYNONYM
EUL PUBLIC $SUMMARY_REFRESH_SETS INVALID SYNONYM
EUL PUBLIC $SUMMARY_REFRESH_INTERVALS INVALID SYNONYM
EUL PUBLIC $SUMMARY_OBJECTS INVALID SYNONYM
EUL PUBLIC $SUMMARY_ITEM_USAGES INVALID SYNONYM
EUL PUBLIC $SUMMARY_ELEMENT_EXCLUSIONS INVALID SYNONYM
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
EUL PUBLIC $SUMMARY_DESIGN_ELEMENTS INVALID SYNONYM
EUL PUBLIC $SUMMARY_BITMAPS INVALID SYNONYM
EUL PUBLIC $SUB_QUERY_CORRELATIONS INVALID SYNONYM
EUL PUBLIC $SUB_QUERIES INVALID SYNONYM
EUL PUBLIC $QPP_STATISTICS INVALID SYNONYM
EUL PUBLIC $QPP_ITEM_STATISTICS INVALID SYNONYM
EUL PUBLIC $PLAN_TABLE INVALID SYNONYM
EUL PUBLIC $OG_OBJ_LINKS INVALID SYNONYM
EUL PUBLIC $OBJS INVALID SYNONYM
EUL PUBLIC $OBJECT_SQL_SEGMENTS INVALID SYNONYM
EUL PUBLIC $OBJECT_JOIN_USAGES INVALID SYNONYM
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
EUL PUBLIC $OBJECT_GROUPS INVALID SYNONYM
EUL PUBLIC $OBJECT_DEPENDENCIES INVALID SYNONYM
EUL PUBLIC $NMSDO_JC_USAGES INVALID SYNONYM
EUL PUBLIC $KEY_CONSTRAINTS INVALID SYNONYM
EUL PUBLIC $JOIN_COMBINATIONS INVALID SYNONYM
EUL PUBLIC $APPLICATION_PARAMETERS INVALID SYNONYM
EUL PUBLIC $ACCESS_PRIVILEGES INVALID SYNONYM
INVALID DISCOVERER_GRANTS PUBLIC SYNONYM
INVALID DISCOVERER_DOCS PUBLIC SYNONYM
INVALID DISCOVERER_ALL_DOCS PUBLIC SYNONYM
DISCOVERER_SEQ PUBLIC SYNONYM INVALID
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
CIF_USER_ROLES_V PUBLIC SYNONYM INVALID
CIF_USERS_V PUBLIC SYNONYM INVALID
CIF_SUBSCRIBERS_V PUBLIC SYNONYM INVALID
CIF_SOURCE_V PUBLIC SYNONYM INVALID
CIF_SEED_LISTS_V PUBLIC SYNONYM INVALID
CIF_SECURITY PUBLIC SYNONYM INVALID
CIF_QUERY_BOOKS_V PUBLIC SYNONYM INVALID
CIF_PROM_OFFER_PRODUCTS_V PUBLIC SYNONYM INVALID
CIF_PROM_OFFERS_V PUBLIC SYNONYM INVALID
CIF_PROMOTIONS_V PUBLIC SYNONYM INVALID
CIF_PROMOTION PUBLIC SYNONYM INVALID
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
CIF_PROFILE PUBLIC SYNONYM INVALID
CIF_PRODUCTS_V PUBLIC SYNONYM INVALID
CIF_PRICELISTS_V PUBLIC SYNONYM INVALID
CIF_ORGANIZATIONS_V PUBLIC SYNONYM INVALID
CIF_MTL_SYSTEM_ITEMS_V PUBLIC SYNONYM INVALID
CIF_MESSAGE PUBLIC SYNONYM INVALID
CIF_MARKET_SEGMENTS_V PUBLIC SYNONYM INVALID
CIF_FND_USER PUBLIC SYNONYM INVALID
CIF_FND_RESPONSIBILITY PUBLIC SYNONYM INVALID
CIF_FND_PROFILE PUBLIC SYNONYM INVALID
CIF_FND_GLOBAL PUBLIC SYNONYM INVALID
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
CIF_FND_CLIENT_INFO PUBLIC SYNONYM INVALID
CIF_CUSTOMERS_V PUBLIC SYNONYM INVALID
CIF_CONTACTS_V PUBLIC SYNONYM INVALID
CIF_COLLATERAL_MGR PUBLIC SYNONYM INVALID
CIF_ACCOUNTS_V PUBLIC SYNONYM INVALID
DEBUG_CARTX PUBLIC SYNONYM INVALID
SENDMESSAGE PUBLIC SYNONYM INVALID
LAUNCH_PORTAL PUBLIC SYNONYM INVALID
LOGOFF_PORTAL PUBLIC SYNONYM INVALID
ISUPPORT_API PUBLIC SYNONYM INVALID
PORTAL_TAB_API PUBLIC SYNONYM INVALID
STATUS OF TYPE OBJECT OWNER
--------------- -------------------------------------------------- ------------------ ----------
EMAIL_TO_RESOLUTION PUBLIC SYNONYM INVALID
PORTAL_CONTENT PUBLIC SYNONYM INVALID
DEFCALL VIEW INVALID SYSTEM
MYGEOCODER INVALID FUNCTION WIRELESS
235 selected lines.

The status of 'INVALID' for the "Oracle Real Application Clusters" component is normal if you have not set up a RAC.

For objects not valid EDW, please make sure that you implement the step "Recreate custom database links (conditional)", in (Doc ID 362203.1)

For the rest of the invalid objects, see:

How to validate IFI packages not valid? (Doc ID 1108214.1)

Invalid objects for Modules EDW and IFI (Doc ID 412032.1)

Large number of non-materialized views valid after Migration from 32-bit to 64-bit (Doc ID 1423709.1)

11i: "ORA-00995: synonymous with missing or invalid identifier" error during recompiling invalid synonyms after Database Upgrade (Doc ID 380480.1)

Thank you

Hussein

Synonyms for invalid public Oracle XE

Hello

I wondered why these public synonyms will always invalid in my Oracle XE?

SQL> select object_name from dba_objects where status != 'VALID';

OBJECT_NAME
--------------------------------------------------------------------------------
DBA_HIST_FILESTATXS
DBA_HIST_SQLSTAT
DBA_HIST_SQLBIND
DBA_HIST_SYSTEM_EVENT
DBA_HIST_WAITSTAT
DBA_HIST_LATCH
DBA_HIST_LATCH_MISSES_SUMMARY
DBA_HIST_DB_CACHE_ADVICE
DBA_HIST_ROWCACHE_SUMMARY
DBA_HIST_SGASTAT
DBA_HIST_SYSSTAT

OBJECT_NAME
--------------------------------------------------------------------------------
DBA_HIST_SYS_TIME_MODEL
DBA_HIST_OSSTAT
DBA_HIST_PARAMETER
DBA_HIST_SEG_STAT
DBA_HIST_ACTIVE_SESS_HISTORY
DBA_HIST_TABLESPACE_STAT
DBA_HIST_SERVICE_STAT
DBA_HIST_SERVICE_WAIT_CLASS

20 rows selected.

I installed XE on Ubuntu 9.04. I have changed default installation is that I put to level Apex 3.2 and archiving on the value.

BR, Jari

Please see BUG 3603160

ORA-00980: synonym translation is no longer valid

I have a two databases. CARRIER_DEV and TRANSPORT_DEV. Everything works fine in Oracle 11 g, but when we migrated to Oracle12c, INFO_FUNC (service Oracle) residing in CARRIER_DEV under carrier scheme is called TRANSPORT_DEV, throwing the ORA-01775: synonym of closure chain. which caused ~ 9 invalid objects.
SELECT INFO_FUNC('1','NAME') FROM DUAL; This has been called TRANSPORT_DEV.
The DB of TRANSPORT_DEV to CARRIER_DEV link has been created to help
CREATE THE DATABASE LINK RCAR PUBLIC
CONNECT TO CARRIER_USR
IDENTIFIED BY < PWD >
With the HELP of ' Carrier_dev. WORLD ';

We have created the synonym and gave the CARRIER_DEV necessary.

CREATE THE INFO_FUNC FOR CARRIER.INFO_FUNC PUBLIC SYNONYM;
GRANT EXECUTE ON CARRIER.INFO_FUNC TO CARRIER_USR;

Transport_dev database,

I created the following synonym to access the CARRIER.INFO_FUNC

CREATE THE INFO_FUNC PUBLIC SYNONYM FOR "PUBLIC".INFO_FUNC@RCAR;

After analysis of the issue, I found that the public synonym in Transport_dev uses 'PUBLIC' as a schema instead of CARRIER name. (It works fine in Oracle 11 g. Explain what is 'PUBLIC' means here).

So I decided to use the name of schema instead of 'PUBLIC '.

CREATE THE INFO_FUNC FOR CARRIER.INFO_FUNC@RCAR PUBLIC SYNONYM;

After this change, all invalid objects went into Oracle 12 c, but a new problem came.

SELECT INFO_FUNC('1','NAME') FROM DUAL; This SQL sataement now gives ORA-00980: synonym translation is no longer valid

SELECT INFO_FUNC@RCAR('1','NAME') FROM DUAL; also gives the same error.

CARRIER_DEV the database

CREATE TABLE CARRIER. CARRIER_NAME
(
NAME_SEQ_NO NUMBER OF NON-NULL,
LNAME VARCHAR2 (50 BYTE),
FNAME VARCHAR2 (20 BYTE),
MNAME VARCHAR2 (20 BYTE),
VARCHAR2 (10 BYTE) SUFFIX
);
CREATE OR REPLACE FUNCTION CARRIER. "" INFO_FUNC "(pin_in VARCHAR2, field_in VARCHAR2: = 'TEST')
RETURN VARCHAR2
IS
tmpVar VARCHAR2 (100);
BEGIN

SELECT lname | ',' | fname | » '|| mname | » '|| suffix
IN tmpVar
OF Carrier_Name
WHERE name_seq_no = pin_in;

END INFO_FUNC;
/
CREATE THE INFO_FUNC FOR CARRIER.INFO_FUNC PUBLIC SYNONYM;
GRANT EXECUTE ON CARRIER.INFO_FUNC TO CARRIER_USR;

In TRANSPORT_DEV

CREATE THE INFO_FUNC FOR CARRIER.INFO_FUNC@RCAR PUBLIC SYNONYM;
Please guide me.

I've recreated the DBLink from TRANSPORT_DEV to CARRIER_DEV. The problem disappeared. Thank you for your help
1. Re-create the synonym.
2. Recreate the DBLink

Public synonyms in a pluggable database deletion

I have a base Oracle container 12 c with pluggable databases in it. In a pluggable data bases, I uninstalled OLAP by running the following scripts:
SQL > @%oracle_home%/olap/admin/catnoamd.sql
SQL > @ /olap/admin/olapidrp.plb% oracle_home %
SQL > @ /olap/admin/catnoxoq.sql% oracle_home %
SQL > @ /olap/admin/catnoaps.sql% oracle_home %
After you run the scripts, I then generated SQL statements to remove invalid OLAP synonyms, by executing the following:
Select ' drop public synonym ' | object_name | ';'
from dba_objects
where <>of status "VALID."
and owner = 'PUBLIC '.
and object_type = 'SYNONYM '.
and object_name like '% OLAP % ';
When I run the SQL statements resulting in the snap-in data base, I get the following error for each of them:
ERROR on line 1:
ORA-65040: operation not allowed a pluggable database
If I switch back to the ROOT of PEH container $ and executes the same statements, I get the following error:
ERROR on line 1:
ORA-01432: due public synonym being abandoned does not exist
How can I remove these invalid public synonyms for my snap-in database?

I think you're right. I re-read the note that I mentioned above. Even uninstalling an option is not supported for a CBD so far. Only option is to disable it. Second option is to create a non - CBD, uninstall option is not required and then plug it into a CBD.

Salman

----------

http://salmandba.blogspot.com

ORA-01937 missing or invalid role name

Hi there, I had a little problem with a small piece of code am familiar with Oracle database, scripts I have been done by another person for the version 6/7 is currently using version 8i for reasons of compatibley with the server software, I am currently setting up.
use the script generates the following error message
Enter the value of old 1: 1: CREATE ROLE & 1._role
new 1:
CREATE ROLE GRANT CONNECT to & 1._role; _role CREATE ROLE GRANT CONNECT to & 1._role; _role
*
ERROR on line 1:
ORA-01937: missing or not a valid role name
Enter the value of old 1: 1: GRANT RESOURCE TO & 1._role
new 1: GRANT RESOURCE to GRANT permission TO & 1._role; _role
RESOURCE of GRANT OF GRANT permission to & 1._role; _role
*
ERROR on line 1:
ORA-00911: invalid character
Enter the value of old 1: 1: GRANT IMP_FULL_DATABASE TO & 1._role
new 1: GIVE the IMP_FULL_DATABASE TO GRANT CREATE ANY SYNONYM OF & 1._role; _role
GRANT IMP_FULL_DATABASE to GRANT CREATE ANY SYNONYM OF & 1._role; _role
*
ERROR on line 1:
ORA-00911: invalid character
Enter the value of old 1: 1: GRANT DROP ANY SYNONYM to & 1._role
new 1: GRANT DROP ALL SYNONYM of _role
GRANT DELETE ANY SYNONYM OF _role
*
ERROR on line 1:
ORA-00911: invalid character
Enter the value 1: enter the value of 2: 1 old: CREATE USER, IDENTIFIED BY 1 & 2
new 1: CREATE a USER IDENTIFIED BY GRANT & 1._role to & 1.
CREATE the USER IDENTIFIED BY GRANT & 1._role to & 1.
*
ERROR on line 1:
ORA-01935: lack of user name or role
Here is the code used
USE of REM: @ous < username > < PASSWORD >
REM create a < username > identified by < PASSWORD >
CREATE a ROLE & 1._role;
GRANT CONNECT to & 1._role;
GRANT RESOURCE to & 1._role;
GRANT permission to & 1._role;
GRANT IMP_FULL_DATABASE to & 1._role;
GRANT CREATE ANY SYNONYM OF & 1._role;
GRANT DROP ANY SYNONYM OF & 1._role;
CREATE a USER & 1 IDENTIFIED BY & 2
QUOTA UNLIMITED ON gam_lgtab
QUOTA UNLIMITED ON gam_bintab
QUOTA UNLIMITED ON gam_tab
QUOTA UNLIMITED ON gam_ind
TEMPORARY TABLESPACE temp;
GRANT & 1._role to & 1.
can someone help me to solve this thanks, that a working example would be due to my lack of knowledge with this database system.
Thank you very much

Hello

How do you call this script?

According to the commentary at the beginning of the script, this is:

USE of REM: @ous

you're supposed to give 2 arguments after the name of the script (which, apparently, is UO). The first argument is a user name; so it should follow the rules for user names (for example it must start with a letter and only contain letters, numbers, or a couple of other characters, such as the features of underscore allowed). The second argument is the password. So if you want to create a user called FOO and give him the password to BAR987, then we could say

@ous FOO BAR987

SQL * more ' SQL > "command prompt, or to the equivalent point in another front-end tools.»

This assumes that the ous.sql script is the default location. If you don't know what it is, you can always give the name of full path, like this:

@d:\my_directory\sql_stuff\creation_scripts\ous FOO BAR987

The script creates a different role for each user, it creates. This isn't a very common practice. Out of context, I can't say for sure if it's a very bad idea, but we can't if abstain I was wondering if based on such an unusual with these old tools is best for your needs.

ORA-0980 SYNONYM IS NO LONGER VALID

Hi all
11.2.0.1
How to list all the "SYNONYM is LONGER VALID' in our database?
Thank you very much
zxy

Please find some time to read the documents/manual or just google it.

Select object_name, status from dba_objects where type_objet = 'SYNONYM' and status = 'INVALID ';

Invalid objects in EBS R12.1.1 SCREWS
I ' v just installed EBS R12.1.1 SCREWS, having found invalid objects in its database that cannot be compiled by running rdbms/admin/utlrp.sql

SQL > @?/rdbms/admin/utlrp.sql

......

ITEMS WITH ERRORS
-------------------
4

......

ERRORS DURING THE RECOMPILATION
---------------------------
4

PL/SQL procedure successfully completed.

Invoking the procedure validation Ultra Search Install/Upgrade VALIDATE_WK
Ultra VALIDATE_WK of research done without error

PL/SQL procedure successfully completed.

SQL > SELECT COUNT (*) FROM obj$ State WHERE (4, 5, 6);

COUNT (*)
----------
12

SQL > SELECT master, count (*) amount FROM dba_objects WHERE the group status <>'VALID' by the owner;

SUM OF OWNER
------------------------------ ----------
RE                    1
CA                    2
PUBLIC 4
HERMAN 1
APPS                    5
FLOWS_010500 2

6 selected lines.

SQL > select * from sys. UTL_RECOMP_ERRORS;

OBJ # ERROR_AT COMPILE_ERR
------------- ----------------------------------------------------- ---------------------------------------------------------------------------
1006661 28 March 13 07.43.15.505723000 AM "ORA-04045: errors during recompilation/revalidation of the PUBLIC." WWV_FLOW_LIST_OF_VALUES_DATA
"ORA-00980: synonym translation is no longer valid.
1006663 28 March 13 07.43.15.507741000 AM "ORA-04045: errors during recompilation/revalidation of the PUBLIC." WWV_FLOW_LISTS_OF_VALUES$
"ORA-00980: synonym translation is no longer valid.
1006687 28 March 13 07.43.15.509455000 AM "ORA-04045: errors during recompilation/revalidation of the PUBLIC." WWV_FLOW_GENERIC
"ORA-00980: synonym translation is no longer valid.
1006699 28 March 13 07.43.15.511259000 AM "ORA-04045: errors during recompilation/revalidation of the PUBLIC." WWV_FLOW_FIELD_TEMPLATES
"ORA-00980: synonym translation is no longer valid.

Question:
How to solve this problem? Can I just remove these invalid objects from SYS. DBA_OBJECTS?
How to solve this problem? Can I just remove these invalid objects from SYS. DBA_OBJECTS?

Simply ignore these invalid objects because they should not affect the functionality of your application.

Thank you
Hussein

Invalid objects?
Hello

I installed 12.1.1 SCREWS & upgarded o 12.1.3, & managed...

But I see a lot of invalid objects... I ran adadmin & still the same utlrp...

When I checked the - utl_recomp_errors

ORA-04045: errors during recompilation/revalidation of the PUBLIC. WWV_FLOW_LIST_OF_VALUES_DATA
ORA-00980: synonym translation is no longer valid

ORA-04045: errors during recompilation/revalidation of the PUBLIC. WWV_FLOW_LISTS_OF_VALUES$
ORA-00980: synonym translation is no longer valid

ORA-04045: errors during recompilation/revalidation of the PUBLIC. WWV_FLOW_GENERIC
ORA-00980: synonym translation is no longer valid

ORA-04045: errors during recompilation/revalidation of the PUBLIC. WWV_FLOW_FIELD_TEMPLATES
ORA-00980: synonym translation is no longer valid

Thank you

Published by: 843272 on July 17, 2011 21:53
If the State of WSH_RLM_INTERFACE is not valid, then this is an expected behavior.

Follow these steps:

-Closing of the database
-Start of the database upgrade mode
-Run the utlrip.sql script
-Closing of the database
-Open the database normally
-Run the utlrp.sql script

Difference between UTLRP. SQL - UTLIRP. SQL - UTLIP. SQL? [272322.1 ID]

Then check the number of invalid objects.

Thank you
Hussein

synonym?
Hello

my oracle 10g db I have access to a tableX since an other oracle 10g db via (tableX@mydblink).

So, I created a synonym

CREATE SYNONYM tablex FOR tableX@mydblink;

If someone drops the synonym, I want to handle this in my pl/sql code

for example

create or replace procedure MyProc
var_col1 varchar2 (10);

Start

Select col1 in tablex var_col1;

Exception?

End

What is the exception available?
There are no exceptions, exceptions are handled the events of the time of execution.

If the referenced object is not the procedure will not compile.

If the procedure is already compiled when the object is deleted, it is invalid and will not run.

Invalid synonyms

Similar Questions

Maybe you are looking for