This chapter describes the bugs fixed and enhancements at the time of release.
The Bug number is the number of the BugDB ticket. For questions on specific tickets or issues, consult Oracle Support.
Bug 28215602 - Automatically create streams in Kinesis
Two new properties added to the Kinesis Handler to auto create Kinesis streams, gg.handler.name.enableStreamCreation and gg.handler.name.shardCount.
Bug 28195145 - Initial load process JVM crashes on Linux x86-64
Replicat was changed to handle NULL CSN and XID values.
Bug 28079597 - PURGEOLDEXTRACTS not working correctly
Changed how PURGEOLDEXTRACTS operates so that all rules are added to the trail to process when there is no checkpoint in the installation.
Bug 27804821 - Update before image token not showing up in Kafka
The Kafka Handler was changed to use the mapped and target before record to populate the before values.
Bug 27525525 - Replicat issues with trail checkpoint and 9-digit trail sequence
Replicat was changed to correct an abend leading to an inconsistent checkpoint file, which caused a problem positioning upon restart. One of the symptoms of this issue is that the Replicat mistakenly assumes that it should reposition to a 6-digit sequence number rather than 9-digit.
Bug 27299518 - SQL is replicated as binary (base64) instead of string
The Kafka Handler was corrected so that a uniqueidentifier column is replicated to the target as a base64 string.
Bug 26957243 - CVE-2017-5645: APACHE LOG4J UPGRADE TO 2.9.1
Due to security issues in log4j component, the log4j version was upgraded to log4j 2.9.1.
Bug 26851391 - File Writer Handler - Target data missing Operation counts
The File Writer Handler was changed to count of operations be provided on data files written to HDFS to provide assurance that all records are processed. This is for an ELT scenario.
Enh 25677977 - Enhancement request to correct the DateString format from operation.getTimestamp
Enh 25289618 - Change the HDFS Handler’s timestamp format to `yyyy-mm-dd hh:mm¿
Enh 24704644 - Where does "op_ts" milliseconds in time stamp value comes from?
With the HDFS Handler, the timestamp data output format is exactly how it is represented in the trail record. The handler was changed so that you can consolidate all of the timestamp output format using the gg.format.timestamp property. The value of this property must follow the specification described in:
https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html.
Bug 27012878 — ReverseProxySettings application has two new parameters
TheReverseProxySettings application has two new parameters in Oracle GoldenGate version 12.3.0.1 and later:
-P: Password for Service Manager account
-u: Name of Service Manager account to use
Doc 27033479 — New option, SQLMODE, is added for the DBOPTIONS parameter
The SQLMODE option is added for the DBOPTIONS parameter. When this option is enabled, the sql_mode variable is set to ‘ANSI_QUOTES’.
Doc 27061717 — Oracle: Replicat issues replicating TIMESTAMP (6) with TIMEZONE
The daylight saving time adjustment issue when UTC timestamp value converted from local timestamp hits daylight saving time transition period was fixed. From standard time to daylight saving time 1 hour window. Replicat applies timestamp value 1 hour off from expected value.
Bug 26742447 — SQL Server: Replicat abends with OGG-10124 parsing error for REPERROR value
The REPERROR option allowed 1-7 digits of error code only, whereas the SQL Server error code contains 10 digits. To fix this, the regular expression was modified to accumulate 10 digits of SQL Server error code.
Bug 27964981 — Oracle: Extract writes number of bytes > max length for the column to the trail file
An issue with Extract data in the trail file was incorrect when the VARCHAR size is more than 32767 bytes was fixed.
Bug 27078084 — Oracle: Integrated Extract captures all columns for delete operations
Fixed as issue where Replicat fails with errors like OGG-01163 Bad column length (nnnn) specified for colum xxxx. This issue occurs because the database NLS_CHARACTERSET is AL32UFT8 and NLS_NCHAR_CHARACTERSET is UTF8. NVARCHAR2 has a byte limit of 4000 bytes. For UTF8, 4000 chars is equal to 4000 bytes. However, Oracle GoldenGate stores NVARCHAR2 in the trail as UTF16, which causes it to expand it to 8000 bytes.
Bug 28043789 — Oracle: @DATE function with @COMPUTE does not work
An issue where the DATE() failed if used as an argument of another column mapping function was fixed.
Bug 26869744 — Oracle: Extract Truncating The Column Data When Used with Coltest
An issue with mapping functions truncating numbers that have more digits than the number of bytes needed to store the target number was fixed
Bug 27701581 - Increase the upper limit of the DBOPTIONS parameter options LOBBUFSIZE and XMLBUFSIZE
The upper limit for LOBBUFSIZE and XMLBUFSIZE was increased from 10485760 to 104857600.