Copy config for PostgreSQL
Use the copy config command to copy a configuration file and save the copy under a different file name.
Copying the configuration allows you to:
- Save a replica for backup purposes
- Use the copy as the basis for composing a new configuration using the edit config command
- Change an active configuration. You can make your changes to the copy with the edit config command while replication under the current configuration continues, and then activate the new configuration when you are ready.
This command copies the configuration to the same source system as the original configuration. To copy a configuration file to a different system, you can transfer the file via tape, CD, or FTP. To see a list of configurations on a system, use the list config command. To view the contents of a configuration, use the view config command.
Usage
| Supported sources: |
PostgreSQL |
| Supported targets: |
PostgreSQL, Oracle, SQL Server, and Kafka |
| Issues on: |
source system |
| Related commands: |
activate config, create config, list config, show config, verify config, view config |
Syntax
| copy config filename to newname |
Syntax description
| filename tonewname |
- filename is the name of the configuration that you want to copy. Configuration names are case-sensitive.
- to is a required part of the syntax.
- newname is the name you are giving to the copy. It must be unique among configurations on the system.
Example: sp_ctrl(sysA)>copy config sales to sales2 |
Create Config for PostgreSQL
Use the create config command to create a new configuration file. This command runs the SharePlex default text editor and opens a new file. To create a configuration, follow the instructions in Chapter 5 of the SharePlex Administrator’s Guide.
If you attempt to give a new configuration the same name as an existing configuration, SharePlex returns this error message “The parameter for create config must be a new filename.”
As an alternative to creating a configuration, you can use the copy config command to duplicate an existing configuration and then use the edit config command to edit the copy.
Usage
| Supported sources: |
Oracle, PostgreSQL |
| Supported targets: |
PostgreSQL, Oracle, SQL Server, and Kafka |
| Authorization level: |
Operator (2) |
| Issues on: |
source system |
| Related commands: |
activate config, copy config |
Syntax
Syntax description
| filename |
The name of the configuration that you want to create. Configuration names are case-sensitive. The name must be unique among configurations on the system.
Example:
sp_ctrl(sysA>create config sales |
Deactivate config for PostgreSQL
Use the deactivate config command to gracefully terminate replication for an active configuration. This command stops all Capture activity for the configuration, posts all data currently in the queues, and removes the associated SharePlex processes and queues.
The deactivate config command does not remove a configuration from the system, but only stops replication of its objects until you activate it again. When you deactivate a configuration, it can cause the target data to go out of synchronization if users continue making changes to the configured source objects. Deactivating one configuration on a system does not deactivate other active configurations on the same system.
Usage
| Supported sources: |
PostgreSQL |
| Supported targets: |
PostgreSQL, Oracle, SQL Server, and Kafka |
| Authorization level: |
Administrator (1) |
| Issues on: |
source system |
| Related commands: |
list config |
Syntax
| deactivate config filename |
Syntax description
| filename |
The name of the configuration that you want to deactivate. Configuration names are case-sensitive.
Example:
sp_ctrl(sysA)>deactivate config sales |
Drop Partition command for PostgreSQL
Use the drop partition command to remove a row partition from a partition scheme in a horizontally partitioned replication configuration. Issue a drop partition command for each row partition that you want to remove.
Reactivate the configuration file if the command affects a table that is already being replicated. SharePlex will only lock tables for which there are configuration changes.
For more information about how to configure horizontally partitioned replication, see the SharePlex Administration Guide.
Usage
Syntax
|
drop partition from scheme_name
where
{
{condition =column_condition
route = routing_map |
name = partition_name |
tablename = target_table |
description = description
} |
Syntax Description
| scheme_name |
The name of the partition scheme. |
| condition |
Column condition that defines the rows of the partition that you want to remove. |
| route |
The routing map of the partition that you want to remove. |
| tablename |
The fully qualified name of the target table in the partition that you want to remove. |
| name |
The short name of the partition that you want to remove. |
| description |
The description of the partition that you want to remove. |
Examples
sp_ctrl> drop partition from scheme1 where name = q1
sp_ctrl> drop partition from scheme1 where condition = "C1 < 200"
sp_ctrl> drop partition from scheme1 where route = sysb:q2@r.dbname
