Re: The first oracle 11.2.0 problem:
Date: Thu, 3 Sep 2009 17:57:15 -0700 (PDT)
Message-ID: <ccceed80-50c6-4f31-be2d-72de52622bc4_at_j39g2000yqh.googlegroups.com>
On Sep 3, 8:58 am, Mladen Gogala <gogala.mla..._at_bogus.email.invalid> wrote:
snip
> Na Thu, 03 Sep 2009 13:32:52 +0100, Palooka napisao:
>
> > Just a thought: What about looking at the SQL for the view and creating
> > your own SQL or view on whatever is/are the X$ table(s)?
>
> > Palooka
>
> The view is simple:
>
> CREATE OR REPLACE FORCE VIEW "SYS"."V_$DIAG_ALERT_EXT" ("ADDR", "INDX",
> "INST_ID", "ADR_PATH_IDX", "ADR_HOME", "ORIGINATING_TIMESTAMP",
> "NORMALIZED_TIMESTAMP", "ORGANIZATION_ID", "COMPONENT_ID", "HOST_ID",
> "HOST_ADDRESS", "MESSAGE_TYPE", "MESSAGE_LEVEL", "MESSAGE_ID",
> "MESSAGE_GROUP", "CLIENT_ID", "MODULE_ID", "PROCESS_ID", "THREAD_ID",
> "USER_ID", "INSTANCE_ID", "DETAILED_LOCATION", "UPSTREAM_COMP_ID",
> "DOWNSTREAM_COMP_ID", "EXECUTION_CONTEXT_ID",
> "EXECUTION_CONTEXT_SEQUENCE", "ERROR_INSTANCE_ID",
> "ERROR_INSTANCE_SEQUENCE", "MESSAGE_TEXT", "MESSAGE_ARGUMENTS",
> "SUPPLEMENTAL_ATTRIBUTES", "SUPPLEMENTAL_DETAILS", "PARTITION",
> "RECORD_ID", "FILENAME", "PROBLEM_KEY", "VERSION") AS
> select
> "ADDR","INDX","INST_ID","ADR_PATH_IDX","ADR_HOME","ORIGINATING_TIMESTAMP","NORMALIZED_TIMESTAMP","ORGANIZATION_ID","COMPONENT_ID","HOST_ID","HOST_ADDRESS","MESSAGE_TYPE","MESSAGE_LEVEL","MESSAGE_ID","MESSAGE_GROUP","CLIENT_ID","MODULE_ID","PROCESS_ID","THREAD_ID","USER_ID","INSTANCE_ID","DETAILED_LOCATION","UPSTREAM_COMP_ID","DOWNSTREAM_COMP_ID","EXECUTION_CONTEXT_ID","EXECUTION_CONTEXT_SEQUENCE","ERROR_INSTANCE_ID","ERROR_INSTANCE_SEQUENCE","MESSAGE_TEXT","MESSAGE_ARGUMENTS","SUPPLEMENTAL_ATTRIBUTES","SUPPLEMENTAL_DETAILS","PARTITION","RECORD_ID","FILENAME","PROBLEM_KEY","VERSION"
> from x$diag_ALERT_EXT;
>
> Problem lies in the x$diag_alert_ext table which is built in the code.
> The DDL cannot be re-generated using DBMS_METADATA. It's not even in the
> DBA_OBJECTS:
>
> SQL>
> SQL> select object_type from dba_objects
> where object_name='X$DIAG_ALERT_EXT';
>
> no rows selected
>
> I even looked into SQL.BSQ, but there it doesn't contain the DDL for that
> table, either. This is a bug.
Did you get it volleyed over into oracle support?
If no support contract someone else can do it. Received on Thu Sep 03 2009 - 19:57:15 CDT