Skip to main content

No subqueries allowed in materialized view? No problem!

Have you ever run into the following error when trying to create a materialized view?
ORA-22818: subquery expressions not allowed here
Yes, it is true: you cannot have a scalar subquery in the SQL statement used to create your materialized view. Here's an example of what won't work (note: I am not claiming this query makes any sense):
CREATE MATERIALIZED VIEW hr_demo_mv
AS
     SELECT employee_id,
            (SELECT MAX (hire_date)
               FROM employees ce) maxhd
       FROM employees t
/

ORA-22818: subquery expressions not allowed here
22818. 00000 -  "subquery expressions not allowed here"
*Cause:    An attempt was made to use a subquery expression where these
           are not supported.
*Action:   Rewrite the statement without the subquery expression.
Rewrite my query without the subquery expression? But I just spent an hour putting it all together. Works great. Gives me exactly the results I want and need. Rewrite it? ARGH.

Calm yourself. While it is true that you will need to "rewrite the statement" that you provide in your CREATE MATERIALIZED VIEW statement, you will not have to abandon your subqueries and all your hard work.

All you have to do is create a view with the subqueries, and then create your materialized view based on the view:
CREATE VIEW hr_demo_v
AS
     SELECT employee_id,
            (SELECT MAX (hire_date)
               FROM employees ce) maxhd
       FROM employees t
/

View HR_DEMO_V created.

CREATE MATERIALIZED VIEW hr_demo_mv
AS
     SELECT * FROM hr_demo_v
/

Materialized view HR_DEMO_MV created.
I recommend this approach (the materialized view is "nothing more" than a select from a view), even if your materialized view query does not contain a subquery or anything else that would preclude the materialized view from being created.

By taking this approach, you can change the contents of the materialized view with the next refresh by doing nothing more than changing the query (instead of dropping and re-creating the materialized view).
Labels:

Comments

  1. Erik van RoonAugust 10, 2017 at 1:26 PM

    That is pretty cool. Thanks!

    And it's so simple it makes me feel stupid for not thinking of this myself. Thanks for that too ;-)

    I am definitely going to use this, starting tomorrow morning.

    ReplyDelete
  2. iudithAugust 11, 2017 at 12:23 AM

    Hello Steven, All,

    When using the approach of basing a naterialized view on a view instead of directly on the base tables,
    you should be aware that this automatically makes the materialized view to be considered COMPLEX,
    and thus NOT fast refreshable.

    This is true even for very simple views, like for example a view that selects all the columns of a single table.

    That is, if the table has a materialized view log defined, then a materialized view based directly on the table
    will be fast-refreshable, while a materialized view based on a view that selects from the table will NOT be fast-refreshable.

    This behavior may be relevant or not, based, of course, on the specifics and performance requirements of your application.


    Thanks a lot & Best Regards,
    Iudith

    ReplyDelete
    Replies
    1. Steven FeuersteinAugust 11, 2017 at 3:53 AM

      Thanks for pointing that out, Iudith.

      Delete
    2. AnonymousJanuary 2, 2018 at 5:07 PM

      Hi everyone, following-up on this thread:

      I just learned about Materialized View today and encountered the same issue in this post. As Steven suggested, I built the MV above a View. But @iudith mentioned that this won't enable the fast-refresh. My questions are:
      1. By default, how is MV refreshed by the system? Is it by period of time or something else?
      2. Since the fast-refresh is not possible, is there a way to regularly update the MV? I will appreciate it if someone can refer me to a good tutorial for beginner about this. The Oracle Docs is a bit overwhelming ...

      Danny

      Delete
    3. Steven FeuersteinJanuary 2, 2018 at 5:10 PM

      Danny, check out Tim Hall's article on materialized views.

      https://oracle-base.com/articles/misc/materialized-views

      On the Oracle Dev Gym (devgym.oracle.com) we use DBMS_SCHEDULER to run jobs daily and weekly to refresh materialized views.

      Delete
  3. AnonymousAugust 11, 2017 at 4:41 AM

    ok, this query doesn't make any sense, however, the "GROUP BY"-part of it doesn't even make any sense at all.
    It should be left away because it might be confusing

    ReplyDelete
    Replies
    1. Steven FeuersteinAugust 11, 2017 at 4:47 AM

      Ha! Excellent point. That was left over from an earlier iteration of the query. I will remove it.

      Delete
  4. AnonymousJanuary 25, 2018 at 8:33 AM

    I just wonder how annoying it might get later on, when you figure out, that changing of query actually does not work in changing of your MV_ contents, and it also stops to refresh.

    Or that when you add column into view query, this will not automatically add column into MV_ ...

    ReplyDelete
  5. AnonymousMarch 15, 2018 at 4:34 AM

    This comment has been removed by a blog administrator.

    ReplyDelete
  6. AnonymousApril 12, 2018 at 12:59 AM

    That's exactly what I needed. It works perfectly!

    ReplyDelete
  7. AnonymousJuly 2, 2019 at 6:07 PM

    This just pushed the error farther down - I'm working in peoplesoft and got the same error when I tried to build the materialized view from the view with subqueries as suggested above - "Warning: named view in FROM list not supported for this type MV" and "Warning: named view in FROM list not supported for this type MV"

    ReplyDelete
  8. modawanatyFebruary 17, 2020 at 1:34 AM

    Thank you Steven this workaround was a great help.

    ReplyDelete
  9. RodneyNovember 2, 2020 at 12:56 PM

    Hi Steven - Just wanted to say many thanks for this!! I spent a few days toiling with a materialized view trying to re-write it. Then I also got this idea to make part of the materialized view simply into a view.

    I didnt have any proof, or a comfort level doing it but after reading your blog I'm more confident that this is the best that can be done :)

    ReplyDelete
    Replies
    1. StevenNovember 2, 2020 at 1:18 PM

      Glad to hear it, Rodney! Thanks for sharing your experience.

      Delete

Post a Comment

Popular posts from this blog

Quick Guide to User-Defined Types in Oracle PL/SQL

A Twitter follower recently asked for more information on user-defined types in the PL/SQL language, and I figured the best way to answer is to offer up this blog post. PL/SQL is a strongly-typed language . Before you can work with a variable or constant, it must be declared with a type (yes, PL/SQL also supports lots of implicit conversions from one type to another, but still, everything must be declared with a type). PL/SQL offers a wide array of pre-defined data types , both in the language natively (such as VARCHAR2, PLS_INTEGER, BOOLEAN, etc.) and in a variety of supplied packages (e.g., the NUMBER_TABLE collection type in the DBMS_SQL package). Data types in PL/SQL can be scalars, such as strings and numbers, or composite (consisting of one or more scalars), such as record types, collection types and object types. You can't really declare your own "user-defined" scalars, though you can define subtypes  from those scalars, which can be very helpful from the p
24 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch,
4 comments
Read more

Working With JSON Arrays in PL/SQL

Oracle Database 12c Release 2 built upon the 12.1 SQL/JSON features by adding a number of builtin object types (similar to classes in object-oriented languages) for manipulating JSON data in PL/SQL blocks. In this post, I explore some of the array-oriented JSON features, all made available through the JSON_ARRAY_T type and its methods. Just like a class, an object type offers a pre-defined constructor function to instantiate new instances of that type, static methods and member methods. Here are the methods you are most likely to use: A couple of things to remember, generally, about working with JSON elements generally and JSON arrays specifically in PL/SQL: Error Handling Behavior By default, if an error occurs when you call a member method for your JSON array (or object), NULL is returned. In other words, an exception is not  raised back to your block. If you want errors to be propagated from the method as an exception, call the ON_ERROR method and pass a value greate
Post a Comment
Read more