How about removing the public synonym and create a private one in the schemas that
need it. Except for a table or procedure that is truly global, making a public synonym
is never a good idea.
>>> "Nisha Patel" <[EMAIL PROTECTED]> 02/13/01 09:55AM >>>
Hi All,
I have a really wierd problem with a client who has tried to export the
whole database. They get errors because there is
a public synonym called System created by a user FCAADMIN. This public
synonym caused several oracle supplied objects to go invalid resulting
in the failed Oracle exports. I know we should not have a table called
System but I had inherited the database and it is too late in the game
to rename it. Does anyone have any solution to this problem?
Thanks in advance,
Nisha
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Nisha Patel
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: William Beilstein
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
