SYS_RUN_REPLICATION_ROLE system role

Users with the SYS_RUN_REPLICATION_ROLE system role have full administrative privileges on the database only when connecting from SQL Remote. SQL Remote users have full access to the database and can make changes specified in the messages. Only users with this privilege can run SQL Remote.

The SYS_RUN_REPLICATION_ROLE system role has the following properties:

No distinct privileges when not connected from SQL Remote A user granted the SYS_RUN_REPLICATION_ROLE system role cannot exercise the privileges inherited from this role on any connection apart from SQL Remote or dbmlsync. Therefore, even if the user name and password for a user with the SYS_RUN_REPLICATION_ROLE system role are widely distributed, there are no security issues. As long as the user name has no privileges beyond CONNECT granted on the database, no one can use this user name to access data in the database.
Full database administration privileges from SQL Remote When connecting from SQL Remote, a user with SYS_RUN_REPLICATION_ROLE system role has full database administration privileges on the database.

When to grant the SYS_RUN_REPLICATION_ROLE system role

It is recommended that when you are creating users on the consolidated database that you grant the SYS_RUN_REPLICATION_ROLE system role to the publisher of the consolidated database and to each remote user. When a remote database is extracted by the Extraction utility (dbxtract) or the Extract Database Wizard, the remote user becomes the publisher of the remote database, and is granted the PUBLISH privilege and the SYS_RUN_REPLICATION_ROLE system role.

This recommendation simplifies the administration of users. Each remote user only needs one user name to connect to the database, whether from the SQL Remote (which provides the user with the SYS_RUN_REPLICATION_ROLE system role) or from any other client application (in which case the SYS_RUN_REPLICATION_ROLE system role grants the user no extra privileges).

Note

GRANT REMOTE DBA is a deprecated statement. Use GRANT ROLE SYS_RUN_REPLICATION_ROLE instead. See GRANT ROLE SYS_RUN_REPLICATION_ROLE statement [MobiLink] [SQL Remote].