delete post queue
Use the delete post queue command to remove a post queue that is left over from a deprecated replication route.
Usage
| Supported sources: |
Oracle |
| Supported targets: |
All |
| Authorization level: |
Operator (2) |
| Issues on: |
source system |
| Related commands: |
delete capture queue, delete export queue, delete export process |
Syntax
|
delete post queue queuename for datasource-datadest |
cleartrans |
[ on host |
on host:portnumber |
on login/password@host |
on login/password@host:portnumber ] |
Syntax description
| queuename |
The name of the post queue, as shown in the Queue Name field of the lstatus command output:
sp_ctrl (mysys)> lstatus on sys103 Queues:
Type # Msgs Size (Mb) Age (mn) Oldest Msg Time Newest Msg Time
------- --------- ---------- -------- ------------------ ------------------
Post 0 5 0 10-Jan-16 23:44:54 10-Jan-16 23:44:54
Queue Name: sysl03
DataSrc-DataDst: o.ora112-o.ora112
|
| for datasource-datadest |
The route specification, as shown in the DataSrc-DataDst field of the lstatus command output:
sp_ctrl (mysys)> lstatus on sys103 Queues:
Type # Msgs Size (Mb) Age (mn) Oldest Msg Time Newest Msg Time
------- --------- ---------- -------- ------------------ ------------------
Post 0 5 0 10-Jan-16 23:44:54 10-Jan-16 23:44:54
Queue Name: sysl03
DataSrc-DataDst: o.ora112-o.ora112
|
| cleartrans |
Delete the specified post queue and remove the related rows from the SHAREPLEX_TRANS table. |
Remote options
These options enable you to issue the command on a remote machine and to script commands that include a login name, password, port number, or combination of those items.
| on host |
Execute the command on a remote system (one other than the one where the current sp_ctrl session is running). You are prompted for login credentials for the remote system. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on SysA |
| on host:portnumber |
Execute the command on a remote system when a remote login and port number must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on SysA:8304 |
| on login/password@host |
Execute the command on a remote system when a remote login, password, and host name must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on john/spot5489@SysA |
| on login/password@host:portnumber |
Execute the command on a remote system when a remote login, password, host name, and port number must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on john/spot5489@SysA:8304 |
disable jobs / enable jobs
Use the disable jobs and enable jobs commands to control whether jobs that are performed by the following synchronization commands are allowed to run:
- copy and copy using
- append and append using
- compare and compare using
- repair and repair using
The disable jobs command is a safeguard that ensures that the actions performed by those jobs do not get issued in a peer-to-peer or high-availability configuration. The command prevents the primary (trusted source) data from being overwritten with un-trusted data if a copy, append, repair, or repair using command is issued on the secondary system.
Use the enable jobs command to enable jobs on the primary (trusted) system when it becomes the active system again.
Usage
| Supported sources: |
Oracle |
| Supported targets: |
Oracle |
| Authorization level: |
Operator (2) |
| Issues on: |
source system |
| Related commands: |
copy, append, compare, compare using, repair, repair using |
Syntax
| disable jobs |
for o.source_SID |
[ on host |
on host:portnumber |
on login/password@host |
on login/password@host:portnumber ] |
Syntax description
| for o.source_SID |
Use this option if there is no active configuration or if there are more than one active configurations against different Oracle source instances.
Examples:
sp_ctrl(SysA)>disable jobs for o.ora1
sp_ctrl(SysA)>enable jobs for o.ora1 |
Remote options
These options enable you to issue the command on a remote machine and to script commands that include a login name, password, port number, or combination of those items.
| on host |
Execute the command on a remote system (one other than the one where the current sp_ctrl session is running). You are prompted for login credentials for the remote system. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on SysA |
| on host:portnumber |
Execute the command on a remote system when a remote login and port number must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on SysA:8304 |
| on login/password@host |
Execute the command on a remote system when a remote login, password, and host name must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on john/spot5489@SysA |
| on login/password@host:portnumber |
Execute the command on a remote system when a remote login, password, host name, and port number must be provided. If used, must be the last component of the command syntax.
Example: sp_ctrl(sysB)>status on john/spot5489@SysA:8304 |
drop partition
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 | hash = hash_value }|
route = routing_map |
name = partition_name |
tablename = target_table |
description = description
} |
Not available |
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. This option and the hash option are mutually exclusive. |
| hash |
Hash value of the partition that you want to remove. This option and the condition option are mutually exclusive. |
| 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@o.orasid
sp_ctrl> drop partition from scheme1 where hash = 4
drop partition scheme
Use the drop partition scheme command to remove a partition scheme from the SharePlex replication configuration. This command also removes all of the row partitions that are specified for the partition scheme.
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 scheme scheme_name |
Not available |
Syntax Description
| scheme_name |
The name of the partition scheme. |
Example
sp_ctrl> drop partition scheme sales
