Eclipse 3.4 with Oracle Plugin - materialized view problem

Similar Questions

• Oracle 8i Materialized view

  I'm on oracle 8.1.7
  
  A few times is not automatically refresh
  
  -I want to connect view refresh time in other tables when it refreshes
  
  -wanted to know whether the necessary changes in the view script
  
  
  DROP MATERIALIZED VIEW MSIRC. IL_BRANCHES;
  
  CREATE THE MSIRC MATERIALIZED VIEW. IL_BRANCHES
  REFRESH FORCE
  START WITH TO_DATE (October 12, 2009 09:15:42 "," dd-mon-yyyy hh24:mi:ss')
  NEXT sysdate + 1/1440
  WITH THE PRIMARY KEY
  ACTIVATE THE QUERY REWRITING
  AS
  / * In format on 2009-10-12 13:44:16 (PS5 v5.115.810.9015) * /.
  SELECT 'IL_BRANCHES '. "" BRANCH_ID ""BRANCH_ID"
  'IL_BRANCHES '. ' ' ' 'NAME',
  'IL_BRANCHES '. "' HEADLINE '"TITLE. "
  'IL_BRANCHES '. "" INSTANCE_ID ""INSTANCE_ID. "
  'IL_BRANCHES '. "' PARENT_ID '"PARENT_ID"
  'IL_BRANCHES '. "" PUB_STATUS ""PUB_STATUS"
  'IL_BRANCHES '. "" ALERT_STATUS ""ALERT_STATUS"
  'IL_BRANCHES '. "' ORDER_FIELD ' 'ORDER_FIELD ',.
  'IL_BRANCHES '. "" DESCRIPTION ""DESCRIPTION. "
  'IL_BRANCHES '. "" RELATED_LINKS ""RELATED_LINKS"
  'IL_BRANCHES '. "" EXTERNAL_LINK ""EXTERNAL_LINK. "
  'IL_BRANCHES '. "" SEND ""SENT. "
  'IL_BRANCHES '. ' ' CONTENT_1 ' 'CONTENT_1 '.
  OF ' IL_BRANCHES"@STAGING 'IL_BRANCHES ';

  I want to connect view refresh time in other tables when it refreshes

  You can check the last_refresh of the user_snapshot_refresh_times view and the view user_refresh next_date

  You can use it in the below format

  TO_CHAR (last_refresh, "DD-MM-YY HH24:MI:SS) last_refresh

  Anand

• A Clause WITH usable in Materialized View SQL

  Hello
  
  We can use SQL WITH clause Materialized View.
  
  Thank you

  Hello

  Here is an example

  CREATE MATERIALIZED VIEW MV_TEST
  BUILD IMMEDIATE
  REFRESH FORCE ON DEMAND
  AS
  WITH t AS (SELECT owner, object_type, COUNT ( * )
             FROM my_objects
             GROUP BY object_type, owner)
  SELECT *
  FROM t
  WHERE owner IN ('SYS', 'SYSTEM');
  

  Concerning

• Fast refresh materialized view problems

  I have two databases (A and B).
  
  In A database, user NICK has a table called COLOUR_MASTER.
  Also in this database, NICK issues creating materialized command newspaper view colour_master with the primary key, including the new values (and Yes, there is a primary key defined for this table)
  In database B, there is a link of database called A_LINK, connect, Nick, identified by password using 'dbA ';
  In database B, user IAN also creates a materialized view CM_MV cool off quickly in select * from colour_master@A_LINK
  
  This statement is done correctly, and there are several million lines in CM_MV when it's done.
  
  Immediately, IAN issued this command:
  
  Start
  dbms_mview. Refresh ('CM_MV');
  end;
  
  .. .and after a small pause, it gets the error
  
  ORA-12008: error path refresh materialized view
  ORA-02068: following sever error of A_LINK
  ORA-03113: end of file on communication channel
  
  One more + "select count (*) of colour_master@A_LINK" + subject immediately manages to return the correct number of records in the database so A 3113 is a bit misleading, I think that, in this case have crash, the database remains accessible at all times, there is no network problem (database A and B are both located in the same server so it of not like I'm trying of) connect to halfway around the globe).
  
  The only thing I can think is that there is a permissions issue causes this error. The creation of MV because is made via a link, it is not a problem of IAN see all appropriate, but once the updates come into play, it is perhaps.
  
  Any who can shed light on why I can't do the fast refresh from the view, I can create joyfully, please?

  I'm surprised no one asked you to do what is obvious: try to do a select * from colour_master@A_LINK, without that being wrapped in a create materialized MATERIALIZED view. Just do a simple select * from...

  My bet is that you will get an error ORA_22992 can not use selected from the remote tables LOB Locators . And if you can't do a simple select * in a remote table, I suspect that you can reasonably expect Fireworks when you try to create or refresh a view materialized on such a thing!

  Here's a quick test:

  In the 1 database:
  =========

  SQL> create table A (col1 varchar2(2), col2 clob);
  Table created.
  
  SQL> alter table A add constraint A1 primary key (col1);
  Table altered.
  
  SQL> insert into A values ('AA','This is an entry into a clob column');
  1 row created.
  
  SQL> commit;
  Commit complete.
  
  SQL> create materialized view log on A with primary key including new values;
  Materialized view log created.
  

  In the database 2
  =========

  SQL> connect ims_global/v0yager1@ussd
  Connected.
  
  SQL> create materialized view B refresh fast as
    2  select * from A@remotedb_link;
  
  Materialized view created.
  
  SQL> exec dbms_mview.refresh('B');
  BEGIN dbms_mview.refresh('B'); END;
  
  *
  ERROR at line 1:
  ORA-12008: error in materialized view refresh path
  ORA-02068: following severe error from REMOTEDB_LINK
  ORA-03113: end-of-file on communication channel
  ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2251
  ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2457
  ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2426
  ORA-06512: at line 1
  
  SQL> drop materialized view B;
  Materialized view dropped.
  
  SQL> create materialized view B refresh fast as
    2  select col1 from A@ims_link;
  
  Materialized view created.
  
  SQL> exec dbms_mview.refresh('B');
  PL/SQL procedure successfully completed.
  

  Which seems to reproduce your problem rather well, I think.

  I don't know if there is no work around for this. I mean, obviously you can't miss the CLOB column in your statement of 'create a MV' as I just did, but I don't know if you're still allowed or expected to be able to create a MV on lob columns and that such and such correction will allow you to do. Maybe someone else can provide this information.

  But at least you won't have to play Russian roulette with your init.ora parameters!

• Problems with the materialized view

  Hello

  I need help enforce data integrity using a materialized view. In my example, each system can consist of three types of components, and it is modeled using the supertype/subtype relationships. I'm trying to argue that, for a given system, a component cannot reside in more than one table of components. For example, given the system 1, if A component exists in the mobile_components table, it is impossible to insert into the table desktop_components for system 1. Rather than using triggers, I try to use views materialized with unique constraint to enforce this rule based on the example of "The trouble with triggers" article http://www.oracle.com/technetwork/issue-archive/2008/08-sep/o58asktom-101055.html of Tom Kyte. However, I can't seem to make it work because it gives me ORA-12054: cannot set the ON COMMIT refresh attribute.  I use UNION ALL and I know that can be difficult, but I can not understand what are the rules I'm breaking.  I have the necessary privileges.  Oracle 11g.  Can anyone help?

  Thank you

  Mark

  create table systems (
  sys_id number,
  sys_name varchar2(100),
  constraint sys_pk primary key (sys_id),
  constraint sys_uk unique (sys_name));
  
  insert into systems values (1,'System 1');
  insert into systems values (2,'System 2');
  
  
  

  create table mobile_components (
  mo_comp_id number,
  mo_comp_name varchar2(100),
  mo_comp_sys_id number,
  constraint mo_pk primary key (mo_comp_id),
  constraint mo_uk unique (mo_comp_name, mo_comp_sys_id),
  constraint mo_fk foreign key (mo_comp_sys_id) references systems (sys_id));
  
  insert into mobile_components values (1,'Component A',1);
  insert into mobile_components values (2,'Component A',2);
  
  
  

  create table desktop_components (
  de_comp_id number,
  de_comp_name varchar2(100),
  de_comp_sys_id number,
  constraint de_pk primary key (de_comp_id),
  constraint de_uk unique (de_comp_name, de_comp_sys_id),
  constraint de_fk foreign key (de_comp_sys_id) references systems (sys_id));
  
  insert into desktop_components values (1,'Component B',1);
  insert into desktop_components values (2,'Component B',2);
  
  
  

  create table internet_components (
  in_comp_id number,
  in_comp_name varchar2(100),
  in_comp_sys_id number,
  constraint in_pk primary key (in_comp_id),
  constraint in_uk unique (in_comp_name, in_comp_sys_id),
  constraint in_fk foreign key (in_comp_sys_id_ references systems (sys_id));
  
  insert into internet_components values (1,'Component C',1);
  insert into internet_components values (2,'Component C',2);
  
  
  

  create materialized view log on mobile_components with rowid;
  create materialized view log on desktop_components with rowid;
  create materialized view log on internet_components with rowid;
  
  
  

  create materialized view mv_components
  refresh fast on commit with rowid as
  select rowid as row_id, mo_comp_id as comp_id, mo_comp_name as comp_name
  from mobile_components
  union all
  select rowid, de_comp_id, de_comp_name
  from desktop_components
  union all
  select rowid, in_comp_id, in_comp_name
  from internet_components;
  
  alter table mv_components add constraint mv_comp_uk unique (comp_id, comp_name);
  
  
  

  You need a column marker to distinguish which questions you Union, that the data are:

  for example

  Create materialized view mv_components

  cool off quickly on commit with rowid as

  Select 'a' marker, rowid as row_id, mo_comp_id as identifiant_composant mo_comp_name as comp_name

  of mobile_components

  Union of all the

  Select 'b', rowid, de_comp_id, de_comp_name

  of desktop_components

  Union of all the

  Select 'c', rowid, in_comp_id, in_comp_name

  of internet_components;

• Oracle Warehouse builder or materialized views

  I have a requirement as follows:
  
  Requirement:
  We must create a Reporting DB to be used for information and a transactional database will be in separate host. Fundamentally, he need to extract data from a set of transactional DB tables and move to the Reporting DB schema at adequate intervals.
  
  We may have to get a different column data in different tables and store it in a single table / several reports DB tables.
  
  
  Can someone whether to go with Oracle Warehouse builder or the materialized views for this offer please?
  Or use OWB to create and maintain the MVs.
  
  Also please me a link point to what features are available with OWB
  
  Our Oracle is installed in Solaris 10 and one who is perfect either generator warehouse Oracle or materialized views
  
  Thank you
  APPU
  
  Published by: user12094414 on October 25, 2009 21:52
  
  Published by: user12094414 on October 25, 2009 22:17

  user12094414 wrote:
  Can someone whether to go with Oracle Warehouse builder or the materialized views for this offer please?
  Or use OWB to create and maintain the MVs.

  The two are not exclusive. OWB is a tool for designing the data movement and implement updates to the warehouse.

  MVs are a tool integrated into the database in support of materialization of the current request to speed up some types of applications related to data that is availoable, perhaps after transport OWB.

  >

  Also please me a link point to what features are available with OWB

  Normal (to allow the future of mutual aid) access is

  http://OTN.Oracle.com
  -> Products (perma menu on the left): database (link)
  -> Warehouseing Bi & data (link in the middle section)
  -> Related products (product menu on the right): Warehouse Builder
  where you can get a Viewlet, whitepapers, docs, demos, tutorials, etc.

  Direct access to the page above is http://www.oracle.com/technology/products/warehouse/index.html

• Materialized view Eror

  Hello
  
  I created a view of ' cool off quickly on commit "materialized on one of my database table. Everything went well until I've created an on this created MV materialized view log. It was because I needed to create another view of fresh fast depends on the MV created earlier.
  
  After all the transactions made on the base tables began to fail with
  ORA-12034: materialized view log on 'TEMP_1234' younger than the last refresh error.
  
  I've studied a lot of things on that front, but was not able to get a solution. Can you help me please on this?
  
  Thank you.

  Check out this link.

  http://oraclesponge.blogspot.com/2005/12/ora-12034-MATERIALIZED-view-log.html

  http://asktom.Oracle.com/pls/asktom/f?p=100:11:0:P11_QUESTION_ID:349809082244

  In the second search for link for the post of David Aldrige dated June 9, 2006 and the immediate follow-up to Tom.

  I hope this helps.

  Concerning

  REDA

• effect of pump or etl data on the materialized view logs

  Hi, we are mobile/upgrading an instance of 10g to 12 c, where one materialized view logs and expect to do one of the following:

  (1) extract/import the meta, only using data pump data and move data using an etl tool

  (2) comprehensive database extract/import using the data pump in

  are there questions that we must be aware of when the displacement of these with either scenario materialized view logs?

  Thanks for any information you can provide.

  > are there questions that we should be aware of when the displacement of these materialized view logs with either scenario?

  No problem

• create materialized view log on the table without a primary key

  Hi all

  CREATE TABLE client_months 
  (
    SUBJ_CODE         NUMBER(4),
    SERV_CODE         NUMBER(4),
    DEBIT_CODE        NUMBER(4),
    PERIOD_NUM        NUMBER(2),
    PERIOD_NAME       VARCHAR2(40 CHAR),
    FIRST_MON_DAY     DATE,
    LAST_MON_DAY      DATE,
    VALUE_MON_DAY     DATE,
    MONTHES           NUMBER(4,2),
    GARDENING_WEIGHT  NUMBER(5,4),
    REASON_CODE       NUMBER(5),
    STAMP_ACTION      VARCHAR2(1 CHAR),
    STAMP_CDATE       DATE                        DEFAULT SYSDATE,
    STAMP_DATE        DATE,
    STAMP_USER        VARCHAR2(15 CHAR),
    REGION_CODE       NUMBER(9)
  )
  table created.
  
  CREATE UNIQUE INDEX client_months_UK  ON client_months 
  (SUBJ_CODE, SERV_CODE, DEBIT_CODE, PERIOD_NUM, REGION_CODE)
  index created.
  
  CREATE MATERIALIZED VIEW LOG ON client_months with rowid;
  
  CREATE MATERIALIZED VIEW client_months_mv 
  BUILD immediate 
  REFRESH FAST ON COMMIT 
  AS 
  SELECT * FROM client_months;
  
  ORA-12014: table 'CLIENT_MONTHS' does not contain a primary key constraint

  I don't want to refresh the mview when validation is performed on the base table.
  And I don't want to change the base table by adding a primary key.
  
  is it possible to create the mview journal using the unique index? or another solution?
  Please help
  Thanks in advance
  Naama

  Naamas wrote:
  No,
  I already read this post!

  Then you read wrong:

  SQL> CREATE TABLE client_months
    2  (
    3    SUBJ_CODE         NUMBER(4),
    4    SERV_CODE         NUMBER(4),
    5    DEBIT_CODE        NUMBER(4),
    6    PERIOD_NUM        NUMBER(2),
    7    PERIOD_NAME       VARCHAR2(40 CHAR),
    8    FIRST_MON_DAY     DATE,
    9    LAST_MON_DAY      DATE,
   10    VALUE_MON_DAY     DATE,
   11    MONTHES           NUMBER(4,2),
   12    GARDENING_WEIGHT  NUMBER(5,4),
   13    REASON_CODE       NUMBER(5),
   14    STAMP_ACTION      VARCHAR2(1 CHAR),
   15    STAMP_CDATE       DATE                        DEFAULT SYSDATE,
   16    STAMP_DATE        DATE,
   17    STAMP_USER        VARCHAR2(15 CHAR),
   18    REGION_CODE       NUMBER(9)
   19  )
   20  /
  
  Table created.
  
  SQL> CREATE UNIQUE INDEX client_months_UK  ON client_months
    2  (SUBJ_CODE, SERV_CODE, DEBIT_CODE, PERIOD_NUM, REGION_CODE)
    3  /
  
  Index created.
  
  SQL> CREATE MATERIALIZED VIEW LOG ON client_months with rowid
    2  /
  
  Materialized view log created.
  
  SQL> CREATE MATERIALIZED VIEW client_months_mv
    2  BUILD immediate
    3  REFRESH FAST WITH ROWID ON COMMIT -- pay attention to WITH ROWID
    4  AS
    5  SELECT * FROM client_months
    6  /
  
  Materialized view created.
  
  SQL>
  

  SY.

• help a single master more editable site materialized views

  Hello world
  
  I have a solution in which I have 5 sites.
  I decided to implement a single site of master with 4 updatable materialized view sites.
  The reason why I made this decision, it's I want that if my main site does not work, the materialized view sites don't update with other data.
  My question is in this situation if the main site became unavailable can be update view materialized sites update their own individually and after master site data become available, they send their data to that or not, they can query just to their own database until the main site are available?
  
  Thank you

  Hello

  Yes, what you think is correct. Mviews update can run locally even if the primary site is unavailable. She can push further data on the master site when the main site is available.

  The mviews update can be updated even if the primary site is unavailable. But the changes that happened on the site controller is not updated until it becomes available and an update is performed.

  Thank you
  Florent

• Materialized with dynamic input possible view?

  Hello

  We have some end users have a very complex query of SQL reports (~ 2500 lines) they came with.  We are trying to tune and to create additional indexes as needed.  He has made more than one aggregation of xml and the chain in select statements.  in any case while I'm looking for other methods deal with the problem regardless of a potentially inefficient SQL query.

  In my opinion, they said that the query taking ~ 6000 sec to finish and basically http sessions expire of their web application after 4000 seconds of inactivity.  They have a few dynamic user input from the web page which is fed in the request for multiple WHERE clauses.  So I think we want to have this query that is run in offline mode (after the user input is collected) as well as the results stored in a table, then the wep app can do a simple select query to retrieve data from the table of results later.

  Is there a way to create a materialized view and replace user with some variables bind input and update the values of the variables bind with the participation of the user whenever they want the data, and then refresh the materialized view?  Or if there is a better mechanism for Oracle to run asynchronously this query offline with dynamic input and then store the results in a table?  My problem is that I don't know if they can call a sp and feed the bind values as parameters, but maybe I need to force them to.  I really don't want to process SQL statements dynamic that their request is so great andt hey asked me on GTT, but I was under the impression that the data is lost after each session and probably wouldn't really solve anything.  Thoughts?

  
  

  Oracle Database 11 g Enterprise Edition Release 11.2.0.4.0 - 64 bit Production

  Web pages should return something in<5s or="" the="" end-user="" will="" hit="" the="" refresh="" button="" again="" and="" again="" and="" again="" and="">

  Do something like this:

  • store the query to run the sql in a table with the values for the variables bind (parent table)
  • run the SQL in the background via DBMS_SCHEDULER
  • store the results in a partitioned table. (child table) (I assume a large amount of data)
    • for example, use a partition of range interval by sequence ID 1. of the parent
  • update the parent with the status table "Hey, I'm made.
  • Maybe the applicant send an email.
  • Web page queries only the parent table.
  • a scheduled task removes the no-more-required data through DROP PARTITION.

  MK

• You want to capture update dates, with trigger on a view to refresh quickly materialized. But trigger on MV consider inserting and updates are inserts only.

  Oracle Database 11 g Enterprise Edition Release 11.2.0.4.0 - 64 bit Production

  PL/SQL Release 11.2.0.4.0 - Production

  CORE Production 11.2.0.4.0

  AMT for Linux: Version 11.2.0.4.0 - Production

  NLSRTL Version 11.2.0.4.0 - Production

  I create the structure of the table like that.

  create table test1 (a primary key, b (2) char number, date c, d varchar2 (10), date of e);

  create table test2 (number of ab, cd (2) tank, date of the ef, gh varchar2 (10), date of the ij, kl varchar2 (100));

  Create materialized view log on test1;

  create materialized view fast refresh test1_v on commit in select * from test1;

  I have create a trigger of the sample

  CREATE OR REPLACE TRIGGER test1_trig

  AFTER INSERT OR UPDATE OR DELETE

  ON test1_v

  FOR EACH LINE

  DECLARE

  lr_test2 test2% ROWTYPE;

  lv_error VARCHAR2 (4000);

  BEGIN

  lr_test2. AB: =: NEW.a;

  lr_test2. CD: =: NEW.b;

  lr_test2. GH: =: NEW.d;

  IF THE INSERTION

  THEN

  lr_test2. EF: = SYSDATE;

  lr_test2.IJ: = SYSDATE;

  lr_test2.KL: = 'INSERT ';

  INSERT INTO test2

  VALUES lr_test2;

  ELSIF UPDATE

  THEN

  lr_test2.IJ: = SYSDATE;

  lr_test2.KL: = 'UPDATE ';

  UPDATE test2 = lr_test2 ab WHERE = LINE: OLD.a;

  ELSIF REMOVAL

  THEN

  DELETE FROM test2

  AB = WHERE: old.a;

  END IF;

  EXCEPTION

  WHILE OTHERS

  THEN

  lv_error: = SQLERRM;

  INSERT INTO XXDOMINO_FG_DATA_LOAD_ERROR

  VALUES ('test1_trig',

  : OLD.a,.

  "test1_trig,"

  LV_ERROR,

  SYSDATE);

  COMMIT;

  END test1_trig;

  /

  So, if check you my code,.

  When I insert EF = SYSDATE, IJ = SYSDATE.

  Update EF is not changed, IJ = SYSDATE.

  So I like to capture their insertion and update dates.

  But if updates or insert arrives on the materialized table. The trigger themselves as an INSERT only.

  So how do you capture the updates?

  I use the statemnet with out merger with performance and also able to capture the update dates.

  CREATE OR REPLACE TRIGGER test1_trig_merge

  AFTER INSERT OR UPDATE OR DELETE

  ON test1_v

  FOR EACH LINE

  DECLARE

  lr_test2 test2% ROWTYPE;

  lv_error VARCHAR2 (4000);

  BEGIN

  IF THE REMOVAL

  THEN

  DELETE FROM test2

      AB = WHERE: old.a;

  ELSIF INSERTION

  THEN

  MERGE INTO test2 one

  B using (SELECT 1 FROM DUAL)

  WE (ab =: new.a)

  WHEN MATCHED

  THEN

  UPDATE the VALUE ab =: NEW.a.

  CD =: NEW.b,

  GH =: NEW.c

  IJ = SYSDATE,

  KL = "Update"

  AB WHERE =: old.a

  WHEN NOT MATCHED

  THEN

  INSERTING VALUES (: NEW.a,)

  : NEW.b,.

  : NEW.c.

  : NEW.d,.

  : NEW.e,.

  "INSERT");

  END IF;

  EXCEPTION

  WHILE OTHERS

  THEN

  lv_error: = SQLERRM;

  INSERT INTO XXDOMINO_FG_DATA_LOAD_ERROR

  VALUES ('test1_trig',

  : OLD.a,.

  "test1_trig,"

  LV_ERROR,

  SYSDATE);

  END test1_trig_merge;

  /

  DISPLAY ERRORS;

• Problem with a complete refresh materialized view when using rownum

  Hi all

  I had a problem with rownum when complete using Refresh

  I use rownum when you create the materialized view, and this is the generation properly. But the question was when I even refreshing, rownum was not get sorted in ascending order.

  anyone encountered this scenario

  rownum is determined as the line came out, also "order by rownum" does absolutely nothing.

  http://docs.Oracle.com/CD/B19306_01/server.102/b14200/pseudocolumns009.htm

• Materialized view does not quickly refresh with sysdate in where clause

  Hi all

  I am trying to create a view, materialized with sysdate in where clause. This makes the complex query, and so I can't create a quick refreshment mview.

  I tried to create with rowid too, but it does not create a quick refreshment.

  I was wondering if someone can advise me, how can I accomplish this task, which would be really appreciated.

  The query is:

  create a materialized view PS_MEETING

  build the DEFERRED payment

  Refresh quickly with rowid

  as

  SELECT *.

  MEETING M

  WHERE state_desc = 'VIC '.

  OR Meet_date < TRUNC (SYSDATE);

  the behavior is documented: http://docs.oracle.com/cd/E11882_01/server.112/e25554/basicmv.htm#DWHSG8201

  General restrictions on update quickly

  The definition of the materialized view query is limited as follows:

  • The materialized view must not contain references to non-repetitive phrases such as SYSDATE and ROWNUM .

  So I guess that you would need a more static than sysdate condition - or another strategy update.

• With as subquery block in create MATERIALIZED view or bulk pl/sql

  Hi all
  
  Can I use the with as subquery block in create MATERIALIZED view?
  
  or in pl/sql
  
  
  
  -Thank you
  
  Published by: xwo0owx on March 31, 2011 11:23
  
  Published by: xwo0owx on March 31, 2011 11:23

  Have you tried to test it? :)

  SQL > SELECT * FROM V$VERSION;
  
  BANNER
  --------------------------------------------------------------------------------
  Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
  PL/SQL Release 11.2.0.2.0 - Production
  CORE    11.2.0.2.0      Production
  TNS for 32-bit Windows: Version 11.2.0.2.0 - Production
  NLSRTL Version 11.2.0.2.0 - Production
  
  SQL > CREATE VIEW TEST_VIEW
    2  AS
    3  WITH d AS
    4  (
    5          SELECT * FROM DUAL
    6  )
    7  SELECT *
    8  FROM   d
    9  ;
  
  View created.
  
  SQL > SELECT * FROM test_view;
  
  D
  -
  X
  
  SQL > DECLARE
    2          x DUAL.DUMMY%TYPE;
    3  BEGIN
    4          WITH d AS
    5          (
    6                  SELECT * FROM DUAL
    7          )
    8          SELECT dummy
    9          INTO   x
   10          FROM   d
   11          ;
   12
   13          DBMS_OUTPUT.PUT_LINE(x);
   14  END;
   15  /
  X
  
  PL/SQL procedure successfully completed.