Chat now with support
Chat with Support

SharePlex 8.6.6 - Release Notes

Release Notes


SharePlex™ 8.6 (8.6.6)

Release Notes

Revision: 8/16/2017

 

About SharePlex

SharePlex provides high-speed replication from Oracle and SQL Server databases to different target databases and messaging containers on major Unix, Linux and Windows platforms.

On the Oracle platform, you can also configure SharePlex to maintain a change history database. Rather than overlaying current target data with the data that changed on the source (as in a regular replication configuration) SharePlex inserts a new row for every change to provide a chronological history of all changes that were made to the source database. Optionally, you can add metadata columns to each row to include context information about the change that was made.

For expert advice and the latest news about SharePlex, join the SharePlex Community at www.shareplex.com/community. Take advantage of our forums, blogs, videos, and more from our own experts, as well as input from our customers and partners.

New Features

New features in this release

The following new features are introduced in this release.

For more information about each of these features, see the documentation that is provided with this release.

Support for SQL Server 2016

SharePlex expands SQL Server support to include replication to a SQL Server 2016 target.

Support for all implementations of PostgreSQL

SharePlex now supports all implementations of the PostgreSQL standard. Mentions of this database type in the documentation have been changed to the generic term "PostgreSQL" unless a specific name is required. Always refer to the SharePlex Release Notes for the version of PostgreSQL that SharePlex supports and for any other specifics that relate to its various vendors.

Queue contention reduction

The new queue contention reduction feature preserves the performance of Post when there is a large backup of messages in the post queue. It is controlled by the following new parameters.

  • SP_IMP_QUEUE_PAUSE: This parameter enables the new queue contention reduction feature. It stops Import from writing data to the post queue when that queue has a specified number of messages. Use this parameter to maintain Post performance when there is a high backlog of messages in the post queue. The use of this parameter prevents Post from running out of shared memory and incurring file IO when the system switches to disk storage.
  • SP_IMP_QUEUE_RESUME: This parameter sets a value for queue backlog at, or below, which Import resumes writing to the post queue.

See the SharePlex Reference Guide for more information.

Logical transaction rollback

You can now configure Post to roll back and discard a transaction if it contains any out-of-sync operations. This functionality is controlled by the SP_OPO_SAVE_OOS_TRANSACTION parameter. When this parameter is set to 1 and a transaction contains any operations that generate out-of-sync errors, Post discards the entire transaction and saves all the operations of that transaction to a SQL file. You can edit this file to repair the problem with the failed SQL and then run the file to apply the transaction to the target database.

Note: All of the tables involved in the transaction that is being rolled back must contain only the following data types. No other data types are supported at this time.

  • CHAR – US7ASCII
  • VARCHAR – US7ASCII
  • NUMBER
  • DATE
  • TIMESTAMP
  • TIMESTAMP WITH TIME ZONE
  • TIMESTAMP WITH LOCAL TIME ZONE
  • INTERVAL
  • ROWID
  • RAW
  • BINARY FLOAT
  • BINARY DOUBLE

See the SharePlex Reference Guide for more information.

Improved queue indexing

The performance of the Post queue was enhanced. This feature uses improved indexing to access the subqueue structures that represent a transaction session. A message "Subqueue index enabled queuename" is written to the Event Log for every Post queue for which this parameter is enabled. To enable this enhancement, set the new SP_QUE_USE_SUBQUE_INDEX parameter to 1.

See the SharePlex Reference Guide for more information.

New hash horizontal partitioning algorithm

SharePlex offers a new option to horizontally partition a table based on the block where the row resides. To enable it, set the new SP_OCF_HASH_BY_BLOCK parameter to 1, then re-activate the configuration file to enable it. Note that activation will lock the tables that are hash partitioned so that they are not part of an open transaction when the algorithm is changed.

Delivery to multiple Kafka partitions

A new partition parameter has been added to the target command to enable posting to multiple Kafka partitions. You can set this option to one of the following:

  • A fixed partition number: Directs Post to post messages only to the specified partition number. For example, setting it to 0 directs Post to post only to partition 0. This option is suitable for use in testing or if the target has multiple channels of data posting to the same Kafka topic.
  • The keyword rotate: Directs Post to apply messages to all of the partitions of a topic in a round-robin fashion. The partition changes with each new message. For example if a topic has three partitions, the messages are posted to partitions 0,1,2,0,1,2, and so on in that order. This option is suitable if you want to replicate each table to a unique topic.
  • The keyword rotate trans: This is similar to the rotate option, except that the partition is incremented with each transaction rather than with each message. For example, if a topic has three partitions, the messages are posted to partition 0 until the commit, then to partition 1 until the commit, and so on in that order. This option is suitable if you are replicating multiple tables to a single topic. It allows you to distribute data across several partitions, while still preserving all of the operations of a transaction together in a single partition. This enables a consumer that reads from a single partition to receive a stream of complete transactions.

The string in the topic parameter of the target command can now contain the special sequences %o or %t. The %o sequence is replaced by the owner name of the table that is being replicated. The %t sequence is replaced by the table name of the table that is being replicated.

The broker parameter of the target command can now specify a comma delimited list of multiple brokers.

The Kafka client parameter request.required.acks is now a target parameter.

Post to Kafka has been improved in the following ways:

  • Errors are now categorized into fatal and non-fatal errors.
  • For non-fatal errors. Post retries the operation if appropriate. If the retries fail, Post exits and then sp_cop starts a new Post, which resets the connection so that the operation can be tried again.
  • Fatal errors cause Post to stop.
  • If the cluster is not responding and Post has sent the maximum amount of data, it waits the number of seconds specified with the target parameter of restart_timeout. Post then exits and then sp_cop starts a new Post, which resets the connection so that the operation can be tried again.

See the target command documentation in the SharePlex Reference Guide for more information about these parameters.

Oneline debug

The oneline debug feature enables you to perform debugging for out-of-sync errors without consuming a large amount of the system resources. The oneline debug logs just enough information in one line to detect where in the data stream an out-of-sync condition occurred. Once oneline debug identifies the process that is causing the problem, you can then enable regular debugging for that process.

See the SP_process_ONELINE_DEBUG parameters in the SharePlex Reference Guide for more information.

Table to capture conflict resolutions

You can now configure SharePlex to log the results of conflict resolution to a table named shareplex_conf_log. The table captures information such as the type of conflict resolution that was used, the operation type, the names of the key columns, and other information about the affected row data. This feature is for use only with the prepared routines that are provided by SharePlex. It can be enabled or disabled with the new SP_OPO_LOG_CONFLICT parameter, and is disabled by default. See the SharePlex Administrator Guide for more information about configuring peer-to-peer, or active-active, replication.

Replication of DDL for Triggers, Grants, and Synonyms

SharePlex can now replicate the following commands made on tables that are listed in the configuration file:

  • CREATE SYNONYM and DROP SYNONYM: To enable, set the new SP_OCT_REPLICATE_SYNONYM parameter to 1.
  • GRANT: To enable, set the new SP_OCT_REPLICATE_GRANT parameter to 1.
  • CREATE TRIGGER and DROP TRIGGER: To enabled, set the new SP_OCT_REPLICATE_TRIGGER parameter to 1.

New Secure Mode

The SP_SYS_SECURE_MODE environment variable was added to enable compare/repair to skip the logging of SQL statements when the variable is set to 1.

See the SharePlex Administrator Guide for more information about environment variables.

Enhancements

Enhancements in this release

The following is a list of enhancements that were implemented in this release line.

8.6.6

Enhancement Issue ID
Added auto-add support for GRANT on tables in replication. See the New Features section of these release notes for additional information. CR112239
Added auto-add support for CREATE and DROP SYNONYM on tables in replication. See the New Features section of these release notes for additional information. CR112245
Added auto-add support for CREATE and DROP TRIGGER on tables in replication. See the New Features section of these release notes for additional information. CR111917
Added a table to contain the results of conflict resolution. See the New Features section of these release notes for additional information.

CR 112360

CR112439

SPO-2449

Made the use of a connection pool in Post the default. A new parameter, SP_OPO_CONNECTION_POOL, controls how Post uses the connection pool. See the SharePlex Reference Guide for more information about this parameter. CR112347
SharePlex now supports Sybase bigdatetime. CR112430
Enhanced hash-based horizontally partitioned replication to support hashing on just the file and block instead of the entire rowid. See the New Features section of these release notes for additional information. SPO-3081
Improved Kafka support. See the New Features section of these release notes for additional information. SPO-3180
Added the SP_SYS_SECURE_MODE environment variable to enable compare/repair to skip the logging of SQL statements when the variable is set to 1. See the SharePlexAdministrator Guide for more information about environment variables SPO-2441

8.6.5

Enhancement Issue ID
Added new parameter SP_OCT_REPLICATE_MVIEW to control whether materialized views listed in the configuration file are replicated. CR112307
Enabled the mapping of Oracle number datatype to HANA decimal.

SPO-2383

SPO-2395

8.6.4

Enhancement Issue ID
Improved the speed of the Post process when processing CREATE/DROP TABLE. 111961

8.6.3

Enhancement Issue ID
Enhanced oneline_debug to include odr_time

SPO-1864

CR 111893

Added a SHAREPLEX_CHANGE_ID column to add_change_tracking_columns.sql CR 110763
Added the SP_OPX_REDUCED_KEY parameter. CR 111461
Capture now can be configured to read from the archived log, rather than the online log, if it is available. The new parameter SP_OCT_PREFER_ARCHIVE enables this feature when set to 1. CR 111182
Added new properties and client_ID properties to JMS category of the target command to support additional JMS targets. CR 111387
Added new options to the compare and repair commands. SPO-878
Added auto-add support for sequences. SPO-915
Expanded horizontally partitioned replication to support partitioning by a hash value. SPO-958
Open Target Post was updated with the option to remove certain headers from being sent to the JMS broker. SPO-1286
Open Target Post was updated with the option to set a connection ID for a JMS target. SPO-1287

8.6.2.44

None

8.6.2.48

Enhancement Issue ID

Enhanced Capture to process higher volumes of data from Exadata in the event that a backup develops when reading the online logs. With this enhancement, Capture can read from a multiplexed archive location outside of the Exadata ASM file system. When a required log is online, Capture makes an additional check to determine whether that log has been archived. If true, then Capture reads from the archived log instead of the online log. This enhancement must be enabled by setting the SP_OCT_PREFER_ARCHIVE parameter to a value of 1. The path to the secondary archive logs must be set with the SP_OCT_ARCH_LOC parameter, and the SP_OCT_CK_LOC_FIRST parameter must be set to 1 so that Capture looks for the archive logs in the secondary location, rather than the Oracle default location.

111,182

111, 659

Suppressed Out of Sync functionality was added for DELETE operations. 111,579

Added automatic validation of the ODBC driver that SharePlex is configured to use to connect to a SQL Server target database. The correct driver is the Microsoft SQL Server ODBC Driver, not the Microsoft SQL Server Native Client driver. SharePlex will return an error when mss_setup is run if the correct driver is not used.

SPO-1361

8.6.2

Enhancement Issue ID
You can now configure SharePlex to include NULL column values in INSERT statements. See the new SP_OCT_INSERT_INCLUDE_NULLS parameter in the SharePlex Reference Guide. 110658
You can now include unchanged columns in the after image for UPDATE operations. See the new SP_OCT_INCLUDE_UNCHANGED_COL parameter in the SharePlex Reference Guide. 107139
Users with spview authority can now run a compare command. 110661
A new environment variable was added to enable users to override the default umask set by SharePlex. 108810
Enhanced the handling of ASM block requests. 109632
Queue performance was enhanced. 110555
Enabled column information for one-line debug for Capture and Read to help debug out-of-sync rows. 110665

8.6.1

There are no enhancements in this version.

8.6.0

Enhancement Issue ID
Added a nolock option that prevents the compare process from locking the target tables during the compare phase of a compare-repair run. Normally, the tables are locked momentarily during the compare phase to get a read-consistent view, and then unlocked immediately. Target tables are always locked during the repair phase of a compare-repair run, as well as during a repair-only run. Source tables are locked momentarily during a repair to get a read-consistent view. 94322
Show capture was enhanced to make it more clear when Capture encounters a log wrap. 108715
Activation was enhanced to support escaping the underscore (_) character in a wildcarded table name. 105257
Added ora-2292 to the list of constraint errors. 109052
Expand the functionality of SP_OPO_TRACK_PREIMAGE with an additional value of 2, which provides a before image for inserts and an after image for deletes. The preimage for the insert and the after image for the delete have the key column populated and the non-keys are null. 109231
Added the ability to get the change history (formerly known as CDC) rule from a file. 109041
Compare/Repair now supports up to 1,000 key columns. 109242

Deprecations

Deprecations in this release

This section contains a list of SharePlex items that were deprecated in this release line.

Note: For a list of all deprecated parameters and commands, their replacements (if any), and the version of SharePlex in which they were deprecated, see the SharePlex Reference Guide.

8.6.6

SP_OCT_REPLICATE_DR_DDL parameter was renamed to SP_OCT_REPLICATE_TRIGGER. The old parameter is still functional for backward compatibility.

The SP_OPO_CONF_LOG parameter was renamed to SP_OPO_LOG_CONFLICT. The old parameter is still functional for backward compatibility.

The date and timestamp options were removed from the format category of the target command.

8.6.5

None.

8.6.4

SP_OPX_CHECKPOINT_FREQ parameter (replaced by the commit_frequency option of the target command)

8.6.3

SP_DEQ_LOG_ROW_DATA parameter

SP_COP_WALLET_PATH parameter

SP_DEQ_LOG_ROW_DATA parameter

8.6.2

SP_OPO_RESTRICT_ALL_REF_CONS (due to the support for Post to ignore ON DELETE CASCADE constraints).

8.6.1

No components were deprecated in this version.

8.6.0

Deprecated commands:

  • Deprecated the -nolockboth, -nolocktarget, -nolocksource options of the compare command. These are replaced by the nolock option.
  • The set odbc options of the target command are deprecated. The new connection command handles these options now. (missing or bad snippet)

Deprecated parameters:

These parameters are deprecated in 8.6 due to the enhancements in Oracle Setup.

SP_ORD_LOGIN_O

SP_ORD_OWNER_O

SP_OCT_ASM_CONNECT_DESC

SP_OCT_ASM_SID

 

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents