Redo and archive log setup

By default, you can access both online and archive logs. You can configure Replication Agent to access only the online logs, but doing so requires you to turn auto-archiving off and requires Replication Agent to issue manual archive log commands to Oracle.

When you are using the default, for archive log files to be accessed, configure Replication Agent to use the directory path where archive log files are located. By default, an Oracle instance creates multiple directories under the flash recovery area specified by the DB_RECOVERY_FILE_DEST parameter of the Oracle ALTER SYSTEM command, each directory corresponding to and named after a separate day. However, Replication Agent requires archived redo log files to reside in a single directory. Consequently, you must configure Oracle to archive to a single directory to be read by Replication Agent.

For information on specifying archive log destinations for your Oracle environment, see the Oracle ALTER SYSTEM command and LOG_ARCHIVE_DEST_n parameter.

In the Replication Agent, set the pdb_archive_path configuration property to the expected location of archived redo log files. You can also set the Replication Agent pdb_remove_archives configuration parameter to true to allow the Replication Agent to remove these archive log files when they are no longer needed to support replication.

When pdb_include_archives is set to true (the default), Replication Agent does not archive, and Sybase recommends that you configure Oracle to perform automatic archiving of redo logs.

When the pdb_include_archives configuration parameter is set to false, Replication Agent for Oracle also requires you to disable automatic archiving of Oracle redo logs. Archiving is performed manually by Replication Agent as the data in the redo log files is replicated.

Replication Agent for Oracle requires the following settings in your Oracle database depending on the Oracle version.

1. Make sure you have sysdba administrator privileges, and close the database.

2. Enter the following:

   alter database ARCHIVELOG MANUAL;
   

3. To verify that log archiving is disabled:

   select log_mode from v$database;
   

   If MANUAL is returned, then automatic log archiving is disabled.

1. To change the LOG_ARCHIVE_START parameter, either manually edit the server start-up parameter file, or use the following Oracle command:

   alter system set log_archive_start=false scope=spfile;
   

2. To check the setting of the LOG_ARCHIVE_START parameter:

   select value from v$system_parameter where name = 'log_archive_start';
   

3. If false is returned, the value in the server parameter file has been correctly modified to prevent automatic archiving when you re-start the Oracle server. For information about the LOG_ARCHIVE_START parameter or the ALTER SYSTEM commands, see the Oracle Database Reference Guide.

4. Automatic archiving must be disabled in the active server and when you re-start the Oracle server. To stop automatic archiving in the active server, enter the following:

   alter system archive log stop;
   

5. To disable automatic archiving when you re-start the Oracle server, change the value of the server’s LOG_ARCHIVE_START parameter to false.

   If pdb_include _archives is set to false: For redo log file processing after Replication Agent for Oracle is initialized, automatic archiving must never be enabled, even temporarily. If automatic archiving is enabled or if manual archiving is performed, causing a redo log file not yet processed by the Replication Agent to be overwritten, the data in the lost redo log file is not replicated. You can recover from this situation by reconfiguring the Replication Agent to access archive log files. Set pdb_include_archives to true, set pdb_archive_path to the directory location that contains the archive of the file that has been overwritten, and resume. After catching up, suspend the Replication Agent, and reset pdb_include_archives to false.

You can enable the forced logging of all database changes to the Oracle redo log file. Sybase recommends setting this option to insure that all data that should be replicated is logged. To enable the force logging command, execute the following statement on the primary database:

alter database FORCE LOGGING;

To verify the current setting of the force logging command, execute the following statement on the primary database:

select force_logging from v$database;