Re: The first oracle 11.2.0 problem:

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Thu, 3 Sep 2009 22:31:12 +0100
Message-ID: <IoednfTOpPcCqD3XnZ2dnUVZ8gednZ2d_at_bt.com>

"Mladen Gogala" <gogala.mladen_at_bogus.email.invalid> wrote in message news:h7oei0$gm2$1_at_solani.org...
> 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.
>
>
>
>
>
>
> --
> http://mgogala.freehostia.com

If you want to examine x$ definitions:

set linesize 132
set pagesize 120
set newpage 0

break on kqftanam skip page
column kqftanam new_value m_table noprint

column kqfconam heading "Column"
column kqfcodty heading "Ext Type"
column kqfcotyp heading "Int Type"
column kqfcomax heading "Array Max"
column kqfcolsz heading "Len Size"
column kqfcolof heading "Len Offset"
column kqfcosiz heading "Col Size"
column kqfcooff heading "Offset"
column kqfcoidx heading "Index"
column kqfcoipo heading "Idx Col"

ttitle -
 skip 1 -
 center m_table -
 skip 2

spool x_desc

select

 kqftanam,
 kqfconam,
 kqfcodty,
 kqfcotyp,
 kqfcomax,
 kqfcolsz,
 kqfcolof,
 kqfcosiz,
 kqfcooff,
 kqfcoidx,

 kqfcoipo
from
 x$kqfta ta,
 x$kqfco co
where
 co.kqfcotab = ta.indx
order by
 kqftanam,
 kqfcooff
;

spool off

-- 
Regards

Jonathan Lewis
http://jonathanlewis.wordpress.com

Author: Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html

The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html

Received on Thu Sep 03 2009 - 16:31:12 CDT