This is a suggestion for the Replicate users manual under using Oracle as a source. Add "enable forced logging" into the list of tasks to be accomplished to prepare an Oracle database as a source for Replicate. Regrettably there is a lot of false information on the WEB that leads developers and end users who have the appropriate tools and access to specify the NOLOGGING clause when doing insert, update or delete activities. If that is done the action is NOT written to the redo logs and as a result Replicate is ignorant of the activity, The forced logging setting of the database negates the NOLOGGING clause in any statement. This is a prerequisite for Oracle when setting up a standby database & should be included here as well. I would also recommend a "select force_logging from v$database;" in the endpoint test when the database is Oracle and it is listed as a source. The answer should be "YES". While I do not think this should cause an endpoint to fail it's test it should behave similarly to when the source user account does not have the "create any directory" system privilege, namely as a warning.
