Finding Invalid objects in schema

Dear All,
How to find all invalid objects in an paticular schema
Regards,
Raju

Hello Raju
SQL> select object_type,count(*) from user_objects where status = 'INVALID'
2 group by object_type;
OBJECT_TYPE COUNT(*)
PACKAGE BODY 4
PROCEDURE 61
VIEW 3
next, as sys
exec dbms_utility.compile_schema( 'ACCOUNTS' );
PL/SQL procedure successfully completed.
then,
connect accounts
SQL> select object_type,count(*) from user_objects where status = 'INVALID'
group by object_type;
OBJECT_TYPE COUNT(*)
PACKAGE BODY 1
PROCEDURE 182
VIEW 3
try this
Ravi
http://dbaoraclefaqs.blogspot.com/

Similar Messages

How to find invalid objects in specific schema?

Please let me know hoe to find invalid objects in specific schema such as SYS?
Please help and guide
Thanks,
Waheed.

Ok i get invalid objects now if i want to delete these invalid objects which query i have to run?
also let me know there is no harm if i del invalid objects from SYS schema?
Please help and guide
Thanks,
Waheed.

How to find invalid views across schemas

I just started on a project that, well let's put it this way, has a messy database. It has multiple schemas and contains many views, synonyms and database links.
I want to add a column to a table, but I want to make sure
this doesn't invalidate any views somewhere in the database.
Is there a way to check for invalid views across multiple schemas? Or better yet, how to find out beforehand what views in what schemas look at the table?
Thanks,
Tim

To find out, where the table is used you can select:
select owner,name,type
from all_dependencies
where referenced_owner = (select user from dual)
and referenced_name = 'TABLENAME'
and referenced_type = 'TABLE'
It not only shows Views but also show�s if the table is used inside a trigger and so on.
To find out, what objects are invalid:
select owner, object_name, object_type
from all_objects
where status = 'INVALID';
regards
Anna

Problem with ORA-24372 invalid object for describe

I have unresolved problem with oracle message: ORA-24372 invalid object for describe. There is the client-server application which installed on users PCs. Client application is program on Delphi 7 that installed on several users PCs which works with Oracle DB 10g server (clients on users side 8.1.7) by means ODAC 5.7. Each user by means this application works with data on Oracle server. Each group of users uses its own schema. Each of this schema has grants to select data and execute procs in the main schema. During the time of operation I modified and compiled some procs in the main schema. As the result I found some depended Invalid objects in main schema. I recompiled them. There is no invalid objects in all schemas. But when I starts application in one user place (he uses for example schema X1) I see oracle message: ORA-24372 invalid object for describe. Other users in group which uses schema X1 works without this problem. There is finite aggregate of users of schema Х1 which has this message but some users of schema Х1 has no problem. All users has identical software and there is no any invalid objects in schemas! I try to start application on my PC using schema X1 and finds ORA-24372 then I try to start application on neighbors PC and it is all ok! It happened after I recompiled main schema in the time of users operation. What should I do to resolve this problem? Where to find the source of the problem: in client or in server?

To Mr. Sven Weller
The purpose of creation X1 (X2, Х3…) was restriction of users to access objects in the Main Schema. X1 has no any objects except function that returns her name for internal purposes. X1 has many synonyms for objects in the Main schema. There is no invalid objects in X1!

Help for "Invalid Object Count"

Hi
I got a Schema in my Database, i added a couple of tables with a script, dropped them again and did so 3 times because of some errors. Now i get the Error "Owner's Invalid Object Count" in the Category "Invalid Objects by Schema" and Oracle Enterprise Manager says i have invalid objects in my schema. How can i clean the schema and delete those invalid objects? i can't seen them in my tables, views or synonyms.
greets

May be some script error
u should drop old table
then create new table.
ok
good luck

Compile Invalid Objects

Hi friends,
how do i compile all the invalid objects in one time ???
thanks,
Raj

Hi,
Here's what I do when I need to recompile a user's schema. Don't say it's bullet proof, but so far it has worked for me. I use it after each deployment to a schema.
procedure recompile_schema
is
   l_type   user_objects.object_type%type;
   l_name   user_objects.object_name%type;
   l_stat   user_objects.status%type;
   compile_error exception;
   pragma exception_init(compile_error, -24344);
   cursor dep_cur
   is
          select object_id
            from (select o1.object_id
                        ,o1.object_name
                        ,o1.object_type
                        ,o1.status
                        ,d1.referenced_name
                        ,d1.referenced_type
                        ,case
                            when exists (select null
                                           from user_dependencies d2
                                          where d2.referenced_name = d1.name
                                            and d2.referenced_type = d1.type)
                            then
                               1
                            else
                               0
                         end
                            is_referenced
                    from user_dependencies d1, user_objects o1
                   where o1.object_type in
                               ('PACKAGE'
                               ,'PROCEDURE'
                               ,'FUNCTION'
                               ,'PACKAGE BODY'
                               ,'VIEW'
                               ,'MATERIALIZED VIEW'
                               ,'TRIGGER'
                               ,'SYNONYM')
                     and d1.name = o1.object_name
                     and d1.type = o1.object_type)
           where is_referenced = 1
      start with is_referenced = 0
      connect by object_name = prior referenced_name
             and object_type = prior referenced_type
        group by object_id
        order by max(level) desc, object_id;
   procedure do_compile(pi_object_type   in user_objects.object_type%type
                       ,pi_object_name   in user_objects.object_name%type)
   is
   begin
      --dbms_output.put_line('Compiling: ' || pi_object_name);
      if pi_object_type = 'PACKAGE BODY'
      then
         exe('ALTER PACKAGE ' || pi_object_name || ' COMPILE BODY');
      else
         exe('ALTER ' || pi_object_type || ' ' || pi_object_name || ' COMPILE');
      end if;
   exception
      when compile_error
      then
         dbms_output.put_line(sqlerrm);
   end do_compile;
begin
   dbms_output.put_line('recompiling invalid objects in schema ' || user);
   -- loop through all objects in order of dependancy.
   for rec in dep_cur
   loop
      -- select the objects attributes (type, name and status).
      select object_type, object_name, status
        into l_type, l_name, l_stat
        from user_objects
       where object_id = rec.object_id;
      -- if the object is invalid, recompile it.
      if l_stat = 'INVALID'
      then
         dbms_output.put_line('Compiling(1): ' || l_name);
         do_compile(l_type, l_name);
      end if;
   end loop;
   -- Recompile all remaining INVALID OBJECTS (all those without dependencies).
   for rec
   in (select object_type, object_name
         from user_objects
        where status = 'INVALID'
          and object_type in
                    ('PACKAGE'
                    ,'PROCEDURE'
                    ,'FUNCTION'
                    ,'TRIGGER'
                    ,'PACKAGE BODY'
                    ,'VIEW'
                    ,'MATERIALIZED VIEW'
                    ,'TRIGGER'
                    ,'SYNONYM'))
   loop
      dbms_output.put_line('Compiling(2): ' || rec.object_name);
      do_compile(rec.object_type, rec.object_name);
   end loop;
end recompile_schema;Regards
Peter

EM alerts :Owner's Invalid Object Count/ 79 object(s) are invalid

Invalid Objects by Schema /Owner's Invalid Object Count/ 79 object(s) are invalid in the SSTTSYS schema.
I am working on db ware house environment & get this alert log.
Can any body guide how i can solve this problem.
Either i should delete these objects or rebuild it ?
Or any other suggestions...

May be some script error
u should drop old table
then create new table.
ok
good luck

Invalid objects in APEX Schemas after import.

Hi,
After importing the APEX_040100 user in the database I got several invalid objects that are causing APEX not to work.
I gave up to compile them. After using all kind of tricks such as compile one schema at a time or compile all of them using the utlprp.sql script
or using EXEC DBMS_DDL.alter_compile('PACKAGE', 'MY_SCHEMA', 'MY_PACKAGE');
or one object art a time using command sililar to:
ALTER PACKAGE my_package COMPILE;
ALTER PACKAGE my_package COMPILE BODY;
ALTER PROCEDURE my_procedure COMPILE;
ALTER FUNCTION my_function COMPILE;
ALTER TRIGGER my_trigger COMPILE;
ALTER VIEW my_view COMPILE;
I can't find any documentation to show how to recompile them properly.
So I am asking:
1. How can we recompile all objects in APEX?
2. How can we re-install APEX?
3. How can we revert to previous version if both have problems?
Thanks
Yannis
Here is the list of invalid objects:
APEX_040100     PACKAGE     WWV_FLOW_DYNAMIC_EXEC     INVALID
APEX_040100     PACKAGE     WWV_FLOW_LOAD_DATA     INVALID
APEX_040100     PACKAGE     WWV_FLOW_SAMPLE_APP     INVALID
APEX_040100     PACKAGE     WWV_FLOW_UTILITIES     INVALID
APEX_040100     PACKAGE BODY     APEXWS     INVALID
APEX_040100     PACKAGE BODY     HTMLDB_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_4000_UI     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_ADMIN_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_ADVISOR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_AJAX     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_APPLICATION_INSTALL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_ASFCOOKIE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_AUDIT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_AUTHENTICATION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_AUTHENTICATION_ENGINE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_AUTHORIZATION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_BUILDER     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_BUTTON     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CALENDAR3     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CALENDAR_AJAX     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CHECK     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_COLLECTION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CONDITIONS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_COPY_PAGE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CREATE_APP_FROM_QUERY     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CREATE_MODEL_APP     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CSS_API_PRIVATE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CUSTOM_AUTH     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_CUSTOM_AUTH_STD     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DATALOAD_XML     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DATA_QUICK_FLOW     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DATA_UPLOAD     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DICTIONARY     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DISP_PAGE_PLUGS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DML     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DOWNLOAD     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DRAG_LAYOUT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_DYNAMIC_EXEC     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_ERROR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_F4000_P4150     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_F4000_PLUGINS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_F4000_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FILE_MGR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FLASH_CHART     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FLASH_CHART2     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FLASH_CHART5     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FLASH_CHART5_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FLASH_CHART_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FND_DEVELOPER_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FND_USER_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FORMS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_FORM_CONTROL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_GENERATE_DDL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_GENERATE_TABLE_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_GENERIC_ATTR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_GEN_API2     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_HINT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_HTML_API_PRIVATE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_IMP_PARSER     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_INSTALL_WIZARD     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_INSTANCE_ADMIN     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_ITEM     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_JAVASCRIPT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_JOB     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_LANG     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_LDAP     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_LIST     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_LOAD_DATA     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_LOAD_EXCEL_DATA     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_LOGIN     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_MAIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_META_DATA     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_META_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_MODEL_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_NATIVE_AUTHENTICATION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_NATIVE_DYNAMIC_ACTION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_NATIVE_ITEM     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PAGE_CACHE_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PLSQL_EDITOR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PLSQL_JOB     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PLUGIN_ENGINE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PLUGIN_F4000     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PLUGIN_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PPR_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PRINT_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PROCESS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PROCESS_UTILITY     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PROVISION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_PROVISIONING     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_QUERY_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_REGEXP     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_REGION_LAYOUT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_RENDER_QUERY     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_RENDER_SHORTCUT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_REST     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SAMPLE_APP     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SC_TRANSACTIONS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SECURITY     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SERIES_ATTR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SESSION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SESSION_MON     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SVG     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SW_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SW_PAGE_CALLS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SW_PARSER     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SW_SCRIPT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_SW_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TABLE_DRILL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TAB_MGR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TEAM     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TEAM_GEN_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TEMPLATES_UTIL     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_THEME_FILES     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_THEME_MANAGER     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TREE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_TREE_REGION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_UPGRADE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_UPGRADE_APP     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_UTILITIES     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_VALIDATION     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WEBSERVICES_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WEB_SERVICES     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WIZARD_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WIZ_CONFIRM     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET_AJAX     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET_DIALOGUE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET_EXPR     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET_FORM     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSHEET_STANDARD     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WORKSPACE_REPORTS     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_ATTACHMENT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_DIALOG     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_EXPORT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_FLASH_CHART     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_FORM     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_GEOCODE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_IMPORT     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_IMPORT_API     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_SECURITY     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_SETUP     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_STICKIES     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_UI     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_WS_WEBPAGE     INVALID
APEX_040100     PACKAGE BODY     WWV_FLOW_XLIFF     INVALID
APEX_040100     PACKAGE BODY     WWV_META_CLEANUP     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_ACC_LOAD     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_FRMMENU_LOAD_XML     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_FRM_LOAD_XML     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_FRM_OLB_LOAD_XML     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_FRM_UPDATE_APX_APP     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_FRM_UTILITIES     INVALID
APEX_040100     PACKAGE BODY     WWV_MIG_RPT_LOAD_XML     INVALID
APEX_040100     PACKAGE BODY     WWV_RENDER_CALENDAR2     INVALID
APEX_040100     PACKAGE BODY     WWV_RENDER_CHART2     INVALID
APEX_040100     PACKAGE BODY     WWV_RENDER_REPORT3     INVALID
APEX_040100     PROCEDURE     APEX_ADMIN     INVALID
APEX_040100     PROCEDURE     F     INVALID
APEX_040100     PROCEDURE     HTMLDB_ADMIN     INVALID
APEX_040100     PROCEDURE     WS     INVALID
APEX_040100     SYNONYM     APEX_COLLECTIONS     INVALID
APEX_040100     SYNONYM     HTMLDB_COLLECTIONS     INVALID
APEX_040100     TRIGGER     WWV_FLOW_FEEDBACK_T1     INVALID
APEX_040100     VIEW     WWV_FLOW_ADVISOR_RESULT     INVALID
APEX_040100     VIEW     WWV_FLOW_COLLECTIONS     INVALID
APEX_040100     VIEW     WWV_FLOW_SEARCH_RESULT     INVALID
APEX_040100     VIEW     WWV_MULTI_COMPONENT_EXPORT     INVALID

yannisr wrote:
Hi,
After importing the APEX_040100 user in the database I got several invalid objects that are causing APEX not to work.Hi,
You mean you did export APEX_040100 schema from one database and import it to another database?
There is also public synonyms and if I recall correct some objects are in SYS schema that belongs to Apex and are needed.
Regards,
Jari
http://dbswh.webhop.net/dbswh/f?p=BLOG:HOME:0

Compile invalid objects in apps schema

i make compiled the apps schema by
adadmin,utlrp.sql,compiled manual but still i am getting INVALID objects .. how to compile these objects ?
Below is the output
SQL>
column owner format A9
column object_name format A31
column object_type format A15
column last_ddl_time format A10
spool invalids.lst
select OWNER, OBJECT_NAME,OBJECT_TYPE,LAST_DDL_TIME
from dba_objects where status='INVALID'
order by owner;
OWNER OBJECT_NAME OBJECT_TYPE LAST_DDL_T
APPS FV_FACTS_TBAL_TRANSACTIONS PACKAGE BODY 03-MAR-13
APPS IGI_IAC_REINSTATE_PKG PACKAGE BODY 03-MAR-13
APPS IGI_IAC_RETIREMENT PACKAGE BODY 03-MAR-13
APPS CST_PERIODIC_ABSORPTION_PROC PACKAGE BODY 03-MAR-13
APPS FV_SLA_UTL_PROCESSING_PKG PACKAGE BODY 03-MAR-13
APPS FV_CCR_UTIL_PVT PACKAGE BODY 03-MAR-13
APPS PSA_AP_BC_PVT PACKAGE BODY 03-MAR-13
APPS XLA_00200_AAD_S_000012_PKG PACKAGE BODY 03-MAR-13
APPS AR_RECEIPT_UPDATE_API_PUB PACKAGE BODY 03-MAR-13
APPS AR_AUTOREC_API PACKAGE BODY 03-MAR-13
10 rows selected.
SQL> alter package APPS.FV_FACTS_TBAL_TRANSACTIONS compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.FV_FACTS_TBAL_TRANSACTIONS:
LINE/COL ERROR
1742/6 PL/SQL: SQL Statement ignored
1743/4 PL/SQL: ORA-00918: column ambiguously defined
SQL> alter package APPS.IGI_IAC_REINSTATE_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.IGI_IAC_REINSTATE_PKG:
LINE/COL ERROR
3470/3 PL/SQL: Statement ignored
3470/10 PLS-00306: wrong number or types of arguments in call to
'GET_ASSET_RETIRE_REC'
SQL> alter package APPS.IGI_IAC_RETIREMENT compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.IGI_IAC_RETIREMENT:
LINE/COL ERROR
4247/10 PL/SQL: Statement ignored
4247/18 PLS-00306: wrong number or types of arguments in call to
'GET_ASSET_RETIRE_REC'
SQL> alter package APPS.CST_PERIODIC_ABSORPTION_PROC compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.CST_PERIODIC_ABSORPTION_PROC:
LINE/COL ERROR
3901/3 PL/SQL: Statement ignored
3901/3 PLS-00306: wrong number or types of arguments in call to
'ITERATION_PROCESS'
SQL> alter package APPS.FV_SLA_UTL_PROCESSING_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.FV_SLA_UTL_PROCESSING_PKG:
LINE/COL ERROR
49/7 PL/SQL: Statement ignored
49/22 PLS-00302: component 'PSA_XLA_ERROR' must be declared
SQL> alter package APPS.FV_CCR_UTIL_PVT compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.FV_CCR_UTIL_PVT:
LINE/COL ERROR
2926/3 PL/SQL: Statement ignored
2926/19 PLS-00302: component 'CONTACT_NAME' must be declared
2928/4 PL/SQL: Statement ignored
2928/20 PLS-00302: component 'CONTACT_PHONE' must be declared
2929/8 PL/SQL: Statement ignored
2929/24 PLS-00302: component 'CONTACT_PHONE' must be declared
2931/3 PL/SQL: Statement ignored
2931/19 PLS-00302: component 'CONTACT_EMAIL' must be declared
2932/3 PL/SQL: Statement ignored
2932/19 PLS-00302: component 'CONTACT_FAX' must be declared
SQL> alter package APPS.PSA_AP_BC_PVT compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.PSA_AP_BC_PVT:
LINE/COL ERROR
291/11 PL/SQL: Statement ignored
291/26 PLS-00302: component 'PSA_XLA_ERROR' must be declared
346/13 PL/SQL: Statement ignored
346/28 PLS-00302: component 'PSA_XLA_ERROR' must be declared
835/7 PL/SQL: Statement ignored
835/12 PLS-00313: 'ISPREPAYDIST' not declared in this scope
1002/15 PL/SQL: Statement ignored
1002/34 PLS-00201: identifier 'J' must be declared
1014/13 PL/SQL: Statement ignored
1014/48 PLS-00201: identifier 'I' must be declared
1020/13 PL/SQL: Statement ignored
LINE/COL ERROR
1020/43 PLS-00201: identifier 'I' must be declared
1022/13 PL/SQL: Statement ignored
1024/73 PLS-00201: identifier 'I' must be declared
1055/11 PL/SQL: Statement ignored
1055/48 PLS-00201: identifier 'I' must be declared
1057/11 PL/SQL: SQL Statement ignored
1057/51 PLS-00201: identifier 'I' must be declared
1080/80 PLS-00201: identifier 'I' must be declared
1080/80 PLS-00201: identifier 'I' must be declared
SQL> alter package APPS.XLA_00200_AAD_S_000012_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.XLA_00200_AAD_S_000012_PKG:
LINE/COL ERROR
157514/2 PLS-00103: Encountered the symbol "THEN" when expecting one of
the following:
( - + case mod new not null <an identifier>
<a double-quoted delimited-identifier> <a bind variable> avg
count current exists max min prior sql stddev sum variance
execute forall merge time timestamp interval date
<a string literal with character set specification>
<a number> <a single-quoted SQL string> pipe
<an alternatively-quoted string literal with character set
specification>
<an alternatively-quote
LINE/COL ERROR
SQL> alter package APPS.AR_RECEIPT_UPDATE_API_PUB compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.AR_RECEIPT_UPDATE_API_PUB:
LINE/COL ERROR
0/0 PL/SQL: Compilation unit analysis terminated
1/14 PLS-00201: identifier 'AR_RECEIPT_UPDATE_API_PUB' must be
declared
1/14 PLS-00304: cannot compile body of 'AR_RECEIPT_UPDATE_API_PUB'
without its specification
SQL> show err
Errors for PACKAGE BODY APPS.AR_AUTOREC_API:
LINE/COL ERROR
2724/9 PL/SQL: SQL Statement ignored
2740/27 PL/SQL: ORA-00904: "EXT"."SEQ_TYPE_LAST": invalid identifier
note:application v12.0.4 database 10.2.3

SQL> alter package APPS.FV_FACTS_TBAL_TRANSACTIONS compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.FV_FACTS_TBAL_TRANSACTIONS:
LINE/COL ERROR
1742/6 PL/SQL: SQL Statement ignored
1743/4 PL/SQL: ORA-00918: column ambiguously defined
SQL> alter package APPS.CST_PERIODIC_ABSORPTION_PROC compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.CST_PERIODIC_ABSORPTION_PROC:
LINE/COL ERROR
3901/3 PL/SQL: Statement ignored
3901/3 PLS-00306: wrong number or types of arguments in call to
'ITERATION_PROCESS'
SQL> alter package APPS.AR_RECEIPT_UPDATE_API_PUB compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.AR_RECEIPT_UPDATE_API_PUB:
LINE/COL ERROR
0/0 PL/SQL: Compilation unit analysis terminated
1/14 PLS-00201: identifier 'AR_RECEIPT_UPDATE_API_PUB' must be
declared
1/14 PLS-00304: cannot compile body of 'AR_RECEIPT_UPDATE_API_PUB'
without its specification
SQL> alter package APPS.XLA_00200_AAD_S_000012_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.XLA_00200_AAD_S_000012_PKG:
LINE/COL ERROR
157514/2 PLS-00103: Encountered the symbol "THEN" when expecting one of
the following:
( - + case mod new not null <an identifier>
<a double-quoted delimited-identifier> <a bind variable> avg
count current exists max min prior sql stddev sum variance
execute forall merge time timestamp interval date
<a string literal with character set specification>
<a number> <a single-quoted SQL string> pipe
<an alternatively-quoted string literal with character set
specification>
<an alternatively-quote
LINE/COL ERROR
SQL> alter package APPS.FV_CCR_UTIL_PVT compile body;
Warning: Package Body altered with compilation errors.
SQL> show err
Errors for PACKAGE BODY APPS.FV_CCR_UTIL_PVT:
LINE/COL ERROR
2926/3 PL/SQL: Statement ignored
2926/19 PLS-00302: component 'CONTACT_NAME' must be declared
2928/4 PL/SQL: Statement ignored
2928/20 PLS-00302: component 'CONTACT_PHONE' must be declared
2929/8 PL/SQL: Statement ignored
2929/24 PLS-00302: component 'CONTACT_PHONE' must be declared
2931/3 PL/SQL: Statement ignored
2931/19 PLS-00302: component 'CONTACT_EMAIL' must be declared
2932/3 PL/SQL: Statement ignored
2932/19 PLS-00302: component 'CONTACT_FAX' must be declared

Invalid objects and ORA-00600 after deleting XML schema

I am running Oracle 10.2.0.3 on Solaris 10. I am new to XML DB but my developers requested it for a new application. Recently we have noticed the following issue:
My developers have attempted to re-register several schemas using:
DBMS_XMLSchema.deleteSchema(SchemaURL => l_strSchemaURL,
Delete_Option => DBMS_XMLSchema.Delete_Cascade_Force);
And then re-register.
DBMS_XMLSchema.RegisterURI( SchemaURL => l_strSchemaURL,
SchemaDocURI => l_strImportURL,
Local => True,
GenTypes => True,
GenBean => False,
GenTables => True,
Force => False,
EnableHierarchy => DBMS_XMLSCHEMA.ENABLE_HIERARCHY_RESMETADATA);
Afterwards I have noticed several invalid objects:
OWNER        OBJECT_NAME                    OBJECT_TYPE     STATUS
ELSVC        hsp_standard825_TAB$xd         TRIGGER         INVALID
ELSVC        hsp_standard1145_TAB$xd        TRIGGER         INVALID
ELSVC        hsp_standard_set827_TAB$xd     TRIGGER         INVALID
ELSVC        hsp_standard_set827_TAB        TABLE           INVALID
ELSVC        hsp_product822_TAB$xd          TRIGGER         INVALID
ELSVC        hsp_product822_TAB             TABLE           INVALID
ELSVC        hsp_planner_content833_TAB     TABLE           INVALID
ELSVC        hsp_planner_content833_TAB$xd TRIGGER         INVALID
ELSVC        hsp_correlations839_TAB        TABLE           INVALID
ELSVC        hsp_correlations839_TAB$xd     TRIGGER         INVALID
ELSVC        hsp_standard825_TAB            TABLE           INVALID
ELSVC        hsp_program819_TAB             TABLE           INVALID
ELSVC        hsp_program819_TAB$xd          TRIGGER         INVALID
XDB          XDLNKrHbGsLaHgRAAUTyLEhg==     XML SCHEMA      INVALID
XDB          XDLNKrHbIULaHgRAAUTyLEhg==     XML SCHEMA      INVALID
XDB          XDLNKrHbJZLaHgRAAUTyLEhg==     XML SCHEMA      INVALID
XDB          XDLNKrHbGFLaHgRAAUTyLEhg==     XML SCHEMA      INVALID
XDB          XDLNKrHbHdLaHgRAAUTyLEhg==     XML SCHEMA      INVALID and if I attempt to compile the triggers I receive an ORA-00600: internal error code, arguments: [diana for triggering table/view ], [], [], [], [], [], [], []. I opened a TAR with oracle but they have not made much headway. Are we attempting to de-register the schemas improperly? Has anyone seen this issue before?
Thanks,
Brian

SR 6204906.993. Up to this point oracle was able to help me identify that the invalid objects were related to the ORA-00600 but it was just recently that it appeared the Issue was possibly related to the delete schema procedure. The informed me that they were not aware of any known issues with this procedure.
Thanks

Invalid Object when Calling Stored Procedure from JDBC Adapter

JDBC Outbound adapter in XI 2.0 connected to SQL Server. I've coded my mapping to format the XSL mapping properly but the Adapter appears to not be able to find the Stored Procedure. Error message returned is "Invalid Object spStoredProcedureName".
Does anybody have any clue as to what I'm missing???

I know this is trivial, but did you use the "full" name of the SP as <schema>.<procname>???
HTH

Invalid objects after running catalog.sql and catproc.sql

I have a db 10.1.0.3.0. standard edition with the 10.1.0.4.0 patch installed.
After executing catalog.sql and catproc.sql the database contains lots of invalid objects in the public, olapsys and xdb schemas.
I have executed utlrp.sql, the script completes successfully, but lots of invalid objects remain.
Does anyone know how to fix this?
Thanks in advance.
Below is the output of
select owner, object_name, object_type from dba_objects where status like 'INVALID';
OWNER OBJECT_NAME OBJECT_TYPE
XDB DBMS_XDBUTIL_INT PACKAGE
XDB SETMODFLG PROCEDURE
XDB DBMS_XDBZ0 PACKAGE BODY
XDB DBMS_XDBUTIL_INT PACKAGE BODY
PUBLIC DBMS_XDBUTIL_INT SYNONYM
XDB XDB$PATCHUPSCHEMA PROCEDURE
OLAPSYS ALL$OLAP2_AW_CATALOGS VIEW
PUBLIC ALL_OLAP2_AW_CATALOGS SYNONYM
OLAPSYS ALL$OLAP2_AW_CATALOG_MEASURES VIEW
PUBLIC ALL_OLAP2_AW_CATALOG_MEASURES SYNONYM
OLAPSYS ALL$OLAP2_AW_PHYS_OBJ VIEW
PUBLIC ALL_OLAP2_AW_PHYS_OBJ SYNONYM
OLAPSYS ALL$OLAP2_AW_PHYS_OBJ_PROP VIEW
PUBLIC ALL_OLAP2_AW_PHYS_OBJ_PROP SYNONYM
OLAPSYS ALL$OLAP2_AW_DIMENSIONS VIEW
PUBLIC ALL_OLAP2_AW_DIMENSIONS SYNONYM
OLAPSYS ALL$OLAP2_AW_ATTRIBUTES VIEW
PUBLIC ALL_OLAP2_AW_ATTRIBUTES SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBES VIEW
PUBLIC ALL_OLAP2_AW_CUBES SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_DIM_USES VIEW
PUBLIC ALL_OLAP2_AW_CUBE_DIM_USES SYNONYM
OLAPSYS ALL$AW_DIM_ENABLED_VIEWS VIEW
PUBLIC ALL_AW_DIM_ENABLED_VIEWS SYNONYM
OLAPSYS ALL$AW_CUBE_ENABLED_VIEWS VIEW
PUBLIC ALL_AW_CUBE_ENABLED_VIEWS SYNONYM
OLAPSYS ALL$AW_CUBE_ENABLED_HIERCOMBO VIEW
PUBLIC ALL_AW_CUBE_ENABLED_HIERCOMBO SYNONYM
OLAPSYS ALL$OLAP2_AW_DIM_LEVELS VIEW
PUBLIC ALL_OLAP2_AW_DIM_LEVELS SYNONYM
OLAPSYS ALL$OLAP2_AW_DIM_HIER_LVL_ORD VIEW
PUBLIC ALL_OLAP2_AW_DIM_HIER_LVL_ORD SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_MEASURES VIEW
PUBLIC ALL_OLAP2_AW_CUBE_MEASURES SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_SPECS VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_SPECS SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_MEAS VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_MEAS SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_LVL VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_LVL SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_OP VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_OP SYNONYM
OLAPSYS MRAC_OLAP2_AW_DIMENSIONS_V VIEW
OLAPSYS MRAC_OLAP2_AW_CUBES_V VIEW
OLAPSYS MRAC_OLAP2_AW_CUBE_MEASURES_V VIEW
PUBLIC MRV_OLAP2_AW_DIMENSIONS SYNONYM
PUBLIC MRV_OLAP2_AW_CUBES SYNONYM
PUBLIC MRV_OLAP2_AW_CUBE_MEASURES SYNONYM
OLAPSYS CWM2_OLAP_METADATA_REFRESH PACKAGE BODY
OLAPSYS OLAP_SYS_AW_ACCESS_DIM_VIEW VIEW
OLAPSYS OLAP_SYS_AW_ACCESS_CUBE_VIEW VIEW
OLAPSYS OLAP_SYS_AW_ENABLE_ACCESS_VIEW VIEW
PUBLIC OLAP_SYS_AW_ACCESS_CUBE_VIEW SYNONYM
PUBLIC OLAP_SYS_AW_ACCESS_DIM_VIEW SYNONYM
PUBLIC OLAP_SYS_AW_ENABLE_ACCESS_VIEW SYNONYM
OLAPSYS CWM2_OLAP_OLAPAPI_ENABLE PACKAGE BODY
OLAPSYS DBMS_AWM PACKAGE BODY
OLAPSYS CWM2_OLAP_CUBE PACKAGE BODY

This note explains 80% of the problem: 42 invalid objects are normal, I have 52 invalid objects.
I have re-executed the catpatch.sql script, I couldn't find any errors in the output. At the end Oracle Intermedia and Oracle Expression Filter remain invalid.
last lines of catpatch.sql output:
COMP_NAME STATUS VERSION
OLAP Analytic Workspace OPTION OFF 10.1.0.3.0
Oracle OLAP API OPTION OFF 10.1.0.3.0
Oracle Database Catalog Views VALID 10.1.0.4.0
Oracle Database Packages and Types VALID 10.1.0.4.0
JServer JAVA Virtual Machine VALID 10.1.0.4.0
Oracle XDK VALID 10.1.0.4.0
Oracle Database Java Packages VALID 10.1.0.4.0
Oracle XML Database VALID 10.1.0.4.0
Oracle interMedia INVALID 10.1.0.4.0
Oracle Text VALID 10.1.0.4.0
Oracle Ultra Search VALID 10.1.0.4.0
Oracle Expression Filter INVALID 10.1.0.4.0
Oracle Enterprise Manager VALID 10.1.0.4.0
Oracle Workspace Manager VALID 10.1.0.2.0
Oracle Data Mining OPTION OFF 10.1.0.3.0
OLAP Catalog OPTION OFF 10.1.0.3.0
Spatial OPTION OFF 10.1.0.3.0
SQL> select owner, object_name, object_type from dba_objects where status like 'INVALID';
OWNER OBJECT_NAME OBJECT_TYPE
WK_TEST BIN$9oUB6zbaOP/gMCzPA4J5+w==$0 TRIGGER
OLAPSYS ALL$OLAP2_AW_CATALOGS VIEW
PUBLIC ALL_OLAP2_AW_CATALOGS SYNONYM
OLAPSYS ALL$OLAP2_AW_CATALOG_MEASURES VIEW
PUBLIC ALL_OLAP2_AW_CATALOG_MEASURES SYNONYM
OLAPSYS ALL$OLAP2_AW_PHYS_OBJ VIEW
PUBLIC ALL_OLAP2_AW_PHYS_OBJ SYNONYM
OLAPSYS ALL$OLAP2_AW_PHYS_OBJ_PROP VIEW
PUBLIC ALL_OLAP2_AW_PHYS_OBJ_PROP SYNONYM
OLAPSYS ALL$OLAP2_AW_DIMENSIONS VIEW
PUBLIC ALL_OLAP2_AW_DIMENSIONS SYNONYM
OLAPSYS ALL$OLAP2_AW_ATTRIBUTES VIEW
PUBLIC ALL_OLAP2_AW_ATTRIBUTES SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBES VIEW
PUBLIC ALL_OLAP2_AW_CUBES SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_DIM_USES VIEW
PUBLIC ALL_OLAP2_AW_CUBE_DIM_USES SYNONYM
OLAPSYS ALL$AW_DIM_ENABLED_VIEWS VIEW
PUBLIC ALL_AW_DIM_ENABLED_VIEWS SYNONYM
OLAPSYS ALL$AW_CUBE_ENABLED_VIEWS VIEW
PUBLIC ALL_AW_CUBE_ENABLED_VIEWS SYNONYM
OLAPSYS ALL$AW_CUBE_ENABLED_HIERCOMBO VIEW
PUBLIC ALL_AW_CUBE_ENABLED_HIERCOMBO SYNONYM
OLAPSYS ALL$OLAP2_AW_DIM_LEVELS VIEW
PUBLIC ALL_OLAP2_AW_DIM_LEVELS SYNONYM
OLAPSYS ALL$OLAP2_AW_DIM_HIER_LVL_ORD VIEW
PUBLIC ALL_OLAP2_AW_DIM_HIER_LVL_ORD SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_MEASURES VIEW
PUBLIC ALL_OLAP2_AW_CUBE_MEASURES SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_SPECS VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_SPECS SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_MEAS VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_MEAS SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_LVL VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_LVL SYNONYM
OLAPSYS ALL$OLAP2_AW_CUBE_AGG_OP VIEW
PUBLIC ALL_OLAP2_AW_CUBE_AGG_OP SYNONYM
OLAPSYS MRAC_OLAP2_AW_DIMENSIONS_V VIEW
OLAPSYS MRAC_OLAP2_AW_CUBES_V VIEW
OLAPSYS MRAC_OLAP2_AW_CUBE_MEASURES_V VIEW
PUBLIC MRV_OLAP2_AW_DIMENSIONS SYNONYM
PUBLIC MRV_OLAP2_AW_CUBES SYNONYM
PUBLIC MRV_OLAP2_AW_CUBE_MEASURES SYNONYM
OLAPSYS CWM2_OLAP_METADATA_REFRESH PACKAGE BODY
OLAPSYS OLAP_SYS_AW_ACCESS_DIM_VIEW VIEW
OLAPSYS OLAP_SYS_AW_ACCESS_CUBE_VIEW VIEW
OLAPSYS OLAP_SYS_AW_ENABLE_ACCESS_VIEW VIEW
PUBLIC OLAP_SYS_AW_ACCESS_CUBE_VIEW SYNONYM
PUBLIC OLAP_SYS_AW_ACCESS_DIM_VIEW SYNONYM
PUBLIC OLAP_SYS_AW_ENABLE_ACCESS_VIEW SYNONYM
OLAPSYS CWM2_OLAP_OLAPAPI_ENABLE PACKAGE BODY
OLAPSYS DBMS_AWM PACKAGE BODY
OLAPSYS CWM2_OLAP_CUBE PACKAGE BODY
53 rows selected.

10.2.0.4, Spatial and invalid objects

We don't use spatial. We have no plans to use spatial. We do use Intermedia, badly.
When I upgraded a database from 10.2.0.3 to 10.2.0.4, everything went OK, except that one object in the MDSYS schema (I can't remember its name, but it was something like SDO_GEOMETRY) was rendered 'invalid' in dba_objects afterwards.
I tried to manually re-compile it. It produced errors like 'table doesn't exist'. And I got to thinking that this was a Spatial object that was invalid because none of the other Spatial components was installed. I needed the invalid status to go away because my boss has a query that spots invalid objects and hassles me if any exist, and my attempts to say 'this one doesn't matter' weren't working.
So I used dbca to add Spatial to the database. (Added a tick to the spatial selector on the database options page). The addition went well, and at the end of it... zero invalid objects.
Problem solved, sort of. Now I have a new problem: when I ran dbca again to UNinstall Spatial, the tick against the Spatial option is greyed out and it cannot be de-selected and hence removed from my database.
And so my questions. How do you remove the Spatial stuff? Will removing it break Intermedia? Is there a better way to fix the 'invalid MDSYS object' problem caused by the 10.2.0.4 upgrade in the first place, because I have 8 other database to upgrade in the coming days? And, if the simplest thing to do is to just leave all the Spatial objects in the database, will we be in breach of our license, because we certainly haven't paid to use this feature, but we equally certainly have no use for it?

I would guess that most questions asked here could have been resolved by 'searching on Metalink first'. According to your standards and rules, then, that makes this place mostly redundant. Perhaps we should just shut the place down?
No, I'll tell you what: if you find your time being wasted, perhaps you could just not bother replying instead of pronouncing on high how those so much less exalted than yourself should behave and do things. You could have provided a metalink document number without the accompanying attitude, and then you would have my thanks and appreciation. But, for being a pompous a-s-s, you get neither.
Here's a clue. Classic Metalink. Search for '10.2.0.4 spatial errors after upgrade', All Sources. Your precious document appears only 16th in the resulting list. Yeah, I could wade through 15 irrelevant documents before stumbling over the correct one, but I figure upgrading to 10.2.0.4 can't be that rare; somebody will have encountered the problem before; quickest way to a solution is therefore probably to post here. Not, I would have thought, an entirely unreasonable train of thought, though obviously it is in your particular corner of the universe.
Besides which, whilst that document tells me how to fix the invalid objects without installing Spatial, which will certainly prove useful for all my other database upgrades, it doesn't tell me (and neither did you) how you uninstall Spatial after having installed it with dbca. That's not asking you to fill in the gaps, by the way: I wouldn't want to waste any more of your precious time.
I'm just pointing out that your "answer", as well as being pompous and arrogant, also proves itself to be deficient.

Why do I get "Error 1 occured at Config Data Registry.vi(get data) invalid object 0" while starting my application?

Why do I get "Error 1 occured at Config Data Registry.vi(get data) invalid object 0" when starting my application created in LabVIEW 7.1? I am starting the application in a PXI rack running Windows XP. I have an executable written in LabVIEW 7.0 that runs without this error. After clicking the Continue button in the error, the application seems to continue happily.
Is there something I need to include when I make the executable?
I would like to understand and eliminate this start up error.
Thanks in advance.
BobNorth

Hi Bob,
I looked through the program and I figured out where the error is coming from, and potentially what is causing it. In a lot of the cases of the program you are searching a 1-D array for the name of the case, and if you don't find it then it skips the function and gives "Error 1 occurred at Config Data Registry.vi(CASENAME) invalid object 0". I attached a screenshot that shows what I mean. The Search 1-D Array.vi is returning a -1 which means it didn't find the case. The reason I believe this is happening is because the shift register for that array is not initialized. While the other cases "reset" and "register" interact with the array shift registers and most likely create the array you need, if the program defaults to the "get data" case then it will try to run that before registering and won't have an array to search. This would also explain why it only has this problem at first and seems to run just fine after that. To fix this you should either make an initial array and wire it into the shift register or make the "reset" case the default as opposed to the "get data" case.
Regards,
Peter W.
Attachments:
Config Data Registry.png ‏55 KB

Unable to delete User object in FIM Portal - Cannot find the object "#calculateRequestSetTransitionsAssembleStatementsPartition"

Hi,
***Problem
I encounter a problem with FIM (version 4.1.3441.0 and 4.1.3496.0) when I try to delete a User object (and only a User object) whatever if it is
manually/Expiration Workflow/Powershell.
Deleting a User object used to be perfectly functional and, without any product version modification, stopped working. I haven't neither deleted/modified or add a
"Grant" MPR or any of the corresponding Sets since last time I saw it working.
Displayed error is "Request could not be dispatched" in FIM Portal and is referencing a stored procedure in Event Viewer.
***Error details
When I try to delete a User object, here is the output :
Portal
"Processing error" on submit
with the following details
Request status is stuck at "Validating" until next restart of FIM Service (after what it becomes “Canceled”)
Request’s “Applied Policy” tab does not contain any MPR where, at least, a “Grant” MPR is expected
As SQL Timeout is relatively high and error happens quickly, I don’t think there is a Timeout problem under that.
Logs
« Application »
The Portal cannot connect to the middle tier using the web service interface. This failure prevents all portal scenarios from functioning correctly.
The cause may be due to a missing or invalid server url, a downed server, or an invalid server firewall configuration.
Ensure the portal configuration is present and points to the resource management service.
« Forefront Identity Manager »
Reraised Error 50000, Level 16, State 1, Procedure ReRaiseException, Line 37, Message: Reraised Error 1088, Level 16, State 12, Procedure CalculateRequestSetTransitionsAssembleStatements,
Line 332, Message: Cannot find the object "#calculateRequestSetTransitionsAssembleStatementsPartition" because it does not exist or you do not have permissions.
Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 0.
Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---> System.Data.SqlClient.SqlException: Reraised Error 50000, Level 16, State
1, Procedure ReRaiseException, Line 37, Message: Reraised Error 1088, Level 16, State 12, Procedure CalculateRequestSetTransitionsAssembleStatements, Line 332, Message: Cannot find the object "#calculateRequestSetTransitionsAssembleStatementsPartition"
because it does not exist or you do not have permissions.
Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 0.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler,
TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult
result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.ResourceManagement.Data.DataAccess.UpdateRequest(RequestType request, IEnumerable`1 updates)
   --- End of inner exception stack trace ---
Requestor: urn:uuid:7fb2b853-24f0-4498-9534-4e10589723c4
Correlation Identifier: e7209633-46d0-4f4b-a59e-807649ef71ea
Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---> System.InvalidCastException: Specified cast is not valid.
   at Microsoft.ResourceManagement.WebServices.RequestDispatcher.CreateRequest(UniqueIdentifier requestor, UniqueIdentifier targetIdentifier, OperationType
operation, String businessJustification, List`1 requestParameters, CultureInfo locale, Boolean isChildRequest, Guid cause, Boolean doEvaluation, Nullable`1 serviceId, Nullable`1 servicePartitionId, UniqueId messageIdentifier, UniqueIdentifier requestContextIdentifier,
Boolean maintenanceMode)
   at Microsoft.ResourceManagement.WebServices.RequestDispatcher.CreateRequest(UniqueIdentifier requestor, UniqueIdentifier targetIdentifier, OperationType
operation, String businessJustification, List`1 requestParameters, CultureInfo locale, Boolean isChildRequest, Guid cause, Boolean doEvaluation, Nullable`1 serviceId, Nullable`1 servicePartitionId, UniqueId messageIdentifier)
   at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Delete(Message request)
   --- End of inner exception stack trace ---
For information, a maintenance plan rebuild/reorganize indexes daily and this problem has occurred on servers with different performances.
Is any of you has already encounter this problem ?
Any help would be greatly appreciated,
Thanks in advance for your help,
Matthew

While there are several SQL Agent jobs (FIM Temporal Events, Maintain Sets, and Maintain Groups among others)created by the FIM install only one of those is enabled and scheduled and it calls all of the same stored procedures that the other
jobs do. Step 2 is Maintain sets and Step 3 is maintain groups. So the Maintain sets and groups jobs never need to get enabled and scheduled, but if you want them to be maintained more frequently then you can.
David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

Finding Invalid objects in schema

Similar Messages

Maybe you are looking for