The following errors are observed when running copy for a source table that resides in an encrypted tablespace: ... 1 "OWNER"."SOURCE_TABLE" Failed - An error occurred in export: EXP-00111: Table SOURCE_TABLE resides in an Encrypted Tablespace TABLESPACE_NAME and will not be exported
Export and Import are slow, what can I do? ... If Export is backing up and replication is over a WAN, and plenty of bandwidth is available, then the following parameters need to be modified to allow SharePlex to send larger packets across the network:
Export slow - Export queue is backlogged as Export is running very slow. ... Some resource or network issues can result in slow Export. ... The issue can also be caused by slow disk I/O on the Target.
Post stops with the following error: ... <CAUSE> Post received a DDL error from the target database. ... Message:[subque/seq 5/208783008 seqno/offset 18219/5970960]. ... <ADVICE> While Post is stopped, fix the problem so that this error does not occur again.
Post process stops when it encounters the following: ... Contact Me By: Email ... "<SCHEMA>"."<SEQUENCE_NAME>" sequence does not exist on the Target database. ... Create the missing sequence on the Target database and restart Post.
When using the CHAR datatype, a difference in column size result in continuous OOS on the table when using Compare. ... A column on Source may be defined as char(1) but as char(3) on Target. ... Executing a Compare on the table will result in all rows being reported as OOS.
Post process got core dump after activation for Kafka target. ... Table or column name with more than 30 characters added to the replication and its causing post queues core dump. ... Known issue SPO-24687 : SharePlex does not replicate data when the table or column name in replication has more than 30 characters for open targets.
This is an informational message only and is not an error. ... "maximum of 100 recorded errors reached" indicates that a 100 errors in a session have been encountered in the errlog.sql file. ... A session is defined as SQL statements between commits.
Key value needs to be included in all Kafka messages produced by SharePlex. ... SharePlex will produce the key value in updates only. ... This is by design in SharePlex, on the basis that all column values are produced in Inserts and Deletes.
How to exclude Sequence replication when Sequences are explicitly defined or match a wildcard in an active configuration, Sequences that match a wildcard will be included in replication. ... This article explains how to exclude Sequences from replication.
2. Select the SharePlex version you require in the 'Choose Different Product' dropdown. ... Browse the release Notes for information on supported features and environments.
Restart Post.<br> <em>sp_ctrl> start post</em><br><br>2. ... If Post stops again with the same error then there was a communication error that requires further investigation.<br> First, check for network problems and review the SQL*Net setup.<br> Secondly, ensure the Target database is up and running.
1. Export/import target table to sync up target table structure using Oracle's Export/Import Utilties. ... 2. Manually create missing table columns via SQL statements.
This article provides a step by step guide to configuring SharePlex to replicate to an SQL Flat File Target. ... In other words, the changes occurring on the Source database in the form of SQLs are applied to a text file on the Target, and not applied to a Target database as would normally be the case with regular replication.
1. Post fails with error ORA-02149 when table partition is dropped and truncated. ... 2. Also find unusable Global indexes in database alert log when table partition is dropped and truncated. ... Table partitions are managed by Oracle so partition IDs will be different between the Source and Target databases.
The Post process is in waiting state and no transactions are applied when 'show post detail' is issued event thought the status shows that it is running: ... The file system housing the LOG_ARCHIVE_DEST directory is full.
How long do Archive Logs need to be retained on Source and Target? ... On Source, SharePlex captures transactions to be replicated by reading the online/archive redo logs. ... Once the SharePlex Export process sends these transactions to the Target, they are not required to be read again by SharePlex, and the archive logs can be removed (and sent to backup tape, etc.).
What is the purpose of the nolock option in the command “activate config”? ... The activation process will attempt to lock a table but if the table is currently locked the activation process will wait for the lock to be released.
When executing pg_setup to configure PostgreSQL for replication the following is encountered:<br><br><em>Error: [unixODBC][Driver Manager]Data source name not found and no default driver specified<br>[SP-SYS01001] Connection to PostgreSQL failed.<br><CAUSE> Either the connection information (server name, driver, port, etc) is incorrect, or invalid credentials were provided.<br><ADVICE> Please make certain that all connection information is correct.<br>See '<a href="http://advice.shareplex.com/SP-SYS01001" target="_blank">http://advice.shareplex.com/SP-SYS01001</a>' for additional advice and support.</em> Either the odbc.ini or odbcinst.ini files are not configured correctly in the /vardir/odbc directory.<br> Configure the odbc.ini and odbcinst.ini files as per the instructions in the SharePlex Installation Guide.<br><br><strong>Example: odbc.ini</strong><br><em>[testdb]<br>Driver = PostgreSQL<br>Database = testdb<br>Servername = 10.250.40.27<br>Port = 5432<br>Uid=splex<br>Pwd=splex<br>TrustServerCertificate=Yes<br>Connection Timeout=30<br>Trusted_Connection=Yes</em><br><br><strong>Example: odbcinst.ini</strong><br><em># Driver from the postgresql-odbc package<br># Setup from the unixODBC package<br>[PostgreSQL]<br>Description = ODBC for PostgreSQL<br>Driver = /usr/lib/psqlodbcw.so<br>Setup = /usr/lib/libodbcpsqlS.so<br>Driver64 = /usr/lib64/psqlodbcw.so<br>Setup64 = /usr/lib64/libodbcpsqlS.so<br>FileUsage = 1</em><br>
***************************************************************** ... Please supply a login and password for <server_name>: login: ... There are 2 potential causes that may lead to this issue, as follows:
Is PostgreSQL Flexible Database as a Source supported in SharePlex? ... Yes. This supports from SharePlex version 11.1.
DML on tables with TDE is supported with Oracle Source to all Target types.</p> Refer to the SharePlex Release Notes for further information, in relation to Conditions of Support.
The following errors are seen in the event_log when activating with Oracle 12c or higher: ... (connecting from server_name) [module osp] ... Insufficient privileges granted to the SharePlex user in the database when executing ora_setup.
ora_setup fails to connect to a remote database when using Oracle Client on local server. ... Validating user name and password. . . ... This may take a few seconds. ... Error! Unable to login using the user name and password just entered.
Use the Provision utility to change a Host name and/or IP address in the SharePlex configuration. ... The SharePlex processes rely on the Host names and/or IP addresses of the Source and Target machines to route data properly.
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center