Attunity Replicate 5.

5 Release Notes - August

2017
Replicate 5.5 introduces several important features and enhancements including enhanced
Change Processing support for IBM DB2 for z/OS and IBM DB2 for iSeries source endpoints,
Change Data Partitioning, Load Ordering, and support for scheduling jobs according to UTC
time or local server time.

Note In addition to these release notes, customers are also encouraged to read the
release notes for all versions higher than their current version.

In these release notes:

Migration and Upgrade
Enhanced Change Processing for IBM DB2 for z/OS and IBM DB2 for iSeries Sources
Change Data Partitioning
Load Ordering
Change Table Column Customization
Hadoop Changes and Enhancements
File Endpoint Enhancements
Support for Overriding Source Column Character Sets and Data Types
Attunity Avro Message Decoder SDK
SAP Application Source Changes and Enhancements
New Endpoints and Version Support
Rolling out Support for Attunity Replicate Connect (ARC)
Miscellaneous
Resolved Issues and Customer Requested Enhancements
Known Issues

Migration and Upgrade

This section describes the issues that you may encounter when upgrading/migrating to
Replicate 5.5.

.NET Framework 4.5.2

From Replicate 5.1.1, .NET Framework 4.5.2 or above needs to be installed on the Attunity
Replicate machine.

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 1
Attunity Ltd.
 User Permissions
In versions preceding Replicate 5.1.1, user permissions were defined in the
UserConfiguration.xml file. From Replicate 5.1.1, user permissions are defined via the
Replicate Web Console. To support this new functionality, when upgrading to 5.5 from a
version prior to 5.1.1, the UserConfiguration.xml file is converted to a local repository
file.
In most cases, the conversion of the UserConfiguration.xml file to a local repository file
is straightforward.
However, although uncommon, the following case should be noted:
Users/Groups defined without a domain: If a user or group is defined in the
UserConfiguration.xml without a domain name (e.g. MyGroup instead of
MyDomain\MyGroup), the Replicate computer domain name will be automatically added to
the user/group name (e.g. AttRepDomain\MyGroup).
If the Replicate computer does not belong to a domain, the computer name will be added
instead of the domain name (e.g. AttRepComputerName\MyGroup).

Multiple Data Folders

When upgrading a Replicate installation with multiple Data folders, only the default Data
folder (<Product_Dir>\Data) will be automatically upgraded. The other Data folders need
to be updated manually by running the following command:
repuictl.exe -d <data_folder_path> setup install

Importing a JSON File from Previous Versions

Before importing a JSON file that was exported from a previous version of Replicate, you
first need to edit the file and remove the Scheduler section (if set). Then, save the file and
continue with the import process.

Kafka Target Endpoint

Replicate 5.2 introduces changes to the JSON message structure. During upgrade, if
Replicate detects any tasks with a Kafka endpoint, it will enable the internal parameter
useOldJsonVersion. This will allow the tasks to continue running using the old JSON
format. Customers who wish to start using the new JSON structure need to stop the task,
clear the useOldJsonVersion internal parameter (in the Advanced tab), and then resume
the task.

Oracle Source Endpoint

Customers upgrading from earlier versions should set the Archived redo logs
destination identifier value to the correct DEST_ID. Note that the specified destination
must be accessible by Attunity Replicate.

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 2
Attunity Ltd.
 If the Archived redo logs destination identifier is not specified (i.e. "0"), Attunity
Replicate will use the minimal existing DEST_ID.

Hadoop Target Endpoint

Importing a Hadoop target endpoint from earlier Replicate versions to Replicate 5.5
changes the Hive Access mode to ODBC.
If you were previously using WebHCat to access Hive, you should change it back to
WebHCat after the import completes.

Teradata Database ODBC Driver

From Attunity Replicate 5.1.1, only Teradata ODBC driver 15.00 is supported. To prevent
tasks from failing, customers with tasks that use the Teradata endpoint should upgrade
their driver before upgrading to the new Replicate version.

Replicating System Names with the New IBM DB2 for iSeries Endpoint
The recently deprecated IBM DB2 for iSeries AIS-based endpoint replicated tables based
on their system names (limited to 10 characters). The new native IBM DB2 for iSeries
source endpoint replicates tables based on their SQL names (unlimited length). If your IBM
DB2 for iSeries database does not use SQL names, it's likely that you'll want to keep the
replication based on system names.
To do this, enable the Use Table and schema System Names option (in the Advanced
tab).

Logging Levels
After upgrade, the logging levels are reset to the default level (Info).

File Target Endpoint

Post-processing commands that are imported into Replicate 5.5 from earlier Replicate
versions will not run unless the Post-process files check box is selected (by default, it’s
not selected).
Note that this only applies to import/export and not to upgrade.

Upgrading from Version 4.0.9 to Version 5.5

Attunity Replicate 5.0 introduced significant changes aimed both at hardening the security
of the product and ensuring its adherence to common industry standards. As such, several
factors need to be taken into consideration when upgrading from Replicate 4.0.9 to
Replicate 5.5.
This section highlights the main security changes and provides instructions on how to
successfully upgrade from Attunity Replicate 4.0.9.

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 3
Attunity Ltd.
 Security Related Changes
The technology of the Attunity Replicate web interface (Attunity Replicate Console) is
now based on HTML5. Older versions used Adobe Flash which had a long history of
security vulnerabilities.
In line with current industry security standards, the Attunity Replicate web server now
enforces the use of HTTPS to protect against eavesdropping and data leakage. Using
HTTPS requires a valid server certificate to be installed on the Attunity Replicate web
server machine.
The default Attunity Replicate web interface URL was changed from:
http://{host}/attunityreplicateconsole
To:
https://{host}/attunityreplicate
This is due both to the new web interface technology and in preparation for an API to be
released in the near future.
As a result of the above-mentioned changes, it is critical to refer to the installation chapter
in the user guide and to make sure that all the required preparations are in place before
beginning the upgrade.

Common Upgrade Issues

The following common issues may arise if an upgrade is done without preparation:
Existing links to the Attunity Replicate Console do not work - Since the new
default URL is different, existing bookmarks and links will not work. This can be resolved
by updating the links (recommended). Another way to resolve this issue is to change the
URL back to the previous URL. This can be done by editing the
~Attunity\Replicate\Data\ServiceConfiguration.xml file (default location) and
changing the AttunityReplicate part of the url= attribute back to
AttunityReplicateConsole.
Opening the Attunity Replicate Console results in a 'connection rest' error -
HTTPS requires a valid HTTPS server certificate to be installed. If the installed
certificate is not valid, the browser will not be able to connect to the Attunity Replicate
web interface.
On opening the Attunity Replicate Console, the browser issues a security
warning about an untrusted web site - When no HTTPS server certificate is found,
Attunity Replicates generates and deploys a self-signed certificate. While this certificate
is perfectly valid and secure, the web browser has no way of knowing this - hence the
warning. This can be resolved by installing a valid HTTPS server certificate or by telling
the browser it can trust that self-signed certificate. Note that the process for trusting
certificates varies from browser to browser and your corporate security policy may
prevent self-signed certificates from being installed (in which case you will need to
purchase and install a third-party certificate).

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 4
Attunity Ltd.
 Enhanced Change Processing for IBM DB2 for z/OS and
IBM DB2 for iSeries Sources
Replicate 5.5 introduces design optimizations that improve performance and reduce the
footprint when capturing changes from IBM DB2 for z/OS and IBM DB2 for iSeries.
Consequently, these endpoints can now be used without needing Attunity Integration Suite
(AIS) to be installed on the source platforms. The ability to directly access these endpoints
from Attunity Replicate reduces MIPS consumption, improves throughput, and reduces
latency. These Change Processing optimizations complement the Full Load enhancements
that were introduced in Replicate 5.2.

Change Data Partitioning

Replicate 5.5 introduces support for Change Data Partitioning.
Change Data Partitioning enables processing of Change Data from many tables in a
consistent fashion. You can define the duration of partitions as well as the partitioning base
time, thereby ensuring overall consistency of the partitioned data (i.e. no partial
transactions).
The partitioned data is stored in the Replicate Change Tables. Information about the
partitions is written to the new "attrep_cdc_partitions" Control Table in the target
database. This information can then be used to identify partitioned data that needs to be
further processed.
This feature is available in the Task Settings|Store Changes tab.

Note This feature is currently only supported with the Hadoop target endpoint.

Load Ordering
You can set the load order priority for each of the tables being replicated. Tables with the
highest priority will be loaded first, followed by tables with lower priorities. This feature
can be used, for example, for loading smaller tables before larger tables or for prioritizing
load order based on data importance.
This facilitate this feature, a new Load Order column has been added to the table lists.

Change Table Column Customization

Users can now choose which header columns will be included in the Change Tables. By
excluding unneeded header columns, customers can reduce the size of the Change Tables
in the target database.
This feature is available in the Task Settings|Store Changes tab.

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 5
Attunity Ltd.
 Hadoop Changes and Enhancements
The following enhancements have been made to the Hadoop endpoint:
The Hadoop target endpoint now supports sequence as a target storage format. When
sequence format is selected, the data is loaded directly to the target (i.e. without
running a Hive process).
Hadoop on Linux now supports Kerberos using a keytab file.
Change Data Partitioning. See Change Data Partitioning above.
WebHCat Deprecation in Hadoop Target: From Replicate 6.0, Attunity is planning to
discontinue support for the WebHCat Hive access method in Hadoop Target. Customers
currently using WebHCat to access Hive should start preparing to switch to an ODBC-
based solution.
The ODBC driver that needs to be installed depends on your particular Hadoop
distribution (Hortonworks, Cloudera, MapR, or Amazon EMR). For information about
supported ODBC drivers, please refer to the Attunity Replicate Help.

File Endpoint Enhancements

The following enhancements have been made to the File endpoint:
File Target: The File Target post command now supports the following exit codes:
Success (0), Recoverable Error (1), Table Error (2), and Failure (3 or above). Users can
also use internal parameters to set exit codes with custom values. This is especially
useful if the customer's application already uses the standard exit code values.
File Source: An Advanced tab has been added to the endpoint settings. The following
options were moved from the General tab to the Advanced tab: File preprocessing
command, Check for changes every, and Change processing cleanup.
Attunity Replicate data types are now included in the metadata file (DFM).

Note After upgrading, customers with existing tasks that wish to use the new data
types should stop the task, clear the dfmVersion=1.0 internal parameter, and then
restart the task.

Support for Overriding Source Column Character Sets

and Data Types
From Replicate 5.5, users will be able to override the character set and type of source
columns.
This is useful in the following cases:
If a source character column is wrongly encoded. For example, if a source character
column is described as encoded in CCSID X, but the data stored in that column is
actually encoded in CCSID Y.

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 6
Attunity Ltd.
 If a source column is defined as character type but the data stored in that column is
binary or vice versa.

Note The following limitations apply:

Currently supported with IBM DB2 for iSeries and IBM DB2 for z/OS endpoints only.
NCLOB columns are not supported.

Note As Replicate never modifies the actual source data, any changes are applied
during buffering.

Attunity Avro Message Decoder SDK

Attunity Replicate supports message streaming using both JSON and Avro formats. To ease
the task of processing Avro messages, Attunity provides the Attunity Avro Message
Decoder SDK, which contains the following:
Avro message deserializer
Working samples

SAP Application Source Changes and Enhancements

The following changes and enhancements have been made to the SAP Application source:
The SAP RFC NetWeaver client is now required to be installed on the Replicate Server.
For instructions, see the Attunity Replicate User Guide.
The authorization object S_DEVELOP is no longer a required permission for the Attunity
communication user in SAP.
The authorizations required for the dialog and communication users no longer require a
strong basis role.
Changes to the structure of source SAP tables and changes to the SAP business groups
are now handled automatically within Replicate.
The only exception is moving a table from one business group to another – in this case,
the change needs to be updated manually in Replicate's Table Selection window.
The Monitor for Full Load now shows % complete based on the number of rows read
from the SAP source as opposed to the number of rows transferred. This makes the
estimation for complex SAP table structures more accurate.
Replicate now automatically reconnects to the SAP source in case of a connection
failure.
A new Connection Type field was added to the endpoint settings. The new field enables
users to choose either Type A (single server) or Type B (load balancing system)
according to their SAP Application environment.

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 7
Attunity Ltd.
 New Endpoints and Version Support
Replicate for Linux: Support for the Microsoft SQL Server endpoint has been added.
Hadoop MapR: Hadoop MapR 5.2 is now supported.
Note that SSL and Kerberos are currently not supported with MapR version 5.2.
SAP Hana: Support for SAP Hana as a target endpoint has been added.

Note The SAP Hana endpoint is currently in Preview mode. Endpoints or features in
Preview mode are available for early preview, but are not generally available at the
time of release.
Please contact us if you are interested in learning more about this endpoint.

Rolling out Support for Attunity Replicate Connect (ARC)

Starting from Replicate 6.0, AIS (Attunity Integration Suite) will be replaced with ARC
(Attunity Replicate Connect).
As preparation for this change, the following endpoints appear in the UI with (ARC) instead
of (AIS).
DISAM (ARC)
IBM DB2 on iSeries (ARC)
IBM DB2 on z/OS (ARC)
IBM IMS (ARC)
RMS (ARC)
VSAM (ARC)
As stated above, the actual change in functionality is only due to be implemented in
Replicate 6.0. Therefore, customers that are currently using AIS do not need to make any
changes to their existing endpoints in Replicate 5.5. Customers should however be aware
that in order to continue using these endpoints from Replicate 6.0, they will need to replace
their AIS installation with ARC.

Miscellaneous
Kafka Target endpoint: Attunity Replicate data types were added to the metadata
message.
Deprecation of the Resume Full Load option: The option to resume loading tables
that were interrupted during Full Load has been deprecated. This option was accessible
when the Error gauge was selected in the Monitor|Full Load tab.
The Advanced Run Options UI has been tweaked to remove redundancies and
categorize the available options.

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 8
Attunity Ltd.
 Resolved Issues and Customer Requested
Enhancements
The table below lists the resolved issues and enhancements for this release.

Component/Process Type Description Ref #

Oracle Source - Binary Issue Crash in parser of oracle binary 151488
Reader reader would occur during an
empty OLTP OVERWRITE event.
Oracle Source - Binary Issue INSERT of changed records that 149007
Reader contained CR (Redo Chain)
flags would not be applied to
the target, despite being
successfully applied to the
Change Table.
Oracle Source - Binary Issue A task would fail when trying to 149800
Reader replicate an OLTP compressed
table, due to an unfamiliar
Oracle redo log structure.
Oracle Source - Binary Issue A task containing compressed 149179
Reader OLTP tables failed due to an
overflow of an internal variable
of columns.
Oracle Source - Binary Issue A task containing compressed 148747
Reader OLTP tables using DIRECT
INSERT failed to run.
Oracle Source - Binary Issue Fixed an issue with Oracle 148515
Reader Source pertaining to updates
that change the partition key.
Oracle Source - Binary Issue A task replicating partitioned 147871
Reader tables would sometimes fail
following operations on
partitions.
Oracle Source - Binary Issue An error occurred when the 147794
Reader redo log's physical block size
was not a multiple of the logical
block size.
Oracle Source - Binary Issue Oracle Binary Reader would fail 147379
Reader when more than one archived
redo destination ID was used.
Oracle Source - Binary Issue Errors would be encountered 147116

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 9
Attunity Ltd.
 Component/Process Type Description Ref #
Reader when using Binary Reader to
capture partition change
operations.
As Binary Reader does not
support capturing partition
change operations, the
resolution was to start the task
from a timestamp to clean the
table partition list
Oracle Source - Binary Issue The task would crash because 148925
Reader of a previously unknown Oracle
UPDATE event that Oracle
creates in rare situations.
Oracle Source Endpoint - Issue Tasks copying archive N/A
Binary Reader directories would stop after two
hours due to a timeout.
The issue was resolved by
adding a new internal
parameter:
retryTimeoutInMinutes.
The default is 120 (2 hours).
Setting "0" disables the timeout
behavior and the task does not
stop at all.
Oracle Source - Binary Issue An invalid timestamp error 149979
Reader would occur on the target when
the source tables resulted from
SHRINK operations.
Oracle Source - Binary Issue Due to an issue handling the 152182
Reader V$ARCHIVED_LOG entry, the
task would stop with the
following error (but could then
be resumed):
Redo archive file with the
sequence 59980 does not
exist.
Oracle Source - Binary Issue When running multiple Oracle- 153226
Reader to-Oracle CDC tasks (same
source and target), the tasks
would enter an infinite loop

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 10
Attunity Ltd.
 Component/Process Type Description Ref #
when reading the online REDO
log.
Oracle Source - Binary Issue Due to an issue with the Oracle 153463
Reader source endpoint, replicating
from an Oracle source would
result in an incorrect
timestamp or incorrect numeric
values on the target.
Oracle Source - Binary Issue Source latency would continue N/A
Reader to increase when the database
was idle
Oracle Source - Binary Issue Tasks copying to archive N/A
Reader directories would stop after two
hours due to a timeout. The
issue was resolved by adding
the retryTimeoutInMinutes
internal parameter.
Setting the parameter to "0"
prevents the operation from
timing out.
Oracle Source - LogMinor Issue Oracle Binary Reader did not 151777
work when more than one
archived redo destination ID
was used.
Oracle Source Issue "Test Connection" on Oracle 147814
source using Internal
Parameter:
"nlsCharsetId=874" would
report an unclear error.
The error was changed to:
Cannot create Oracle NLS
environment for charset
874 and ncharset 1000 OCI
error..SYS,GENERAL_
EXCEPTION,Cannot create
Oracle NLS environment for
charset 874 and ncharset
1000 OCI error.,ORA-12715:
invalid character set
specified OCI error."

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 11
Attunity Ltd.
 Component/Process Type Description Ref #
Oracle Source Issue High source latency would 148618
occur with Oracle source when
ASM was used for storing
Oracle redo logs.
Oracle Source Issue chr(0) would be converted to 148507
single byte space instead of
empty string on the target.
Oracle Source Issue When the Oracle environment 147782
could not be established (e.g.
due to an incorrect charset
value), Replicate did not print
the correct error messages.
Oracle Source Issue Oracle source did not handle an 149251
internal flag correctly.
Oracle Target Issue Replication would fail due to an 147500
Oracle bulk limitation of 330
columns per table.
Oracle Target Issue An error would occur when 134893
dropping a column that is part
of a primary key.
Oracle Target Issue A double-byte space inserted 147155
into a column of type
NVARCHAR2 was replicated as
a regular space during full load.
During Apply Changes, the task
would stop abnormally.
Oracle Target Issue Oracle bulk apply would 149147
sometimes crash during a
Replicate upgrade when the net
changes table already existed.
Oracle Target Issue The char(0) of nchar and 150255
nvarchar2 data types would not
be replicated correctly.
Microsoft SQL Server Issue The task would fail when 150370
Source Endpoint reading a large transaction log
file if the Replicate has file-
level access to the backup
log files option was enabled.

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 12
Attunity Ltd.
 Component/Process Type Description Ref #
Microsoft SQL Server Issue The user credentials for the 151431
Source Endpoint Replicate has file-level
access to the backup log
files option would be refused.
Microsoft SQL Server Issue During change capture, the 151822
Source Endpoint task would fail with the
following error:
A change record for table
'dbo.LOG_RAW_MSG' cannot
be fully parsed.
Oracle ASM Issue Performance issues were 148359
encountered when replicating
from ASM.
File Channel Issue When Full Load was aborted by 149221
the user, the File Channel
remote task would not cancel
the Full Load operation
correctly. This resulted in
missing events in the remote
task's target database.
File Channel Issue If the File Channel local task 149221
was stopped during Full Load
with cached changes, the File
Channel remote Task would
start to apply changes on a
table during the Full Load
operation.
Hadoop Source Issue Replicate would fail to capture 151186
files generated by Spark.
Hadoop Target Issue An error would occur when 149453
configuring an ODBC
connection using the
Hortonworks ODBC driver.
Hadoop Target Issue The task would fail as a result 148531
of dropping a column in a
transformation.
Hadoop Target Issue Setting high values for the 147932
"writeBufferSize" option would
result in high memory

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 13
Attunity Ltd.
 Component/Process Type Description Ref #
consumption.
Hadoop Target Issue An error would occur when 148609
trying to configure Huawei
Hadoop as a target.
Hadoop Target Enhancement Improved performance when 149606
using ODBC to access Hive.
Hadoop Target Enhancement Added support for field 153198
delimiter values ranging from
200 to 377 octal (128 to 255
decimal).
MySQL Source Issue Task would crash when parsing 149830
CDC strings with NLS
characters.
MySQL Source Issue The MySQL unsigned 147961
mediumint data type was
incorrectly replicated to the
target when the value
exceeded the high boundary.
MySQL Source Issue Full Load of a table with 4 147486
billion rows would stall at 2
billion rows.
MySQL Source Endpoint Issue The MySQL timestamp data 149504
type would appear with an
offset value on the target (e.g.
17:03:31 on the source would
be 22:03 on the target). This is
because MySQL converts
TIMESTAMP values from the
current time zone to UTC for
storage, and back from UTC to
the current time zone for
retrieval.
A workaround for this issue
was provided using the
following internal parameter:
serverTimezone
This should be set with the
MySQL Server time zone.

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 14
Attunity Ltd.
 Component/Process Type Description Ref #
MySQL Source Endpoint Issue Stopping a task and then 150833
resuming it would sometimes
result in missing UPDATEs on
the target.
MySQL Target Endpoint Issue Bulk Apply would return "0 145686
rows affected" when a key
value was NULL.
MySQL Target Endpoint Issue Memory leaks would occur 152008
when replicating data from a
MySQL source to a File target
on Linux.
IBM DB2 for LUW Source Issue An unclear "offset X is larger 148564
than buffer length Y ignore" 148566
message would be displayed in
the log. The message did not
indicate that the source table
was created with extended row
size (and therefore not
supported by Replicate).
This was resolved by making
the log message clearer.
IBM DB2 for LUW Source Issue Task would crash while parsing 148358
a variable string buffer.
IBM DB2 for LUW Source Issue The prerequisite for the IBM 147700
DB2 for LUW driver was not
correct in the help.
IBM DB2 for LUW Source Issue The SELECT query to get the 145352
table metadata would wait on a
lock and time-out when a table
was being updated by a long
transaction.
IBM DB2 for LUW Source Issue The endpoint would incorrectly 152004
log a warning message when
encountering a specific
unrecognized event.
IBM DB2 for LUW Source Issue Updating a source table to 152043
which columns were added
would cause the task to fail.
IBM DB2 for LUW Source Issue Capturing an IBM DB2 for LUW 153484

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 15
Attunity Ltd.
 Component/Process Type Description Ref #
rare complex update would
cause a crash.
Microsoft Azure SQL Data Issue An error would be generated 147887
Warehouse Target when loading a string field with
null value from a File Channel
source endpoint.
Microsoft Azure SQL Data Issue Replicate's behavior when 146718
Warehouse replicating source columns with
empty values to Microsoft
Azure SQL Data Warehouse
was not clear. The Help was
updated to make the behavior
clear.
Microsoft Azure SQL Data Issue The apply_exceptions table 148696
Warehouse Target would contain corrupt data due
to incorrect use of memory
pools.
AIS Source Issue The value 24:00:00 in the DB2 147910
for z/OS TIME data type would
not be replicated.
AIS Source Issue Events were not captured when 147656
Replicate AIS CDC started from
'now' and no CVS file existed.
File Target Issue Archiving a file compressed 147314
with gzip (after processing)
would fail.
PostgresSQL Target Issue Task would crash during 147276
target_lookup on a
PostgresSQL target.
Teradata Target Issue A typo in the td_data_ 150203
encryption internal parameter
prevented communications
from being encrypted between
Replicate Server and Teradata.
SAP Application Source Issue Table filtering would not work 149268
during Full Load.
SAP Application Source Issue An issue with the Oracle Binary 149943
Endpoint Reader would cause tasks to

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 16
Attunity Ltd.
 Component/Process Type Description Ref #
fail.
SAP Application Source Issue Initial load of BSEG table would 150777
Endpoint result in an error.
SAP Application Source Issue Capturing changes from a BSEG 150978
Endpoint table would result in an error.
SAP Application Source Issue When replicating from a BSEG 151601
Endpoint clustered table, Full Load would
take a long time and Change
Processing would not work at
all.
SAP Application Source Enhancement Replicating the Indexed Cluster N/A
Table STXL is now supported.
SAP Application Source Issue Due to an issue with handling 152150
non-consecutive column IDs,
the task would fail after adding
and removing columns to a
table.
ODBC With CDC Source Issue Removing and adding tables to 149175
a CDC task caused Replicate to
crash.
Sybase ASE Source Issue An error would be encountered 149730
when capturing data during a
Change Processing operation.
File Target Issue Resuming a task would fail 150666
when tables that were
originally included in the
replication were removed from
the source.
File Target Issue Task recovery would fail when 150877
tables that were originally
included in the replication were
removed from the source.
File Target Issue The row count in the DFM file 150844
would not match the row count
in the CSV file.
Kafka Target Issue An unnecessary warning 148276
message about the table not
having a primary key or a

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 17
Attunity Ltd.
 Component/Process Type Description Ref #
unique index would be
generated.
Kafka Target Endpoint Issue/Feature The Kafka target endpoint 151233
Request would fail to capture data from
partial records. A limitation
was added to the Help and a
feature request was opened.
Kafka Target Endpoint Issue Empty string values would be 153657
incorrectly applied as null
values.
UI - Transformations Issue Columns defined as NUMERIC 148998
(x,0) would be shown as
NUMERIC(x,-1) after saving
and then reopening the
transformation.
UI - Transformations Issue The UI would allow entering 149151
scale and precision for data
types in Global
transformations, even though
the server does not support
this.
UI - Transformation Issue A global transformation rule 147281
converting from numeric to
string would not work the first
time it was defined.
UI - Transformations Issue An error would be generated 148388
when trying to remove an
expression from a
transformation.
UI - Transformations Issue The Output column order could 148207
not be reverted to the original
table order. This was resolved
by adding a "Restore default
sorting" option to the UI.
UI - Tables Issue When trying to edit a table, the 148875
UI would stop responding after
removing a column using a
transformation and then
removing the column from the

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 18
Attunity Ltd.
 Component/Process Type Description Ref #
actual database.
UI - AIS Source Issue The setEventsTimeOffsetSec 148863
property would not support
negative values.
UI - Endpoints Issue Endpoint names displayed in 149831
the console would be truncated
when a task was selected.
UI - Monitor Issue The UI would show the 148143
WARNING messages even hen
clearing the warning message
option and switching between
tasks.
UI Monitor - Full Load By Design The "Estimated Finish Time" 145848
and "Time Remaining
(Estimated)" values are not the
same.
Reason:
The "Time Remaining
(Estimated)" value is calculated
by the combined transfer rate
of all the records of the task,
while the "Estimated Finish
Time" is calculated per table.
The discrepancy arises when
the table transfer rate at the
beginning of the task is very
fast, but slows down towards
the end of the task.
In this situation, the "Time
Remaining (Estimated)" value
will be greater and less
accurate than the "Estimated
Finish Time" value.
UI Designer Issue After changing the sorting 148530
order in the Table Settings >
Transform > Output list, the
original sorting order could not
be restored.
The issue was resolved by

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 19
Attunity Ltd.
 Component/Process Type Description Ref #
adding a "Restore Default
Sorting" option.
UI Designer Issue Using the [Ctrl] key for Full 152889
Load and CDC Filtering would
not work on a Mac. Now, on a
Mac, you can perform these
functions using the [Command]
key.
Sorter Issue After upgrading from Replicate 150251
5.0.4 to 5.2, tasks would start
to fail due to a conflict with
sorter transaction versions.
Sorter - Oracle to Kafka Issue Loading a table with many 150366
records while accumulating
many cached events would
result in unusually high
memory consumption.
Sorter and Logger Issue When recovering from a task 150420
crash, Replicate would
sometimes start the recovery
from the wrong place, resulting
in missing data on the target.
File Channel Issue When a task was stopped and 151334
Sorter restarted, transactions would
be applied to the target at a
much slower rate and the
target would fall progressively
further behind.
Sorter Issue Replicate would not capture 151361
INSERTs in a remote task from
Oracle to File Channel.
Transformations Issue SQLite would generated an 148543
internal error when using a
column name with a slash in a
table transformation.
The limitation was added to the
help.
Transformations Issue The outcome of transformation 147804
conflicts (Global Vs Table-

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 20
Attunity Ltd.
 Component/Process Type Description Ref #
specific) was not clear. A note
was added to the help clarifying
the matter.
Transformations Issue An incorrect error message 147805
was displayed when failing to
create table transformations.
Transformations Issue Transformation for binary data 147406
types would not work.
Installation Issue The installation would override N/A
the addons_def.json file.
Installation Issue Installation on Linux would fail 147811
when an existing group was
used.
Installation Issue Data directory would be N/A
created in the default location
even if the server was defined
to run with an alternative data
folder.
Silent Installation Issue Silent install would not return a 147945
warning when prerequisites
were missing. A note about the
prerequisites was added to the
Silent Installation section in the
Help.
Notifications Issue A error would occur when 148004
sending emails to an email
server that does bot support
bare <LF>.
Notifications Issue Notifications would not be 147872
modified after saving the
changes.
Upgrade Issue Upgrade to Replicate 5.1.2 148078
failed in a Windows
environment with FIPS
encryption.
Upgrade Issue Upgrading from 4.0.9 to 5.1.X 149469
or 5.2 would disable log roll
over.

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 21
Attunity Ltd.
 Component/Process Type Description Ref #
Installation Issue When the Replicate binaries 150935
and the Replicate "data" folder
were installed on different
drives, the shortcut to open the
console would not work.
Migration Enhancement Enabled migration path from a 147917
running server to a new server,
without the need to reload the
tasks.
Logging Enhancement The Change Table names were 147942
added to the task log, enabling
customers to delete them when
a task ends.
Logging Enhancement No messages were printed to 147068
the log when a task was in IDLE
mode.
This issue was fixed by printing
a message to the log every 10
minutes when Replicate is in
idle mode.
Logging Enhancement The sequence values were not N/A
included in the TARGET_APPLY
log.
Logging Enhancement Information enabling N/A
customers to measure the read
time of each archive log was
added to the SOURCE_CAPTURE
log in DEBUG mode.
Documentation Issue The explanation for the Target 149150
table preparation "Do
Nothing" option was not
accurate. The Help was
updated with a more accurate
explanation.
Documentation Issue A description of the metadata 148528
variables was missing from the
Help.
Documentation Issue Transformations would fail due 146287
to a known limitation. This

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 22
Attunity Ltd.
 Component/Process Type Description Ref #
issue was resolved by
modifying the transformation
limitations in the Help.
Documentation Issue The "Stop the task after Full 147386
Load completes and cached
changes have been applied"
was working correctly, but
appeared to be working
incorrectly. A note was added
to the Help explaining in more
detail how this option is
implemented.
Documentation Enhancement A note was added to the Help 148994
clarifying that the Scheduler 146259
will run a task according the
task's replication settings.
Documentation Enhancement Added a note to the description 147874
of the HQL scripts option in the
Help, clarifying that the target
storage format must be set to
Text.
Documentation Enhancement A note was added to the Help, N/A
advising customers to back up
the Data folder before upgrade.
Documentation Customer reported that a case 151859
number in the release notes
was incorrect. It transpired
that the case number was
correct, but for a different
customer (the same issue was
reported by several
customers). The customer's
case number was also added.
Documentation Issue Information for setting up the 149410
native IBM for DB2 for z/OS
endpoint was missing.
Documentation - Hadoop Issue Information about how to 149902
Target specify the cluster name when
using a Knox Gateway was
missing from the Help.

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 23
Attunity Ltd.
 Component/Process Type Description Ref #
Task - Engine Issue When resuming a Full Load task 150562
from a timestamp, Replicate 150823
would try to run the task in
Apply Changes mode, resulting
in task failure.
Engine - Change Data Issue Due to a possible issue with N/A
Partitioning Control Tables being included in
the batch partition, the task
would fail with the following
error:
The transaction timestamp
already exists in an earlier
partition.
The issue was resolved by
including these tables in the
partition and issuing an
appropriate warning in the log.
Replicate Server on Linux Issue When using a custom data 147983
folder, the Replicate service
could not be restarted after
being stopped using "kill -9".
Transactional Apply Issue It appeared that source 147526
changes were not being
immediately reflected in the
target. This was due to a failure
to properly understand the
impact of the Minimum
number of changes per
transaction option. The
explanation of this option in the
Help was expanded.
Metadata Manager Enhancement Added support for reloading a 147409
table when the task is in a
stopped state.
Change Tables Issue The CT table column [header_ 148769
_]change_seq would be
generated with a wrong
timestamp value of 19700101
instead of the actual timestamp

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 24
Attunity Ltd.
 Component/Process Type Description Ref #
Change Tables Issue When starting a task from 149171
timestamp, Replicate would
drop and recreate Change
Tables according to the policy
defined in the task settings for
"Store Changes." With this fix,
Replicate will only create
Change Tables if they do not
exist when a task is started
from timestamp.
Change Tables Issue After resuming a task, the 151100
timestamp would be missing
from the [header__]change_
seq column.
FTS Server Issue Stopping/reconnecting to the 148303
FTS server would sometimes
cause a crash.
Scheduler Issue The Scheduler date was not 146110
saved correctly.
Run Options Issue Enabling the Metadata Only. 150700
Create Missing tables and
then stop run option would
have no effect. A Full Load
operation would be performed
and the task would not stop.
Endpoint Shell Issue When retrieving tables, the 150696
endpoint shell would crash
upon encountering source
tables with a null owner.

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 25
Attunity Ltd.
 Known Issues
The table below lists the known issues for this release.

Component/Process Type Description Ref #

Microsoft SQL Server Issue Support for AlwaysOn Availability N/A
Groups is not available when
Replicate is installed on Linux.
File Transfer Service Issue Clicking the View Logs button in RPT-
Logs the File Transfer Service 8980
Logging Levels tab does not
display the logs.
Workaround:
Browse to:
C:\Program
Files\Attunity\Replicate\data\
repfts_defaultFts.log
Table Selection Issue When clicking the Search button RPT-
in the Select Tables window, the 8246
search continues indefinitely and
no error is shown (although an
appropriate error is written to the
logs).
This issue occurs when the user
defined in the source endpoint
settings does not have sufficient
permissions to view the tables. For
example, this issue will occur with
the Microsoft SQL Server endpoint
if the user does not have the db_
owner permission.
Note: In the event of such an
occurrence, you can close the
window by clicking the "x" in the
top right corner.

Copyright © 2017
Attunity Replicate 5.5 Release Notes - August 2017 | Page 26
Attunity Ltd.