This chapter contains instructions for configuring SharePlex to replicate from Oracle to a different type of cloud storage targets. These instructions highlight specific tasks that are pertinent to the flow of data between source and target.
SharePlex can post replicated Oracle data to a file formatted as Parquet. This data is written as a sequential series of operations as they occurred on the source, which can then be posted in sequential order to a target database or consumed by an external process or program.
These instructions contain setup instructions that are specific to this target. Install SharePlex on the source and target according to the appropriate directions in this manual before performing these setup steps.
For the versions, data types and operations that are supported when using SharePlex to replicate to this target, see the SharePlex Release Notes.
PRE-REQUISITEs:
To enable efficient processing of Parquet files by columnar query engines, the Update and Delete operations must include image data for all columns. Therefore, it is recommended to set the parameters SP_OCT_REDUCED_KEY and SP_OPX_REDUCED_KEY to 0. This ensures that SharePlex captures all data written to the Oracle redo log, excluding LONG and LOB data.
Oracle supplemental logging for all columns must be enabled to ensure that complete column data is written to the redo log.
On the source, create a SharePlex configuration file that specifies capture and routing information. The structure that is required in a configuration file varies, depending on your replication strategy, but this shows you the required syntax for routing data to a Parquet file.
| Datasource:o.SID | ||
| src_owner.table | !file[:tgt_owner.table] | host |
where:
src_owner.table is the owner and name of the source table.
Note: For more information, see Configure SharePlex to Replicate Data in the SharePlex Administration Guide.
The following example replicates the parts table in schema PROD from Oracle instance ora112 to a file on target system sysprod.
Datasource:o.ora112
PROD.parts !file sysprod
To generate data in Parquet format, use the target command as shown below.
To generate data in Parquet format:
Issue the following required target commands to output the records in Parquet.
Note: Use all lower-case characters.
target x.file [queuequeuename] set format record=Parquet
where:queuequeuename constrains the action of the command to the SharePlex Post process that is associated with the specified queue.
To refer to the configuration settings and other properties for using the Parquet record format as a target on the cloud, See the Configure Parquet record format as target section under Configure Cloud storage targets for SharePlex in the SharePlex Administration Guide.
To view current property settings for output to a file, use the following command:
target x.file show
To change a setting, use the following target command.
target x.file [queuequeuename] set [category] property=value
Post writes to a series of files. The active working file is prepended with the label of current_ and is stored in the opx/current subdirectory of the variable-data directory.
| Output Format | Name of Current File |
|---|---|
| Parquet | current_prodsys.parquet |
Important: Do not open or edit the current_ file.
Post uses the max_records, max_size and max_time parameters to determine the point at which to start a new active file. When this switch occurs, Post moves the processed data to the configured cloud storage location. The file names include the name of the post queue, the time and date, and an incrementing ID.
For Oracle to Parquet replication, a separate Parquet file will be created at the target end for each table in replication. This file will reside in a newly created directory named after it at the configured location. The file format for the consumable file will be:
<schema.table>/<seq_no>_<timestamp>_<queue_name>.parquet
Parquet files:
Microsoft_Azure_Storage -> parquetpocblobs01/parquetsamples
0000000000_20140305130858_prodsys.Parquet
0000000001_20140305131130_prodsys.Parquet
0000000002_20140305131212_prodsys.Parquet
0000000003_20140305133835_prodsys.Parquet
0000000004_20140305134028_prodsys.Parquet
To force a file switch:
The current file cannot be viewed or consumed without stopping Post. To access the data in the current file, you can use the target command with the switch option to move the data to a sequenced file, from which it can then be consumed or viewed. After issuing this command, the switch occurs after Post processes a new record.
target x.file [queuequeuename] switch
SharePlex supports databases installed as services of Amazon Web Services (AWS) and Microsoft Azure. To view the cloud databases that SharePlex supports, refer to the Supported Cloud Platforms section in the SharePlex Release Notes document for the respective databases.
There are some differences in the way that SharePlex installs in an IaaS cloud environment, a PaaS cloud environment, and a SaaS cloud environment. These differences are only in the installation and configuration of SharePlex. Once installed and configured, SharePlex operates in the cloud the same way that it operates in on-premise installations.
If your cloud database service is a true IaaS virtual computing environment, you can install and run a custom application environment, access the operating system, and manage access permissions and storage. In this environment, SharePlex is installed directly on the cloud server just as you would install it locally, without any special setup requirements.
In this environment, the following applies:
SharePlex can capture from an Oracle source database in an IaaS cloud.
SharePlex can Post to any supported target database in an IaaS cloud.
You can proceed to the standard installation instructions in this manual.
If your cloud database is installed in a true PaaS environment, you do not have access to the underlying operating system, and you must install SharePlex on a server that is external to the cloud deployment. You then configure SharePlex to interact with the target database through a remote connection.
SharePlex can capture data from supported sources and post it to databases in PaaS environment using remote capture and remote post capabilities.
You can install SharePlex for a PaaS source and target in one of the following ways:
With remote post, you can use your on-premise production source server to run all of the SharePlex replication components. In this setup, both source and target replication processes (and their queues) are installed on one server. The SharePlex Post process connects through a remote connection to the target cloud database.
For more information, see Post to PaaS cloud from the source system.
NOTE: In a high-volume transactional environment, the buildup of data in the post queues and the presence of multiple Post processes may generate unacceptable overhead for a production system. In that case, you should use an intermediary server.
You can use an on-premise intermediary server to run the Import and Post components (and the post queues). Post connects to the cloud target through a remote connection. This method removes most of the replication overhead from the source server. For more information, see Post to PaaS cloud from an intermediary server.
If your cloud database is hosted in a true SaaS environment, you do not have access to the underlying operating system, and you must install SharePlex on a server that is external to the cloud deployment. You then configure SharePlex to interact with the source and target databases through a remote connection.
You can install SharePlex for a SaaS target in one of the following ways:
With remote capture, you can utilize an on-premise or cloud VM intermediary server to install and configure SharePlex for running the Capture and Export processes. Capture establishes a remote connection to the source SaaS database, while Export communicates with Import and Post on the target system.
With remote Capture and remote Post, you can employ an on-premise or cloud VM intermediary server to install and configure SharePlex. Both Capture and Post processes will run on the same server. Capture establishes a remote connection to the source SaaS database, and Post establishes a remote connection to the target SaaS database.
Install SharePlex on Linux/Unix for PostgreSQL Database as a Service.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center
