Accessing new data source objects
To access new data source objects, you must create nicknames for them. Use the CREATE NICKNAME statement for data sources that do not have nicknames.
Before you begin
The federated system must be configured to access the data source.
A server definition for the data source server on which the object resides must exist in the federated database. You create a server definition with the CREATE SERVER statement.
To insert, update, or delete data with a nickname, all of the following privileges must be true:
- The privileges held by the authorization ID of the statement must include the necessary SELECT, INSERT, UPDATE, and DELETE privileges on the nickname for the federated database to accept the request.
- The user ID at the data source must have the necessary SELECT, INSERT, UPDATE, and DELETE privileges on the underlying table object for the data source to accept the request.
- The user ID at the data source must be mapped to the authorization ID at the federated server through a user mapping.
You must have the required authorizations for the CREATE NICKNAME statement.
- SYSADM or DBADM
- IMPLICIT_SCHEMA authority on the federated database, if the implicit or explicit schema name of the nickname does not exist
- CREATEIN privilege on the schema, if the schema name of the nickname exists
About this task
Periodically, you need to access data source objects that lack nicknames. These might be new objects added to a data source, such as a newly created view. These might be existing objects that were not registered with the federated server when it was initially setup. In either case, you must create a nickname for the object.
Issue the CREATE NICKNAME statement to access new data source objects.