The interesting thing I've since tried is that it will work on our production database
(which is Novell 8.1.5.0.4), but not on the archive (NT 8.1.5.0.0) or the test one
(which was made from an export of the archive) that I'm trying to set up.
The archive was made from a backup of the former pr
Ian,
You are correct. If you're connected as FARS_OWNER
the public synonym will not be referenced since you
own a table named MFGALIASTYPE.
I suspect the error is not being signaled by the
insert itself, but by some underlying recursive sql.
Is there a trigger on this table? If not, the trace
Why would 0racle even consider the public synonym? I thought this might be a
materialized view, but I would expect to see an
undefined object type.
Ian MacGregor
-Original Message-
Sent: Friday, May 04, 2001 8:21 AM
To: Multiple recipients of list ORACLE-L
Are you sure the public syn
..or that the public synonym is really pointing at the object you think it is?
>>> [EMAIL PROTECTED] 05/03/01 04:55PM >>>
Why do I keep getting this error even though this object is not a view??? I am in as
the owner of the table, which has the DBA role to boot.
SQL> show user
USER is "FARS_OW
Are you sure the public synonym isn't pointing to an object in some other database
thru a link?
>>> [EMAIL PROTECTED] 05/03/01 04:55PM >>>
Why do I keep getting this error even though this object is not a view??? I am in as
the owner of the table, which has the DBA role to boot.
SQL> show user
Why do I keep getting this error even though this object is not a view??? I am in as
the owner of the table, which has the DBA role to boot.
SQL> show user
USER is "FARS_OWNER"
SQL> select owner, object_name, object_type from dba_objects where object_name like
'%ALIASTYPE%';
OWNER OBJECT_NA
