Re: Materialized Views

From: The Magnet <art_at_unsu.com>
Date: Thu, 15 Apr 2010 10:42:30 -0700 (PDT)
Message-ID: <57abad0c-82ca-404c-b6bb-e7a8a80a6cfa_at_r18g2000yqd.googlegroups.com>

On Apr 15, 12:36 pm, "Michel Cadot" <micadot{at}altern{dot}org> wrote:
> "The Magnet" <a..._at_unsu.com> a écrit dans le message de news: 059a76ea-1b9d-486d-bd56-ae3857f9b..._at_w17g2000yqj.googlegroups.com...
> |
> | We're about at the end of our rope.  We have a script that runs at
> | night and re-created some materialized view.  The SQL simple drops the
> | view and re-creates it.
> |
> | However, each night a different view fails to be created.  The view is
> | dropped, but when attempting we'll get a ORA-00955:
> |
> |  FROM analyst a, broker b, master_table m, (
> |       *
> | ERROR at line 14:
> | ORA-00955: name is already used by an existing object
> |
> | How can you get that error on a SELECT??  And, it is different every
> | time.  I thought is was timing, but that is not it.
> |
> | Suggestions?
>
> Because the optimizer generates intermediate memory views and
> unfortunatly (and bugly) it generates trwice the same name.
>
> Regards
> Michel

If this is true, the I have 2 questions:

1. Why does it not happen to every view
2. How to get around it?

We have 7 views which we create.

Thanks. Received on Thu Apr 15 2010 - 12:42:30 CDT