Oracle Replication Manager Version 1.6.0.0.0
Release Notes
June 1998
These Release Notes update the documentation
included with Oracle Replication Manager Version 1.6.0.0.0 for
the Oracle Server 8.0.5 release.
NOTE: Oracle Replication Manager and
Oracle Enterprise Manager are trademarks of Oracle Corporation.
General Information
Oracle Replication Manager runs as an integrated application within Oracle Enterprise Manager,
or as a stand-alone program.
Oracle Replication Manager requires an Oracle Database Version of 7.3 or greater on which
Advanced Replication has been installed.
If you are using Oracle Enterprise Manager
along with Oracle Replication Manager, read the release notes
for Oracle Enterprise Manager as well.
This version is designed for use under
the following operating systems: Windows NT 4.0 and Windows
95.
Recommended Use
Oracle Corporation recommends that the
replicated environment be administrated by a single Replication
Administrator who makes changes to one site at a time.
Oracle Replication Manager should be
used to establish connections to databases that already have replication
support installed. In addition the "Administrator" that
establishes the connection should have been granted permissions
appropriate to a "Replication Administrator" using the
dbms_repcat_admin.grant_admin_any_schema() API call. This can
be done using the "Setup Wizard" on the "File"
menu.
Troubleshooting
The Replication Administrator should check the "Admin Requests" to troubleshoot possible error conditions. Many events in a replicated environment occur asynchronously. If your environment appears to be out of sync, ensure that your requests have completed successfully:
1. Expand the tree view of a database.
2. Expand the tree view of Configuration.
3. Click Master Groups to display Master Groups in the tree view window.
4. Click a Master Group to display
Admin Requests.
Command Line options
If you pass a connection string (username/password@databasename),
such as scott/tiger@sales_headquarters, then Oracle Replication
Manager will automatically establish that connection when it starts
up eliminating the need to explicitly expand that line in the
tree view. This can be done, for example, in the Program Item
Properties dialog of the Window's Explorer.
Security
For additional security, accept the
"Always prompt for password" default in the Creating
new DB Connection property sheet. Although Oracle Replication
Manager stores passwords to its connections in a safe, encrypted
format it is safer to always prompt for the password each time
before a connection is made.
Known Bugs, Limitations and Workarounds:
Replication Manager connects as SYSTEM to create users and grant privileges for replication
administration. In particular, sys.dbms_repcat_admin is used to grant replication administration
privileges to users. This does not work in a database with dictionary protection enabled because SYSTEM does not have execute privileges for this package. However, SYSTEM is granted the
EXECUTE_CATALOG_ROLE role. Therefore, this problem can be resolved by granting execute
on sys.dbms_repcat_admin to the EXECUTE_CATALOG_ROLE.
(GRANT EXECUTE ON sys.dbms_repcat_admin
TO execute_catalog_role)
Generate replication support after any
activity requiring it (for example, changing propagation mode
or conflict resolution method), whether or not a prompt appears.
You can view the status of replicated objects to see if they need
generation or not.
When you browse links to get to the
master of a snapshot group, you may see more links than those
related to the master group.