Post stops with SP-OPX1009 (4278449)

Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Post stops with SP-OPX1009
Description

Post stops with SP-OPX1009 when replicating from source database with non-unicode character set.
Error 2016-02-09 08:36:22.506069 30107 3997542144 Poster: [SP-OPX01009] Post cannot apply the data because the source character set is not Unicode. <CAUSE> SharePlex only supports Unicode and US7ASCII on Open Target. SharePlex is not configured to support conversion from source data that is not one of those character sets. <ADVICE> If the source data is US7ASCII, you can set the SP_OPX_NLS_CONVERSION parameter to 0, and Post will apply the data as-is. Otherwise, see <LINK> to configure the system to support conversion. See 'http://advice.shareplex.com/SP-OPX01009' for additional advice and support. (posting from ORA11GR2, queue alvsupl17, to edb) [module opx]
Error 2016-02-09 08:36:22.992206 30107 4172273504 Poster stopped: Internal error encountered; cannot continue (posting from ORA11GR2, queue alvsupl17, to edb)
Info 2016-02-09 08:36:24.000530 24447 2369865568 Poster exited with code=1, pid = 30107 (posting from ORA11GR2, queue alvsupl17, to edb)
Cause

Required Oracle client is not installed on target when replicating from Database with non-unicode character set to non-oracle target.
Resolution

SOLUTION:
In order for SharePlex to perform characterset conversion when source database is non-unicode charactersets other than US7ASCII,
Here are the requirements for target installation on Unix servers.
1. Install an Oracle Administrator client on the target system. The client must be the
Administrator installation type. The Instant Client and Runtime installation types are
not supported.
2. Set ORACLE_HOME to the client installation. Set ORACLE_SID to an alias or a nonexisting
SID. SharePlex does not use them and a database does not have to be
running.
3. Download the Oracle-based SharePlex installer, rather than the Open Target
installer, to install SharePlex on the target system. The Oracle-based installer
includes functionality that directs Post to use the conversion functions from the Oracle
client library to convert the data before posting to the target database.
4. Follow the instructions for installing SharePlex for Oracle (not the ones for installing
on Open Target).
5. Make certain the SP_OPX_NLS_CONVERSION parameter is set to the default of 1.
Here are the requirements for target installation on windows.
1. Install an Oracle Administrator client on the target system. The client must be the
Administrator installation type. The Instant Client and Runtime installation types are
not supported.
2. In the SharePlex Registry key \HKEY_LOCAL_
MACHINE\SOFTWARE\Wow6432Node\QuestSoftware\SharePlex\port_number, set
ORACLE_HOME to the Oracle client installation location, and set ORACLE_SID to an
alias or a non-existing SID. No Oracle database is required. SharePlex only needs to
use the client libraries. Shutdown and restart sp_cop service after making this change.
3. Install SharePlex using the Windows installer.
4. Make certain the SP_OPX_NLS_CONVERSION parameter is set to the default of 1.
Note: To apply Unicode and US7ASCII data without conversion
If the source data is Unicode or US7ASCII and you are not replicating LOB data, no
conversion or Oracle client is needed. Set the SP_OPX_NLS_CONVERSION parameter to 0
to disable conversion, and then restart Post if it is running.
For more information, please refer to related SharePlex Admin Guide or Installation Guide.
Additional Information

SP-OPX01009

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Request a KB Article

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

Post stops with SP-OPX1009 (4278449)

Title

Description

Cause

Resolution

Additional Information

Leave a Comment