Structure of the Configuration File

Configuring and Managing the Oracle BI Presentation Catalog 17-49 ReadLogRecordsSinceHoursAgo120ReadLogRecordsSinceHoursAgo RecordsInFileLimit4000RecordsInFileLimit Cluster IDsinClusterID_FOR_S1, ID_FOR_S2IDsinCluster MyInstanceIDID_FOR_S1MyInstanceID Cluster Replication ps:Catalog ServerInstance On Server2, you set the instanceconfig.xml file to these same values, with one exception. You set the MyInstanceID element to a value of ID_FOR_S2 to indicate that log files that are generated by the instance of Presentation Services on this server use a suffix of ID_FOR_S2. MyInstanceIDID_FOR_S2MyInstanceID Table 17–7 shows sample replication log files names that are generated by Server1 and Server2. Each node in the cluster must know the names of the other server log files to read replication information that is generated by the other servers.

17.12.7 Resuming Replication if Replication Log Files Are Unavailable

If, for some reason, replication log files are unavailable in an instance of Presentation Services, then you can resume replication by copying over the Oracle BI Presentation Catalog folders that the instance subscribes to. However, this method loses the catalog contents that were not replicated to other instances. The following method preserves all catalog contents. To resume replication if replication log files are unavailable: 1. Use Catalog Manager to erase all replication logs in the presentationcatalogpathreplicationchangelog and presentationcatalogpathreplicationplayback folders, where presentationcatalogpath is the full path to the Oracle BI Presentation Catalog folder. Table 17–7 Replication Log File Names by Server Log File Type Server1 Server2 Change log sawchange_ID_FOR_S1_1.log sawchange_ID_FOR_S1_2.log sawchange_ID_FOR_S1_3.log sawchange_ID_FOR_S1_4.log sawchange_ID_FOR_S2_1.log sawchange_ID_FOR_S2_2.log sawchange_ID_FOR_S2_3.log sawchange_ID_FOR_S2_4.log Playback log sawplayback_ID_FOR_S1_1.log sawplayback_ID_FOR_S1_2.log sawplayback_ID_FOR_S1_3.log sawplayback_ID_FOR_S1_4.log sawplayback_ID_FOR_S2_1.log sawplayback_ID_FOR_S2_2.log sawplayback_ID_FOR_S2_3.log sawplayback_ID_FOR_S2_4.log Note: If you must resume replication after Presentation Services has been offline for a time period in excess of that specified in the ReadLogRecordsSinceHoursAgo element in the instanceconfig.xml file, then you can adjust the value of ReadLogRecordsSinceHoursAgo so that log files in the offline period are replicated. Then, reset ReadLogRecordsSinceHoursAgo back to its original setting.