Re: 19.3 - Hard Coded Schema Names Issue

From: Maxim <mdemenko_at_gmail.com>
Date: Thu, 18 Mar 2021 20:43:38 +0100
Message-ID: <CAFP4yMwTu_oX1sqP8KMWzTibyghjUuvaetOV0GDAVihuzTyhag_at_mail.gmail.com>



I can't reproduce your issue:

SQL> connect schemaname/schemaname
Connected.
SQL> select banner from v$version;

BANNER



Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production

SQL> CREATE VIEW TEST_VW AS SELECT * FROM schemaname.TEST;

View created.

I would probably enable 10046 to see, what happens.

Regards

Maxim

On Thu, Mar 18, 2021 at 8:06 PM Dave Morgan <oracle_at_1001111.com> wrote:

> Hello all,
>
> connect schemaname
>
> CREATE VIEW TEST_VW AS SELECT * FROM schemaname.TEST;
>
> will result in
> ERROR at line 1:
> ORA-02000: missing VIEW keyword
>
> Removing the hard coded schema name removes the issue. I have
> long had a policy of no hard coded schema names so this did not
> affect us much, however, this seems a rather large change.
>
> Or am I missing something, a configuration setting, documentation?
> That is usually the case.
>
> TIA
> Dave
>
> --
> Dave Morgan
> Senior Consultant, 1001111 Alberta Limited
> dave.morgan_at_1001111.com
> 403 399 2442
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Mar 18 2021 - 20:43:38 CET

Original text of this message