Use the typemap command to show data type mappings. The data type map is used to map the data type of a column on the source to a corresponding data type on the target. SharePlex uses the data type map when replicating DDL and when creating tables on the target. For example, Post uses the data type map corresponding to the source-target combination to determine the data type of the target column when it replicates ALTER TABLE...ADD COLUMN DDL operations.
The data type map contains a list of rules for the source-target combination. Each rule has a pattern that Post uses to match against the source data type. If the pattern matches, the corresponding pattern is used to construct the target data type.
Example rules
| CHAR(n) |
VARCHAR(n) |
Any column defined as CHAR in DDL from the source is mapped to VARCHAR on the target with the same length (n). |
| VARCHAR(4000:) |
CLOB |
Any column defined as VARCHAR with a length greater than or equal to 4000 is mapped to a CLOB datatype on the target. |
To show data type map: Use the show option to view the current typemaps.
Usage
| Supported sources: |
Oracle |
| Supported targets: |
All |
| Authorization level: |
Operator (2) |
| Issues on: |
target system |
| Related commands: |
connection, target |
Syntax
|
typemap show |
[source-target] |
Not available |
Syntax description
|
show |
Use this option to display part or all of the current typemap information.
Examples:
typemap show displays all typemaps
typemap show oracle-sqlserver displays the Oracle to SQL Server typemap. |
|
source-target |
source-target specifies the source-target map to show. |
Use the usage command to view the syntax for a SharePlex command. You can enter the entire command or just the first few keywords. For example, type usage compare to view syntax for both the compare using and compare commands.
To view syntax plus an explanation of a command or group of commands, use the help command. There are no [on host] options for this command.
| Supported sources: |
Oracle |
| Supported targets: |
All |
| Authorization level: |
Viewer (3) |
| Issued for: |
source or target system |
| Related commands: |
help |
Syntax
| usage commandname |
Not available |
Syntax description
| commandname |
The command for which you want to view the syntax.
Example:
sp_ctrl(sysA)> usage stop |
The verify config command is intended for use as a preventive measure to avoid certain activation and replication problems. It is intended to be used to test activation to ensure that it will complete successfully.
The verify config command verifies tables and sequences only.
This command can be used to:
- Verify the syntax of the entries in the configuration file.
- Report an error if the source object is not supported for replication by SharePlex.
- Report if a host name specified in a route is unreachable.
- Report if there are duplicate specifications for a single object.
- Report if an object specification will be skipped and the reason why.
What the verify config command does not support
The verify config command does not:
- Verify activation time.
- Verify target objects or the target SID.
Verifying added or changed objects in an active configuration
To verify objects that you want to add to an active configuration or objects that you want to change (such as routing changes), it is suggested that you copy and modify the active configuration and then run the verify command against that copy.
Using with partitioned replication
You can use the verify config command for configurations containing tables that use partitioned replication. While SharePlex supports the use of verify config with partitioned replication, it does not include any additional functionality for verifying partitions or their definition.
Viewing the results of the verification
The verify config command retains control of the sp_ctrl interface until the verification is completed.
The command will read the entire config file, logging errors and duplicates, and expanding objects falling under wildcards.
The results of the verify are displayed to the screen within sp_ctrl.
If you would like to view detailed results you may:
- Issue the verify config command in sp_ctrl using the detail option
- Navigate to the results file directly using the path displayed to the screen after issuing the verify config command.
Usage
| Supported sources: |
Oracle |
| Supported targets: |
All |
| Authorization level: |
Viewer (3) |
| Issued for: |
source system |
| Related commands: |
activate config, copy config, create config, edit config |
Syntax
| verify config filename |
detail |
[ on host |
on host:portnumber |
on login/password@host |
on login/password@host:portnumber ] |
Syntax description
| filename |
filename is the name of the configuration to be verified. |
| detail |
This option will display a greater level of detail to the screen.
Example:
sp_ctrl(sysA)> verify config myconfig detail
In this example, the myconfig file will be verified and the results will be displayed with a higher level of detail. |
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 |
Use the version command to view the version number of the SharePlex software on a system.
Usage
| Supported sources: |
Oracle |
| Supported targets: |
All |
| Authorization level: |
Viewer (3) |
| Issued for: |
source or target system |
| Related commands: |
none |
Syntax
| version |
[ on host |
on host:portnumber |
on login/password@host |
on login/password@host:portnumber ] |
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 |
