CDC Provider Replication Server Properties List

The CDC Provider Replication Server Properties list identifies the required and optional properties of the component.

Required Properties
Property	Description
RepServer Name	Specify the Replication Server to use to capture data changes. After Replication is created, this property cannot be modified. To modify it, right-click the component and select Drop Replication.
Rep Database	Object name generated during replication creation. This property is read-only.
Source Table Options	Set the replication definition options: Interface – identify the method or driver to use to connect to the primary datasource. Host Name – identify the primary datasource. The options depend on the selected interface. User and Password – identify an authorized database user, and protect the database against unauthorized access. If the source database is Adaptive Server Enterprise, the database user requires “sa” or “dbo” permission or “replication_role.” Database – identify the database to use as datasource. Also select an appropriate interface, and in some cases, specify an appropriate user ID and password. Schema – identify the schema or owner to use as datasource. The objects that appear are restricted accordingly and new tables are created in that schema. Table – identify the source table. Replicate – identify the column to be replicated. Note: Since large object (LOB) data processing is not supported, a column with LOB type is not replicated. Key – identify the columns with keys. Replication Server and Sybase IQ InfoPrimer use the key to identify each row of the source table. Note: Replication Server does not allow using column with LOB type as key. The key values should be unique for each row and the key columns must be replicated. Size – identify the column size. If the source database is Oracle, enter Replication Agent details: RepAgent Host – Replication Agent name, which must be the same as in Replication Agent. RepAgent Database – Replication Agent database name, which must be identical to the configuration value of ‘ rs_source_db ’ in Replication Agent. RepAgent Username and Password – user name and password to connect to Replication Agent. After Replication is created, you cannot modify this property. To modify it, right-click the component and select Drop Replication.
Port Options	Specify the port type of each output port: Port Name – specify the output port name. Function – specify the data changes to be sent from this port: Insert – sends insert changes. Delete – sends delete changes. Update – sends update changes. Upsert – sends insert and update changes. All – sends all data changes.
Capture Mode	Specify whether to send all received data changes or only the last received data changes on each row, to the next component. By default, this property is set to “Last,” which is appropriate for most incremental loading.
Replication	Indicates whether replication is created or dropped. The value for this property is generated by Sybase IQ InfoPrimer and is read-only.

Optional Properties
Property	Description
Rep Server User and Password	Specify an authorized Replication Server user name and password.
Stage Mode	Specify whether data changes should be staged in the memory or in an IQ temporary table. If the capture mode property is set to Last, provide a value for the stage mode property. Note: For a 32-bit grid engine, Sybase recommends that you set stage mode to IQ.
IQ for Stage Mode Options	Specify configuration for staging IQ. This property is enabled only when capture mode is Last, and stage mode is IQ.
Timeout seconds for no data	Specify the wait time, in seconds, for the component before it stops waiting to receive data changes from Replication Server.
Read Block Size	Determine the number of records retrieved by the component in a single step.
Auto Initial Load	Specify whether you want the initial load to take place automatically. Before transferring source table data changes, Sybase IQ InfoPrimer must perform an initial load to synchronize the source and destination table data, and create replication objects to make Replication Server start capturing data changes. Note: Since Replication Server does not support materialization for Oracle, this property does not work if the source database is Oracle. While executing or simulating a project: If this property is selected and Replication is not created, Sybase IQ InfoPrimer creates the replication definition, connection, and function strings, and uses the atomic materialization method to create the subscription. This materialization method locks the source table until all source table records are captured by Replication Server as insert operations in a transaction. After this, simulation or execution performs the initial load. If this property is not selected and Replication is not created, you see an error message. If this property is selected and execution or simulation fails, right-click the component and select Drop Replication. Try to execute or simulate the project again. If you right-click the component and select Create Replication while this property is selected, initial load does not take place. Note: While simulating a project, if this option is selected and you click Reset and Start to restart simulation, the CDC Provider Sybase Replication Server component does not receive the source table initial data a second time. Replication Server pushes initial data to Sybase IQ InfoPrimer only once.
Output Old Value	Select to output old column values of each data change. After Replication is created, you cannot modify this property. To modify it, right-click the component and select Drop Replication.
Transactional	All work performed by the component, including preprocessing SQL statements and postprocessing SQL statements, is done in a single database transaction that is committed when the project finishes normally. Select this option to roll back the transaction, if this component encounters an error.
Save Interval	Specify the amount of time, in minutes, for which Replication Server should save the data changes after it is received by Sybase IQ InfoPrimer. By default, Replication Server discards each data change after Sybase IQ InfoPrimer receives it. Set this property to have Replication Server save data changes for a while after Sybase IQ InfoPrimer receives them. You must save data changes, since a project or job failure can cause the destination table changes to roll back, if project level transactionality is enabled. In this case, all source table data changes received are not applied to destination tables. In subsequent executions, the data changes that are not processed successfully in the previous execution, that still exist in the Replication Server, are sent to the CDC Replication Server Provider component, along with any new changes. This ensures that the destination tables are updated correctly. If the save interval is too short, some data changes from running a failed project are not sent to the destination components, causing the destination tables to be out of sync with the source table data. If the save interval is too long, duplicate data changes are sent to the component, leading to decreased performance, and increased resource usage.