SharePlex® 9.2.10
Release Notes
Revision: 4/7/2021
| New Features |
| Resolved Issues and Enhancements |
| Basic system requirements |
| System requirements for Oracle |
| Known issues |
| Product Licensing |
| Third Party Contributions |
SharePlex provides high-speed replication from Oracle database to different target databases and messaging containers on major Unix, Linux and Windows operating systems— both on-premises and in the cloud. SharePlex supports a wide variety of configurations to meet different and complex data availability needs.
SharePlex supports reliable Oracle high availability configurations where replication maintains a duplicate database in a different location that is ready for fast, seamless failover and failback in planned or unplanned mode.
You can also use SharePlex to replicate data from Oracle source to maintain a change history database in an Oracle target. Rather than updating or deleting target rows based on the source change, SharePlex inserts a new row on the target for every source change. The result is an archive that reflects the chronological history of every change made to the source database.
SharePlex also includes, at no extra charge, the compare and repair tools that you need to verify the accuracy of a target maintained by replication. These tools not only detect hidden out-of-sync conditions, but they also repair the target to restore parity of your source and target data.
SharePlex value and versatility continues to grow with the requirements and requests of our customers. Although SharePlex is a reliable, relatively low-maintenance solution, our top-rated support team is ready around the clock to help with any trouble you may have. To get you started with your deployment, our professional services team is highly experienced and readily available.
For expert advice and the latest news about SharePlex, join the SharePlex Community at https://www.quest.com/community/products/shareplex. Take advantage of our forums, blogs, videos, and more from our own experts, as well as input from our customers and partners.
This is a minor release and includes new features and enhanced functionality.
SharePlex 9.2.10 is a patch release and includes resolved issues. See Resolved Issues and Enhancements for a complete list.
SharePlex has put bug fixes into a cumulative update rollup (denoted by third digit in the version number)—starting with the 9.2.3 release. Customers that require bug fixes which are already available in a patch update rollup will be required to apply that patch release to get the bug fix.
SharePlex 9.2.9 is a patch release and includes resolved issues. See Resolved Issues and Enhancements for a complete list.
SharePlex 9.2.8 is a patch release and includes resolved issues. See Resolved Issues and Enhancements for a complete list.
SharePlex 9.2.7 is a patch release and includes resolved issues. See Resolved Issues and Enhancements for a complete list.
SharePlex 9.2.6 is a patch release and includes resolved issues. See Resolved Issues and Enhancements for a complete list.
SharePlex 9.2.5 is a patch release and includes resolved issues. See Resolved Issues and Enhancements for a complete list.
Oracle Cloud Infrastructure as a Service (IaaS) Compute Virtual Machine is now supported as a target.
SharePlex 9.2.4 is a patch release and includes resolved issues. See Resolved Issues and Enhancements for a complete list.
SharePlex 9.2.3 is a minor release and includes resolved issues. See Resolved Issues and Enhancements for a complete list.
SharePlex 9.2.1 is a minor release and includes the following new features and enhanced functionality.
Oracle 18c. This release includes support for capture from and replication to Oracle 18c.
Note: SharePlex does not support replication of DML operations on objects compressed using OLTP Compression in Oracle 18c. This limitation applies to objects in the source database.
Kafka 1.1.x. This release includes support for replication to a Kafka 1.1.x target.
Operating System Support. This release includes support for SuSE SLES 15.
SharePlex installer packages for Linux/Unix. SharePlex installer packages for Linux/Unix are now database independent. You are no longer required to select an installer package based on the database for which SharePlex will be used (i.e., Oracle or Open Target). To install SharePlex for Oracle or Open Target, simply select the installer package for your operating system.
The SharePlex installer packages now have a slightly different naming convention:
SharePlex-release#-build#-platform-chipset.tpm
For Oracle Solaris (Sun), the operating system version is included:
SharePlex-release#-build#-platform-version-chipset.tpm
SharePlex 9.2 is a minor release and includes the following new features and enhanced functionality.
Oracle UROWID data type. Support has been added for the Oracle UROWID data type. This support applies to Oracle-to-Oracle configurations only.
Support for SCN metadata for HANA target. This release of SharePlex supports posting the Oracle SCN to a column in a HANA target table.
Oracle replication to MySQL 5.7. SharePlex supports replication from an Oracle source to a MySQL 5.7 target on-premises.
Support for 128-byte table and column names. In Oracle capture, SharePlex now supports table and column names that are up to 128 bytes in length. Please note the following limitations applicable to this release.
Support for Windows Server 2016. Support for capture from and replication to databases on Microsoft Windows Server 2016.
Improved Performance in the Post Process.
The following enhancements were made to improve performance of the Post process.
New jobs status database
Simplified SharePlex Installation Process on Windows
This release of SharePlex includes a new typemap command, as well as changes to the default data type mappings. Review the following details.
TLS 1.2 (or later) required for TLS connections. If you intend to use TLS connections in SharePlex, TLS 1.2 or later is required.
The following is a list of issues addressed and enhancements implemented in this release of SharePlex.
NOTE: SharePlex has put bug fixes into a cumulative update rollup (denoted by third digit in the version number) — starting with the 9.2.3 release. Customers that require bug fixes which are already available in a patch update rollup will be required to apply that patch release to get the bug fix.
| Issue ID | Description |
|---|---|
| SPO-21181 | Compare/Repair could report a false OOS. This issue is more likely to occur when comparing a single column table without keys. |
| SPO-21081 | SharePlex is unable to compare the tables that are not in the active configuration file using the Compare Force option. The issue is resolved now. The functionality of comparing data that is outside of the replication was removed from SharePlex 9.0 version onwards. However, now, we have added this functionality back into the product for the 9.2.10, 10.0.1, 10.1 versions. |
| SPO-21076 | The memory usage of the SharePlex capture process named "sp_ocap" started increasing after running for a month due to the allocation / de-allocation of the typecheck object. |
| SPO-21072 | SharePlex poster stopped while replicating the data from the source database to the target database due to an invalid length in a column. The issue is observed in the CDC environment. |
| SPO-21058 | SharePlex capture process stops due to an Oracle error whenever the RAC database is restarted. Users need to start the capture manually. |
| SPO-21054 | SharePlex stopped while replicating the Oracle heap organized tables that are altered with the external tables after renaming the table name. The capture was discarding the external table as invalid. This issue was observed intermittently after upgrading from 8.1.6 to 9.2.6. |
| SPO-21050 | SharePlex poster dumped core due to the column data set inappropriately in the key cache. This issue is observed only when the supplemental logging is not set on the source. |
| SPO-21047 | SharePlex capture displayed a full disc space error on a NAS drive immediately after initiating the database replication process, even when there is enough space on the disc. |
| SPO-21042 | Using non-ASCII characters as part of horizontal partitioning column conditions are not accepted via sp_ctrl. SharePlex reader process fails to evaluate such conditions. This issue exists for SharePlex versions 9.x up to 9.2.9. Reader evaluation issue is now resolved if the below workaround for mentioned sp_ctrl issue is performed. Workaround: Edit horizontal_partitioning.yaml file to input the non-ASCII characters since sp_ctrl rejects non-ASCII character input. |
| SPO-20946 | SharePlex is unable to display before and after images for the deleted records/rows in the CDC environment even when the sp_opo_track_preimage D parameter for delete is set. This issue is observed after upgrading from SharePlex 9.1.4 to 9.2.8. |
| SPO-20942 | SharePlex poster stopped while performing the cascading replication from source database to target database due to invalid columns and invalid objects in the cache. This issue is observed when bulk updates are being applied such as multiple table creation, peer-to-peer replication, and performing the DDL and DML activity. |
| SPO-20939 | sp_utils does not display the license information for the SharePlex product in the license tab but the customer is able to fetch the license information using splex_get_key. This issue is specific to the windows operating system. |
| SPO-20931 | SharePlex is giving reader core dump in a horizontally partitioned table. |
| SPO-20929 | SharePlex poster dumps core when PEP tries to obtain a row ID for the NOP messages. |
| SPO-20921 | SharePlex capture is dumps core and gets memory corruption issue when handling Multi-Block Undo records for 12C or above version of the Oracle database. |
| SPO-20916 | Tables get out of synchronization when a user tries to replicate a horizontally partitioned HP table without a primary key on a dependency check enabled setup. This issue is observed specifically after upgrading from the SharePlex 9.1.4 to 9.2.6 version even after a user performs the full repair. |
| SPO-20914 | SharePlex reader displays an error when a table is dropped without a table name on the source database after updates are accumulated on the capture queue. This issue is observed intermittently while running an internal upgrade application process in the database after upgrading to SharePlex 9.2.7 on a database where PK/UK is not enabled. |
| SPO-20911 | In the peer-to-peer configuration, SharePlex is unable to replicate the updated information in a row from the source to the target database due to the conflict found in the target database. In the debug process, SharePlex is not able to find the pre-image record to resolve the conflict. |
| SPO-20780 | SharePlex encounters stale blocks in the online log during data replication when the SharePlex was in the remote-connection capture mode. The issue is resolved. When a stale block is detected a switch command is sent to Oracle to switch the log from online log to archive log and the capture reads the data from the archive log. |
| SPO-20663 | SharePlex declines the transaction, which has only LMN records without any HRID value, with 'NULL HRID' warning message. This issue is resolved now. SharePlex now declines the transaction without generating the 'NULL HRID' warning message. |
| SPO-20623 | SharePlex capture process dumps core while trying to read an archive log from a perpetually down node on a RAC environment. |
| SPO-20330 | While cross replicating the data from Oracle to the Windows SQL server, the SharePlex poster is performing the delete operation very slow on tables and most of the tables are displayed out of synchronized. Due to this, a heavy backlog is observed for a particular queue. |
| SPO-20012 | SharePlex poster stopped while executing an insert statement on an object in the target database. It stopped due to an invalid length of the variable character string even when the source and target are having the same structure. This issue is observed while processing the corrupt data specifically the special characters. |
| SPO-19967 | SharePlex capture's parser dumps core while decompressing the OLTP compressed DLOAD records. This issue is observed when the data size of the DLOAD record exceeds the size of the standard message. |
| SPO-19927 | SharePlex is getting an issue while accessing a VARDIR installed on a network drive on Windows environment. |
| SPO-19318 | SharePlex capture process stopped with an error when the DB max sessions per node (5 nodes) was set to 4000 each. Maximum number of concurrent oracle sessions for DDL and DML are now increased to 5000 per node. |
| SPO-17695 | SharePlex was unable to replicate data from source database to target database when the table data has UDT (User Defined Data Type) and LOB data. This issue was observed on the SharePlex 9.2.1 version. |
| Issue ID | Description |
|---|---|
| SPO-20665 | Fixed inconsistent processing of trailing NULL on chained row preventing it from properly replicating to Kafka. |
| SPO-20651 | Replication of comments on DDL can be disabled by setting SP_OCT_REPLICATE_COMMENT to 0. DDL replication is enabled by setting SP_OCT_REPLICATE_DDL to 1, 2, or 3. |
| SPO-20562 | Fixed cleanup of routing files to after activation is successful. |
| SPO-20524 | Fixed CREATE TABLE AS SELECT DDL not replicating correctly when DDL user is different from schema owner. |
| SPO-20454 | Fixed logic in Compare to work properly even when character set between endpoints are superset or subset of each other when SP_DEQ_CONV2UTF8 is enabled. |
| Issue ID | Description |
|---|---|
| SPO-20426 | Fixed Capture DDL replication of grant on commit refresh |
| SPO-20139 | Fixed Capture DDL processing of chained row in system table |
| SPO-20125 | Fixed Post XML missing trailing null columns |
| SPO-20033 | Fixed Windows issue with stopping SharePlex processes from Services |
| SPO-20024 | Fixed Post memory leak due to rollbacks |
| SPO-19633 | Fixed Compare/Repair issue where invalid duplicate checksums reports OOS |
| SPO-17868 | Fixed Post conflict resolution existing win log message output for most and least recent |
| SPO-19872 | Fixed performance issue with large partial rollbacks. |
| Issue ID | Description |
|---|---|
| SPO-19907 | Fixed ignored DDL when source and target database endianness are different |
| SPO-19834 | Fixed Post stopping when object cache missing from previous activation |
| SPO-19734 | Fixed Chinese NCHAR & NVARCHAR2 characters not showing up correctly in Kafka |
| SPO-19722 | Fixed Capture core when processing DLOAD from OLTP tables |
| SPO-19563 | Fixed Capture core when issuing DDL alter table modify on XML type column |
| SPO-19494 | Fixed Chinese NVARCHAR2 characters no showing up in Kafka |
| SPO-19468 | Fixed commits not routing to Post due to bad bitmaps in Read |
| SPO-19458 | Fixed compare ignoring nolocksource and nolocktarget parameters |
| SPO-19448 | Fixed Reader redundant processing rollback updates when using horizontal partition |
| SPO-19070 | Fixed VARRAY corrupting XML in Kafka |
| SPO-19003 | Fixed extra data appearing in XML from bad VARRAY parsing in Kafka.NOTE: VARRAY element in XML is fixed to now correctly be a child element of the parent column. VARRAY will no longer appear as a sibling to the column. |
| SPO-18985 | Fixed out-of-sync when operations are related using distributed transactions |
| SPO-18931 | Fixed Post DDL error creating table using materialized views |
| SPO-18875 | Fixed Post stopping when JMS not responding. Post will now retry automatically. |
| SPO-18800 | Fixed Linux endianness posting to Kafka causing invalid characters |
| SPO-18405 | Fixed posting bad records when using OLTP |
| SPO-18157 | Fixed Capture to correctly skip filtered out DDL |
| SPO-18154 | Fixed invalid numeric data by setting the value to zero when condition met in Capture |
| SPO-18146 | Fixed Open Post stopping when DDL messages are only updating object cache |
| SPO-18138 | Fixed CTAS issues when using non-qualified schema |
| SPO-17856 | Fixed Post error ORA-29877 on update table containing SDO_GEOMETRY column but not part of the update |
| SPO-17693 | Fixed upgrade issues from 9.2.1 when processing older DDL cache version |
| SPO-16944 | Fixed Post to properly update LOBs when using CDC |
| SPO-15820 | Fixed errors using Oracle Filter Driver with ASM disks in native mode |
| SPO-5032 | Fixed Poster error ORA-1805 using time zone |
| Issue ID | Description |
|---|---|
|
SPO-19151 |
Resolved capture performance issues when data not ready in log |
|
SPO-18872 |
Fixed post issues with delete-n where some columns contains NULL |
|
SPO-18866 |
Resolved corruption using alter table DDL on long name table |
|
SPO-18850 |
Resolved offset calculation on SecureFiles CLOB with Japanese CharSet |
|
SPO-18838 |
Resolved issue with alter table DDL using dbms_job package |
|
SPO-18798 |
Fixed SP_OPX_REDUCED_KEY=2 using update containing keys and non-keys |
|
SPO-18628 |
Fixed issue with create public synonym |
|
SPO-18625 |
Fixed conversion issues with SJIS Ⅱ symbol |
|
SPO-18615 |
Fixed SQL Server ODBC driver issues using float |
|
SPO-18501 |
Fixed post inserting CLOB with ORA-64204 error |
|
SPO-18402 |
Fixed corruption issues in object cache on tables with UDT |
|
SPO-18169 |
Compare now properly supports configurations that use compound routes |
|
SPO-18029 |
Fixed issue with converting exponential number with some SQL Server ODBC drivers |
|
SPO-17592 |
Fixed conversion issues with UTF16 Chinese |
|
SPO-17318 |
Fixed installation issues as root on Red Hat |
|
SPO-17005 |
Fixed issue replicating insert operation on compressed tables |
|
SPO-10528 |
Resolved issue with parsing SecureFiles LOB where data object ID not extracted |
|
SPO-10282 |
Fixed capture to better handle alter table shrink table |
|
SPO-3828 |
Changed read update of SharePlex marker to once per second |
| Issue ID | Description |
|---|---|
| SPO-10592 | Fixed post failure when executing 'alter index' with a fully-qualified index name for table replicating to a different schema on target. |
| SPO-15132 | Fixed messages not getting sent when using DML filtering. |
| SPO-16402 | Fixed XML/JSON document types to format null & empty data as attributes. |
| SPO-17528 | Fixed XML document emitting extra tags for CDC. |
| SPO-17863 | Fixed network issue when using SSL. |
| SPO-17991 | Fixed sp_utils not properly showing port numbers. |
| SPO-18202 | Fixed post error recovery accessing row of a record after insert error. |
| SPO-18224 | Fixed read error when using DML filtering |
| SPO-18259 | Fixed better recovery handling after encountering SSL error. |
| SPO-18321 | Fixed export using SP_SYS_HOSTNAME IP when set |
| SPO-18419 | Enhanced capture performance. |
| SPO-18487 | Fixed post shutdown due to ORA-01458 after upgrade and SQL cache is enabled. |
| SPO-18501 | Fixed automatic detection of UTF16 CLOB data. |
| SPO-18527 | Fixed internal routing data to better handle non-UTF8 characters. |
| SPO-18617 | Fixed parsing of DLOAD record with OLTP. |
| SPO-18794/4506554 | ON CASCADE DELETE constraints are now supported. |
| Issue ID | Description |
|---|---|
| SPO-16402 | Corrected XML messages not properly tagging NULL or EMPTY columns |
| SPO-17528 | Resolved XML messages including extraneous metadata |
| SPO-17991 | Fix Windows 'SharePlex Utilities' not showing correct port number for associated processes |
| SPO-18321 | Fix export not using SP_SYS_HOST_NAME parameter value |
| SPO-18419 | Resolved capture performance issues |
| SPO-18487 | Fix post stopping due to ORA-1458 after upgrading when SQL cache is enabled |
| SPO-18501 | Fix post stopping due to ORA-600 or ORA-64204 when using CLOB caused by incorrect character set parsing |
| Issue ID | Description |
|---|---|
| SPO-17377 | Corrected an issue that caused the Post process to stop with the following error: "ORA-01741: illegal zero-length identifier." |
| SPO-17384 | Corrected an issue in which a DDL transaction (alter table to add partition) was not processed successfully after a database upgrade. |
| SPO-17507 | Resolved an issue which caused the Repair process to fail because the SQLite marker table used in the Compare process was not successfully created. |
| SPO-17668 | Resolved an issue that caused remote Capture to stall when reading online logs and disk_asynch_io was enabled on the remote database. |
| SPO-17681 | Corrected an issue which caused the following error when replicating to JMS: "No such file or directory - bridge.ini." |
| Issue ID | Description |
|---|---|
| SPO-10567 | Improved error-handling and advice for the following errors: SP-OCT01004 and SP-OCT01005. |
| SPO-10836 | Corrected an issue in which having a schema/object DDL filter causes all DDL that has no schema/object name to be filtered. |
| SPO-11221 | Oracle Poster core dumping in Breaklines |
| SPO-11443 | Post Enhanced Performance (PEP) improvement. |
| SPO-11501 | PEP (dependency checking) should skip objects that are disabled |
| SPO-13894 | A description of the copy cache command is now included in the SharePlex 9.2 Reference Guide. |
| SPO-14638 | Allow Comment on Table to pass through as non-recursive DDL |
| SPO-15088 | Corrected an issue in which Capture generated the incorrect Update operation that updates a non-NULL column with NULL value. |
| SPO-15449 | Corrected an issue in which detecting Kafka supported versions fails for SUSE Linux. |
| SPO-15452 | Corrected an issue which caused a core dump when Capture processed autoadd on a table with complex/nested UDT columns. |
| SPO-15455 | Corrected an issue that caused an error in SQL Server to SQL Server replication when the source database uses BIN or BIN2 binary collations. |
| SPO-15519 | When DDL greater than 319K is encountered, discard it and log an error instead of dumping the core. |
| SPO-15523 | Corrected an issue which caused a failure when posting the DDL for a interval-partitioned table created with an unnamed partitioned in create table statement. |
| SPO-15553 | Corrected an issue in which upgrading Oracle from 11.2 to 12.2 caused Capture to erratically drop the replicated tables. |
| SPO-15685 | Corrected an issue in which issuing a non-replicated create sequence with SP_OCT_AUTOADD_SEQ=1 and SP_OCT_REPLICATE_ALL_DDL=0 (default) caused a defunct entry in 9iDDLcache file. |
| SPO-15856 | Improved Processing of CLOBS. |
| SPO-15937 | Corrected an issue involving OCI calls being called on non-ASM RAC is setup without enabling OCI parameter. |
| SPO-15952 | Corrected an issue that caused Poster core dumping in keycache. |
| SPO-15959 | Corrected an issue in which compare SQL statement missing user-provided Oracle partition for the SP hz partition table. |
| SPO-16076 | Corrected an issue that caused an activation error upon reactivating the same configuration after a rename. |
| SPO-16114 | Certain redo-record with compressed data caused Capture to core. |
| SPO-16161 | Capture failed to parse certain redo-records generated from Oracle 12cR2. |
| SPO-16257 | When changing the SharePlex User password using the ora_chpwd utility, the "alter user" privilege is required instead of the DBA role. |
| SPO-16264 | During SharePlex installation on Windows, if the MKS installation fails, the SharePlex installation does not proceed. |
| SPO-16474 | Renaming sets of tables on peer-to-peer setting could cause ODR message to loopback causing failure in Post process. |
| SPO-16486 | Open Target logs invalid WHERE clause column_name = null in sqlerror.log |
| SPO-16700 | Removed the limitation of 8192 bytes for SQL text. The limitation caused a "SQL too large" error message during Capture. |
This chapter contains the basic system requirements for SharePlex. See also:
System Requirements for Oracle Capture
Before installing SharePlex, ensure that your system meets the minimum hardware and software requirements.
Per process memory of greater than or equal to 256 MB is required. Depending on how you configure SharePlex, there can be one or more of the following processes on a system:
Capture
Read
Export
Import
Post
For TLS connections, SharePlex supports TLS 1.2 (or later) only.
SharePlex supports IPv4 and IPv6 internet protocols. The following table shows the operating systems for which SharePlex was tested with IPv6.
Note: If the SP_SYS_HOST_NAME environment variable is set to an IPV6 address on the source system, SharePlex on the target system must be version 9.0 or later.
|
Operating System |
Source |
Target |
SharePlex Source |
On-premises/Cloud |
|---|---|---|---|---|
|
Linux RHEL |
Link-Local IPV6 |
Link-Local IPV6 |
9.0 - 9.0 |
On-premises |
|
Linux RHEL |
Link-Local IPV6 |
Link-Local IPV6 |
8.6.5 - 9.0 |
On-premises |
|
Linux RHEL |
Link-Local IPV6 |
Link-Local IPV6 |
9.0 - 8.6 |
On-premises |
|
Linux Suse |
Link-Local IPV6 |
Link-Local IPV6 |
9.0 - 9.0 |
On-premises |
|
Windows |
Link-Local IPV6 |
Link-Local IPV6 |
9.0 - 9.0 |
On-premises |
|
Windows |
Link-Local IPV6 |
Link-Local IPV6 |
9.0 - 8.6.4 |
On-premises |
|
HP UA |
Link-Local IPV6 |
Link-Local IPV6 |
9.0 - 9.0 |
On-premises |
|
HP IA |
Link-Local IPV6 |
Link-Local IPV6 |
9.0 - 9.0 |
On-premises |
|
SUN Sparc |
Link-Local IPV6 |
Link-Local IPV6 |
9.0 - 9.0 |
On-premises |
|
SUN Solaris |
Link-Local IPV6 |
Link-Local IPV6 |
9.0 - 9.0 |
On-premises |
|
AIX |
Link-Local IPV6 |
Link-Local IPV6 |
9.0 - 9.0 |
On-premises |
|
Linux RHEL |
Public IPV6 |
Public IPV6 |
9.0 - 9.0 |
Cloud |
|
Windows |
Public IPV6 |
Public IPV6 |
9.0 - 9.0 |
Cloud |
Refer to the following guidelines if the system where you are installing SharePlex is in a configuration where one or more other systems will continue to use an older version of SharePlex. An example is when installing or upgrading SharePlex on a target, but the source will continue to use SharePlex 8.6.x.
Versions with full interoperability
The following SharePlex versions are fully interoperable, including the Compare/Repair feature:
8.6.x
9.0.x
9.1.x
9.2.x
9.4.x
10.0.x
To support replication from a higher to a lower version, set the SP_SYS_TARGET_COMPATIBILITY parameter on the source system to the lower SharePlex version. If Capture is running, restart it.
Important: Downgrading from a higher to a lower version of SharePlex is not supported.
Notes:
If you upgrade the target to the current release at a future time, issue a reset for SP_OCT_TARGET_COMPATIBILITY on the source system to remove it from the SharePlex environment. Going forward, SharePlex will use the setting of the new SP_SYS_TARGET_COMPATIBILITY parameter, which defaults to the current version.
To reset SP_OCT_TARGET_COMPATIBILITY
Stop Capture.
sp_ctrl> stop capture
In sp_ctrl on the source system, issue the following command:
sp_ctrl>reset param SP_OCT_TARGET_COMPATIBILITY
Restart Capture.
sp_ctrl>start capture
© ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center
