Release Notes for IDR 11.4 for Teradata

IDR 11.4.0.5-5731

Enhancements in IDR 11.4.0.5-5731 for CDC Replication Engine for Teradata

• Users can now specify subscriptions that are not allowed to use the shared scrape staging store by setting system property mirror_subs_allowed_to_use_staging_store to false at the subscription level

Known Issues fixed in IDR 11.4.0.5-5731 for CDC Replication Engine for Teradata

• DT394553 CDC Replication Engines - subscription ends on error NullPointerException when a commit fails on the target engine
• DT393813 CDC Replication Engines - Differential Refresh includes CDR columns in update and delete where clauses leading to rows not being found

IDR 11.4.0.5-5730

Enhancements in IDR 11.4.0.5-5730 for CDC Replication Engine for Teradata

• CDC Replication Engines now issue a warning if source and target columns have incompatible datatypes during table assignment for non-explicitly mapped columns
• System property mirror_timezone_support_enabled added to force CDC Replication Engines to use the source timezone when converting JCF and commit timestamps

IDR 11.4.0.5-5726

Enhancements in IDR 11.4.0.5-5726 for CDC Replication Engine for Teradata

• Effective January 2025, IDR CDC will no longer provide support for following operating system versions: RedHat Enterprise Linux (RHEL) 7; CentOS 7.x

IDR 11.4.0.5-5725

Enhancements in IDR 11.4.0.5-5725 for CDC Replication Engine for Teradata

• IIDR now provides the option of retrying the fast apply failed Unit of Work
• Updated JVM to 8.0.8.25, java version "1.8.0_411" Java(TM) SE Runtime Environment (build 8.0.8.25 - pwa6480sr8fp25-20240328_01(SR8 FP25))

Known Issues fixed in IDR 11.4.0.5-5725 for CDC Replication Engine for Teradata

• DT382379 CDC Replication Engines - dmsupportinfo command does not collect complete details expected.

IDR 11.4.0.5-5722

Known Issues fixed in IDR 11.4.0.5-5722 for CDC Replication Engine for Teradata

• DT258648 CDC Replication Engines - Replication ends on error "ClassNotFoundException" for Timestamp12Format class when executing a user exit that uses Timestamp12 class

IDR 11.4.0.5-5721

Enhancements in IDR 11.4.0.5-5721 for CDC Replication Engine for Teradata

• CDC now supports custom character sets that map multiple byte sequences to the same Unicode character.

IDR 11.4.0.5-5715

Enhancements in IDR 11.4.0.5-5715 for CDC Replication Engine for Teradata

• Document userexit interfaces such as UserExitIF, DataRecordIF and ReplicationEventIF in docs folder

IDR 11.4.0.5-5706

Enhancements in IDR 11.4.0.5-5706 for CDC Replication Engine for Teradata

• Updated JVM to 8.0.8.20, java version "1.8.0_401" (build 8.0.8.20 - pwa6480sr8fp20-20240112_01(SR8 FP20))
• Increased the requested maximum number of pending connections on the TCP accept queue

Bugs fixed in IDR 11.4.0.5-5706 for CDC Replication Engine for Teradata

• NecessityException could occur when running a table level user exit with any of the parallel hash fast apply algorithms

IDR 11.4.0.5-5703

Enhancements in IDR 11.4.0.5-5703 for CDC Replication Engine for Teradata

• Effective February 2024, IDR CDC will no longer provide support for Teradata 14.x, 15.x
• Effective February 2024, IDR CDC will no longer provide support for following operating system versions: SuSE 11.0; Ubuntu 16.04; Oracle Linux 6.x; CentOS 6.x; AIX 7.1; Microsoft Windows 7, 8, 8.1, Server 2008, Server 2008R2

Bugs fixed in IDR 11.4.0.5-5703 for CDC Replication Engine for Teradata

• When a key column update is converted to a delete/insert, we unnecessarily use Adaptive Apply as the RWA conflict resolution method for the delete and insert

IDR 11.4.0.5-5702

Enhancements in IDR 11.4.0.5-5702 for CDC Replication Engine for Teradata

• Added ParallelizeByHash, ParallelizeByHashNetEffect, and ParallelizeByHashNetEffectConvertUpdates fast apply algorithms

Bugs fixed in IDR 11.4.0.5-5702 for CDC Replication Engine for Teradata

• Specifying the number of image builder threads via the NullMirrorOptimizer fast apply user exit causes subscription to stop

IDR 11.4.0.5-5700

Enhancements in IDR 11.4.0.5-5700 for CDC Replication Engine for Teradata

• If system property mirror_refresh_while_active_resolution_method is set to IGNORE_CONFLICTS, CDC no longer uses full Adaptive Apply to resolve conflicts when applying operations that occurred during the refresh-while-active period for a table. Instead, conflicts are resolved in a simpler, more efficient way that allows JDBC batching.
• Updated various open source libraries

Bugs fixed in IDR 11.4.0.5-5700 for CDC Replication Engine for Teradata

• NecessityException can occur when target is using fast apply and the Unit Of Work has to be reapplied due to an exception and adaptive apply was used when applying an operation in the UOW

IDR 11.4.0.5-5699

Bugs fixed in IDR 11.4.0.5-5699 for CDC Replication Engine for Teradata

• Fix incorrect product version shown in Windows program manager

IDR 11.4.0.5-5696

Enhancements in IDR 11.4.0.5-5696 for Teradata

• Updated JVM to 8.0.8.11, java version "1.8.0_381"

IDR 11.4.0.4-5694

Enhancements in IDR 11.4.0.4-5694 for Teradata

• Updated JVM to 8.0.8.6, java version "1.8.0_371" (build 8.0.8.6 - pxz6480sr8fp6ifix-20230817_01(SR8 FP6+IJ47696))

IDR 11.4.0.4-5686

Enhancements in IDR 11.4.0.4-5686 for Teradata

• Updated JVM to 8.0.8.6, java version "1.8.0_371"

IDR 11.4.0.4-5676

Enhancements in IDR 11.4.0.4-5676 for Teradata

• Added ParallelizeByTableNetEffect and ParallelizeByTableNetEffectConvertUpdates fast apply algorithms

IDR 11.4.0.4-5674

Enhancements in IDR 11.4.0.4-5674 for Teradata

• Updated JVMs to 8.0.8.0

APARs in IDR 11.4.0.4-5674 for Teradata

• JR65266 ARRAY INDEX OUT OF BOUNDS EXCEPTION IF MAPPING HAS MULTIPLE DERIVED COLUMNS AND A SELECTED DERIVED COLUMN FOLLOWS AN OMITTED DERIVED COLUMN

IDR 11.4.0.4-5672

Enhancements in IDR 11.4.0.4-5672 for Teradata

• New derived expression %ORDERTAB(), to track per table record sequence number, is now supported on target agent.
• Updated JVMs to 8.0.7.20

Bug fixes in IDR 11.4.0.4-5672 for Teradata

• In some low volume workloads latency can be 1-5 seconds more than it should be

IDR 11.4.0.4-5670

Enhancements in IDR 11.4.0.4-5670 for Teradata

• Prevent JDBC refresh from failing with duplicate key exceptions during standard apply

APARs in IDR 11.4.0.4-5670 for Teradata

• JR65110 REFRESH NUMBER OF ROWS SUCCESSFULLY APPLIED CAN BE NEGATIVE
• JR65235 ROW FILTER &ENTTYP='UB' NEVER MATCHES, AND &ENTTYP='UP' MATCHES BOTH UB AND UP ROWS

IDR 11.4.0.4-5666

Enhancements in IDR 11.4.0.4-5666 for Teradata

• IDR now supports TLS 1.3 in addition to TLS 1.2 for communication between Management Console, Access Server, source datastores and target datastores. For improved security, only the most secure protocols are supported for TLS 1.3 (TLS_AES_256_GCM_SHA384, TLS_AES_128_GCM_SHA256) and TLS 1.2 (TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256).

Bug fixes in IDR 11.4.0.4-5666 for Teradata

• TCP/IP connections are closed prematurely when encrypted with TLS.
• "PKIX path building failed" error while retrieving schemas from the database over TLS, even though the database's root CA certificate was configured in the encryption profile's trust store.

IDR 11.4.0.4-5661

Enhancements in IDR 11.4.0.4-5661 for Teradata

• JDBC batching is now allowed if target table before-operation user exits exist

IDR 11.4.0.4-5659

Enhancements in IDR 11.4.0.4-5659 for Teradata

• Added property target_apply_assume_db_enforces_unique_key_violations that indicates whether CDC should assume the target database enforces unique key violations
• Do not send DML operation if column participating in row filtering condition is updated

IDR 11.4.0.4-5656

Enhancements in IDR 11.4.0.4-5656 for Teradata

• Performance optimization added for applying all deletes in a batch as a single delete statement. Dramatically improves performance of applying deletes against column organized tables. Enabled by setting system property target_apply_delete_batch_via_single_statement = true

APARs in IDR 11.4.0.4-5656 for Teradata

• JR65145 CDC COMMAND DMFLAGFORREFRESH SHOULD NOT ALLOW TO USE DIFFERENTIAL REFRESH (-DR) OPTION IF TARGET ENGINE DOESN'T SUPPORT IT

IDR 11.4.0.4-5652

Enhancements in IDR 11.4.0.4-5652 for Teradata

• dmclearstagingstore no longer implicitly clears the shared scrape parser transaction queues as this is not necessary in most cases

APARs in IDR 11.4.0.4-5652 for Teradata

• JR65123 TRUNCATION WARNING ISSUED EVEN THOUGH THERE IS NO NON-SPACE DATA TO BE TRUNCATED

IDR 11.4.0.4-5643

Enhancements in IDR 11.4.0.4-5643 for Teradata

• Fast apply modes GroupByTableNetEffect and GroupByTableNetEffectConvertUpdates are available for target engines that support fast apply.
• Support storing replication engine database credentials in an external secret store
• Updated JVMs to 8.0.7.10

IDR 11.4.0.4-5629

APARs in IDR 11.4.0.4-5629 for Teradata

• JR64572 NO WARNING EVENT WHEN CHARACTER DATA IS TRUNCATED

IDR 11.4.0.4-5627

Enhancements in IDR 11.4.0.4-5627 for Teradata

• Parallel Apply is now allowed with Adaptive Apply

APARs in IDR 11.4.0.4-5627 for Teradata

• JR64736 WARNING 9700 CAN OCCUR AND DUPLICATE OPERATIONS APPLIED IF A SUBSCRIPTION IS USING SHARED SCRAPE AND STAGING STORE IS CLEARED

IDR 11.4.0.4-5625

Enhancements in IDR 11.4.0.4-5625 for Teradata

• InstallAnywhere VM pack for CDC engine installer updated to Java 8.0.7.0
• IDR added a new command line utility "dmimportuserconfiguration" to help automate creation of multiple product instances with user configured values

APARs in IDR 11.4.0.4-5625 for Teradata

• JR64618 DMTS64 PROCESS IS TAKING A LONGER TIME TO START

Bug fixes in IDR 11.4.0.4-5625 for Teradata

• Fixed possible "duplicate key" or "row does not exist" error when replication key is being updated with ParallelizeSingleTableByHash fast apply algorithm

IDR 11.4.0.4-5622

Enhancements in IDR 11.4.0.4-5622 for Teradata

• Java Runtime Environment updated from IBM Java 8.0.6.30 to 8.0.7.0. Fix notes can be found at https://developer.ibm.com/javasdk/support/fixes/sdk8/ . This resolves IJ35231 - Missing byte when retrieving LOB data from database.

IDR 11.4.0.4-5618

APARs in IDR 11.4.0.4-5618 for Teradata

• JR64485 ADDRESSED ILLEGALARGUMENTEXCEPTION EMPTY KEY ERROR ISSUED DURING UPGRADE FOR SUBSCRIPTION ALERT HANDLERS CONFIGURED WITHOUT A SENDER EMAIL AND PASSWORD

IDR 11.4.0.4-5616

Enhancements in IDR 11.4.0.4-5616 for Teradata

• Added slf4j-api-2.0.0-alpha5.jar, slf4j-jdk14-2.0.0-alpha5.jar
• No longer bundle log4j-1.2.17.jar, slf4j-api-1.7.26.jar, slf4j-log4j12-1.7.26.jar dependencies

IDR 11.4.0.4-5611

APARs in IDR 11.4.0.4-5611 for Teradata

• JR64335 OUTOFMEMORY OCCURS WHEN TLS ENCRYPTION IS ENABLED AND MANY AGENT CONNECTIONS ARE MADE TO THE INSTANCE

IDR 11.4.0.4-5607

Bug fixes in IDR 11.4.0.4-5607

IDR 11.4.0.4-5607 for all LUW engines

• Addressed an issue causing bootstrap- .jar, user-exit- .jar and kafka-engine-kcop- .jar to keep accumulating in lib folder after product upgrades

IDR 11.4.0.4-5603

Enhancements in IDR 11.4.0.4-5603

IDR 11.4.0.4-5603 for Teradata

• IDR now supports Teradata 17.0 and 17.1 as target

APARs in IDR 11.4.0.4-5603

IDR 11.4.0.4-5603 for all LUW engines

• JR64071 IDR CDC FAILS WITH STATEMENT CLOSED ERROR WHILE RUNNING ADDITIONAL SQL STATEMENTS DURING REFRESH.

Bug fixes in IDR 11.4.0.4-5603

IDR 11.4.0.4-5603 for all LUW engines

• Addressed an issue causing an OOM error if there are large number of trace files

IDR 11.4.0.4-5599

Enhancements in IDR 11.4.0.4-5599

IDR 11.4.0.4-5599 for all LUW engines

• Updated the Java Virtual Machine to IBM 8.0.6.30

APARs in IDR 11.4.0.4-5599

IDR 11.4.0.4-5599 for all LUW engines

• JR63805 UTILITY TRACE FILES ARE ALWAYS GENERATED EVEN IF GLOBAL_TRACE_UTILITY_CREATE_ON_DEMAND = TRUE IF GLOBAL TRACING WAS EVER ENABLED
• JR63847 NECCESSITYEXCEPTION "CHANGE LOG BLOCK WE ARE TRYING TO READ IS EMPTY!" IF TIMING CIRCUMSTANCES ARE UNFORTUNATE
• JR63844 NPE OR ASSUMPTION EXCEPTION IF SUBSCRIPTION IS USING SHARED SCRAPE AND STAGING STORE IS CLEARED OR DISK QUOTA EXCEEDED
• JR63848 MEMORY LEAK IF SHARED SCRAPE STAGING STORE IS CLEARED WHEN MEMORY WAS TIGHT

Bug fixes in IDR 11.4.0.4-5599

IDR 11.4.0.4-5599 for all LUW engines

• Addressed an issue causing some persistent subscriptions to restart unexpectedly after the user stopped multiple subscriptions at the same time

IDR 11.4.0.3-5596

Bug fixes in IDR 11.4.0.3-5596 for Teradata

• Fixed NecessityException in ChangeLogBlock on instance start up

IDR 11.4.0.3-5594

APARs in IDR 11.4.0.3-5594 for Teradata

• JR63511 AUDIT WRONGLY DETECTS THAT REPLICATION ENGINE HAS MULTIPLE OFFERINGS INSTALLED
• JR63191 DMTS64 CPU USAGE GOES TO NEAR 100% WHEN LAST SUB USING SHARED SCRAPE STOPS AND BEFORE ITS LOG PARSER AND READER STOP

IDR 11.4.0.3-5582

Bug fixes in IDR 11.4.0.3-5582 for Teradata

• Fixed issue which caused error "LOBs are not allowed in indexes" when BYTE or VARBYTE is used as part of index

IDR 11.4.0.3-5576

Enhancements in IDR 11.4.0.3-5576 for Teradata

• The dmsupportinfo command line utility now dumps and collects configuration metadata in a text format

APARs in IDR 11.4.0.3-5576 for Teradata

• JR62920 EXCESSIVE DIAGNOSTIC PROBES FOR TRUNCATE OF CLOB EVENTS

Bug fixes in IDR 11.4.0.3-5576 for Teradata

• IDR now truncates LOB data precisely based on the value of the userexit_max_lob_size_kb parameter instead of exceeding the maximum size for some values

IDR 11.4.0.3-5572

Enhancements in IDR 11.4.0.3-5572 for Teradata

• EVENT THAT ALERTS USER THAT IDR HAS DETECTED A DDL NOW INCLUDES THE DDL TEXT IF LOGGING OF DDL STATEMENTS IS ENABLED

APARs in IDR 11.4.0.3-5572 for Teradata

• JR62909 INCORRECT SAMPLE CONTENT WHEN ISSUING "DMEXPORTCONFIGURATION -?"
• JR62934 DMTS64 NOT RELEASING IX (EXCLUSIVE) LOCK ON SYSTABLES AFTER MAKING DATABASEMETADATA CALLS

Bug fixes in IDR 11.4.0.3-5572 for Teradata

• &LIBRARY, &MEMBER and &OBJECT Journal Control Fields now evaluate to the correct values instead of an empty string when used in a derived column
• JR62973 IDR IS NOT POPULATING JCF FIELDS FOR START AND END REFRESH EVENTS WHEN USEREXIT USED

IDR 11.4.0.3-5570

Enhancements in IDR 11.4.0.3-5570 for Teradata

• The dmsupportinfo command line utility now collects trace files significantly faster
• The dmsupportinfo command line utility now collects all available trace files, performance statistics and events when you do not use the "-t" property to specify a time range

APARs in IDR 11.4.0.3-5570 for Teradata

• JR62799 MIRRORING DOES NOT ENTER FAILED STATE WHEN IT DETECTS A DDL OCCURRED ON A STATIC TABLE
• JR62787 USER GETS A DUPLICATE KEY EXCEPTION IF THEY HAVE A TABLE MAPPING WITH TWO OR MORE COLUMNS WITH A COMMENT THAT IS THE SAME FOR THE FIRST 260 CHARACTERS

Bug fixes in IDR 11.4.0.3-5570 for Teradata

• Addressed a defect in the dmsupportinfo command line utility that caused trace files to be omitted during collection

IDR 11.4.0.3-5567

APARs in IDR 11.4.0.3-5567 for Teradata

• JR62737 CDC ERROR 9506 OCCURS AFTER A DDL EVEN WHEN ALL DDL PROCEDURES ARE FOLLOWED

Bug fixes in IDR 11.4.0.3-5567 for Teradata

• Fixed Array Index Out of Bounds Exception or Null Pointer Exception occurring when operation from shared scrape staging store needs a table definition that is older than the current table definition

IDR 11.4.0.3-5566

Enhancements in IDR 11.4.0.3-5566 for Teradata

• Java Runtime Environment updated from IBM Java 8.0.6.0 to 8.0.6.10. Fix notes can be found at https://developer.ibm.com/javasdk/support/fixes/sdk8/

APARs in IDR 11.4.0.3-5566 for Teradata

• JR62628 INDEX OUT OF BOUNDS EXCEPTION CAN OCCUR AT DBCONNECTIONMANAGER.RELEASEMETADATASESSION()

IDR 11.4.0.2-5563

APARs in IDR 11.4.0.2-5563 for Teradata

• JR62451 IDR REPLICATES SOURCE DERIVED COLUMN DATA TO INCORRECT TARGET COLUMN

IDR 11.4.0.2-5560

Enhancements in IDR 11.4.0.2-5560 for Teradata

• Instance-specific command line utilities now trace their parameters and an execution return code.

Bug fixes in IDR 11.4.0.2-5560 for Teradata

• IDR will no longer log excessive tracing of NonTransientConnectionException by avoiding rolling back a transaction on a database connection that has auto-commit enabled.
• dmconfigurets no longer creates two trace files when run in the command line mode.

IDR 11.4.0.2-5544

Enhancements in IDR 11.4.0.2-5544 for Teradata

• dmsupportinfo no longer collects duplicate information in the "dir.txt" support assistant file when an instance folder is inside the product installation directory.

APARs in IDR 11.4.0.2-5544 for Teradata

• JR62126 IMPROVED IDR COMMAND LINE UTILITIES PERFORMANCE BY OPTIMIZING ACCESS TO CDC SECRET STORE WHEN ENGINE-TO-ENGINE ENCRYPTION IS DISABLED, ENABLED OR REQUIRED.
• JR62158 SCHEDULED END BY TIME SOMETIMES DOESN'T WORK WHEN DB IS 100% IDLE, SHARED SCRAPE IS USED AND SUBSCRIPTION FINDS NEW OPERATIONS IN STAGING STORE AT STARTUP.

Bug fixes in IDR 11.4.0.2-5544 for Teradata

• Addressed the error "row already exist in index TABLE_NAMES_IDENTITY_NAME_IDX" when accessing the metadata
• Addressed intermittent "java.lang.AssertionError thread interruption is not supported" in TraceFormatter.
• Instance commands no longer create trace files in "installation_directory/log".

IDR 11.4.0.2-5528

Enhancements in IDR 11.4.0.2-5528 for Teradata

• IDR now closes some idle database connections and re-opens them as needed. The global_database_connection_idle_timeout_seconds system parameter controls how long to keep idle database connections open. Closing idle database connections before firewalls close them prevents subscriptions from stopping due to broken database connections.

APARs in IDR 11.4.0.2-5528 for Teradata

• JR61841 ERROR REFRESHING A TABLE WITH A LONG COLUMN COMMENT: "AN UNCAUGHT EXCEPTION HAS OCCURRED"

Bug fixes in IDR 11.4.0.2-5528 for Teradata

• IDR automatically recovers an erroneous metadata state that could cause lead to "An error has occurred. Possible recovery steps: Please try again. If the error persists, if possible restart the IBM Data Replication instance and try again. Internal error information: Agent Message 'Message3036' Exception text 'null'"
• Improved reliability when global_subscription_level_connection_keep_alive_seconds is set to a non-zero value.
• IDR now uses a different method to manipulate metadata table TABLE_NAMES_IDENTITY that is expected to prevent metadata corruption involving this table. This corruption could lead to the inability to use a table mapping or even delete it.
• Addressed intermittent EOFException and SocketException when running command line utilities under stress.
• Addressed intermittent EOFException reported by Agent Reader thread when using command line utilities.

IDR 11.4.0.2-5522

Enhancements in IDR 11.4.0.2-5522 for Teradata

• IDR issues an improved error message when dmconfigurets is run with non-Administrator privileges in Windows Server 2016

APARs in IDR 11.4.0.2-5522 for Teradata

• JR61803 IIDR FAILS WITH ERROR TOO MANY OPEN FILE DESCRIPTOR WHEN MULTIPLE INSTANCES ARE RUNNING FROM SAME INSTALLATION BECAUSE OF FILE DESCRIPTOR LEAK.

IDR 11.4.0.2-5512

Enhancements in IDR 11.4.0.2-5512 for Teradata

• IIDR now supports always encrypting communication with TLS, without negotiation. This feature may be enabled by setting Engine-to-Engine Communication Encryption to Always in the encryption profile. When this feature is enabled, IIDR will not be able to communicate with source datastores, target datastores, or Access Servers that negotiate encryption through STARTTLS.
• IDR no longer raises an error event if it cannot extract primary index information for a table from the database

APARs in IDR 11.4.0.2-5512 for Teradata

• JR61637 CDC STILL TAKES VALUES IN BYTES AFTER CHANGING SYSTEM PARAMETER USEREXIT_MAX_LOB_SIZE_KB UNLESS THE INSTANCE IS RESTARTED

Bug fixes in IDR 11.4.0.2-5512 for Teradata

• Trace can now be collected reliably using support assistant in concurrent invocations.
• Addressed differential refresh failing when order of columns in primary key differs from order returned by JDBC

IDR 11.4.0.2-5507

Enhancements in IDR 11.4.0.2-5507 for Teradata

• dmsupportinfo command line utility collects replication product traces using an optimized algorithm to speed up data collection

IDR 11.4.0.2-5506

Enhancements in IDR 11.4.0.2-5506 for Teradata

• IDR CDC product binaries are signed with a new signing service and with an updated certificate with expiry date "Wed Jun 30 08:00:00 2021"
• IIDR now supports dmcreateencryptionprofile for creating encryption profiles.

IDR 11.4.0.2-5503

Enhancements in IDR 11.4.0.2-5503 for Teradata

• Prior product libraries found in /lib are deleted when upgrading product binaries before new libraries are dropped on disk. All jar files with names similar to those installed with the product will be deleted.
• IIDR now supports the option of requiring TLS encryption for all connections from Access Server and other datastores.

APARs in IDR 11.4.0.2-5503 for Teradata

• JR61380 "ARITHMETICEXCEPTION DIVIDE BY 0" IS THROWN WHEN ONLY DERIVED COLUMN ARE SET FOR REPLICATION