If you do so, then all PL/SQL units that use that name will be invalidated. Take care not to create a public synonym with the same name as an existing schema.
If you create a public synonym and it subsequently has dependent tables or dependent valid user-defined object types, then you cannot create another database object of the same name as the synonym in the same schema as the dependent objects. Notes on Public Synonyms The following notes apply to public synonyms: A private synonym name must be unique in its schema. If you omit this clause, then the synonym is private and is accessible only within its schema. When resolving references to an object, Oracle Database uses a public synonym only if the object is not prefaced by a schema and is not followed by a database link. However each user must have appropriate privileges on the underlying object in order to use the synonym. Public synonyms are accessible to all users. Specify PUBLIC to create a public synonym. Restriction on Replacing a Synonym You cannot use the OR REPLACE clause for a type synonym that has any dependent tables or dependent valid user-defined object types. Use this clause to change the definition of an existing synonym without first dropping it. Specify OR REPLACE to re-create the synonym if it already exists. To create a PUBLIC synonym, you must have the CREATE PUBLIC SYNONYM system privilege.ĭescription of the illustration create_synonym.gif To create a private synonym in another user's schema, you must have the CREATE ANY SYNONYM system privilege. To create a private synonym in your own schema, you must have the CREATE SYNONYM system privilege. See Also: Oracle Database Concepts for general information on synonyms
0 kommentar(er)
