A synonym is an alias for a database object (such as a table, view, materialized view, sequence, stored procedure, function, package, type, or user-defined type). You can also create synonyms for other synonyms. A synonym is just an alias and does not occupy any space. This topic describes the types, basic characteristics, and privileges of synonyms.
Types
Synonyms are classified into public synonyms and private synonyms.
Public synonyms are in the PUBLIC group and can be accessed by all users. Private synonyms are owned by the object owner and can be accessed by other users only if they are explicitly authorized.
Public synonyms are usually created by DBAs. If a regular user wants to create a public synonym, they must have the CREATE PUBLIC SYNONYM system privilege.
Basic characteristics
Synonyms extend the usability of databases, enabling seamless interaction between different database users. They are often used to simplify object access and enhance the security of object access.
Create a synonym
The CREATE SYNONYM statement is used to create a synonym. The syntax is as follows:
CREATE [ OR REPLACE ] [ PUBLIC ]
SYNONYM [ schema. ]synonym
FOR [ schema. ]object;
Parameter description
| Parameter | Description |
|---|---|
| OR REPLACE | Indicates that if a synonym with the specified name already exists, it will be replaced with the new definition. |
| PUBLIC | Specifies to create a public synonym, which can be used by all users. Users must have the necessary privileges on the underlying object to use this synonym. During reference resolution of an object, public synonyms are used only when the object does not specify a schema. If PUBLIC is not specified, the synonym is private, accessible only within the current schema, and the synonym name must be unique within the current schema. |
| [schema. ]synonym | The schema specifies the owner of the synonym. If PUBLIC is specified, the owner cannot be specified for the synonym. synonym indicates the name of the synonym. |
| [schema. ]object | Indicates the name of the object that the synonym refers to. |
After a synonym is created, you can view it in the USER_SYNONYMS, ALL_SYNONYMS, or DBA_SYNONYMS view.
Examples
Create a private synonym.
obclient> CREATE TABLE t1(c1 INT); obclient> CREATE SYNONYM s1 FOR t1; obclient> INSERT INTO s1 VALUES(1); obclient> SELECT * FROM s1; +------+ | c1 | +------+ | 1 | +------+ 1 row in setCreate a public synonym.
obclient> CREATE PUBLIC SYNONYM syn_pub FOR t1; obclient> SELECT * FROM syn_pub; +------+ | c1 | +------+ | 1 | +------+ 1 row in set
Drop a synonym
The DROP SYNONYM statement is used to drop a synonym. The syntax is as follows:
DROP [PUBLIC] SYNONYM [ schema. ]synonym;
Parameters
| Parameter | Description |
|---|---|
| PUBLIC | Specifies to drop a public synonym. If you do not specify PUBLIC, a private synonym is dropped. |
| [ schema. ]synonym | Schema specifies the user to which the synonym belongs. If you specify PUBLIC, you cannot specify a user for the synonym. synonym specifies the name of the synonym. |
Examples
Drop a private synonym.
obclient> DROP SYNONYM test.s1; Query OK, 0 rows affectedDrop a public synonym.
obclient> DROP PUBLIC SYNONYM syn_pub; Query OK, 0 rows affected
Considerations
To create a synonym, you must meet the following privilege requirements:
To create a private synonym in the current user's schema, you must have the
CREATE SYNONYMprivilege.To create a private synonym in a schema other than the current user's schema, you must have the
CREATE ANY SYNONYMprivilege.To create a
PUBLICsynonym, you must have theCREATE PUBLIC SYNONYMprivilege.You do not need the privilege to access the object for which you want to create a synonym.
/*Connect to the sys user.*/
obclient> CREATE USER syn_user IDENTIFIED BY syn_user;
obclient> GRANT CREATE ON syn_user.* TO syn_user;
obclient> GRANT SELECT ON syn_user.* TO syn_user;
/*Connect to the syn_user account and create a synonym, which fails.*/
obclient> CREATE SYNONYM syn_1 FOR t1;
ERROR-00600: internal error code, arguments: -5036, Access denied; you need (at least one of) the CREATE SYNONYM privilege(s) for this operation
/*Connect to the sys user and grant the CREATE SYNONYM privilege.*/
obclient> GRANT CREATE SYNONYM ON *.* TO syn_user;
/*Connect to the syn_user account and create a synonym.*/
obclient> CREATE SYNONYM syn_1 FOR t1;