Oracle Distributed Systems

Administrative Accounts, Privileges, and Database Links

Depending on whether you are running Oracle7 or Oracle8 and which security model you choose to follow, the account-creation process can be simple or tedious. In Oracle7, you have the choice of either mirrored user access or global access. In Oracle8, the management of user accounts is substantially easier; you need only to create propagator and receiver accounts. Regardless of which model you choose or which Oracle version you are using, the proper configuration of accounts, privileges, and database links is crucial. In this section we provide step-by-step procedures you can follow.

Note

In all cases, the creation of administrative accounts and database links requires that you have already run the catalog scripts catproc.sql, catrep.sql, and optionally catrepad.sql.

Configuring Oracle7 for the Mirrored User Access Model

As its name implies, the mirrored user access model requires that every database have an account for every user who is allowed to perform DML against replicated tables. The onus of creating accounts for all of these users in multiple databases lies with the DBA, who must also ensure that these accounts have the same passwords in each database. In addition, these user accounts require EXECUTE privileges on the generated replication support packages for each replicated object they can manipulate. These privileges must be directly granted, not inherited through a database role. Each of these accounts also requires ...