SharePlex can post replicated Oracle data to an SAP ASE target database through an Open Database Connectivity (ODBC) interface. These instructions guide you through the configuration processes that are required to support this target.
Note: For the platforms, datatypes and operations that are supported when using SharePlex to replicate to a Sybase target, see the SharePlex Release Notes.
Configure SharePlex and the database on the source system as follows.
To replicate to an Open Target target, enable PK/UK supplemental logging in the Oracle source database. SharePlex must have the Oracle key information to build an appropriate key on the target.
To replicate to an Open Target database target, set the SP_OCT_USE_SUPP_KEYS parameter to a value of 1. This parameter directs SharePlex to use the columns set by Oracle's supplemental logging as the key columns when a row is updated or deleted. When both supplemental logging and this parameter are set, it ensures that SharePlex can always build a key and that the SharePlex key will match the Oracle key.
See the SharePlex Reference Guide for more information about this parameter.
On the source, create a SharePlex configuration file that specifies capture and routing information. The components that are required in a configuration file vary, depending on your replication strategy. However, the most important part of the configuration file as it relates to replication to an Open Target target is the portion of the routing map after the @ symbol.
Note: See Create configuration files for additional information about creating a configuration file.
To configure replication to an Open Target target, use the following syntax in the configuration file:
Datasource:o.SID | ||
src_owner.table |
tgt_owner.table |
host@r.database_name |
where:
* Important! If target owner or table name is defined in the database as anything other than UPPERCASE, be certain to:
The following configuration file replicates table HR.EMP from Oracle instance ora112 to target table Region1.Emp in database mydb on target system sysprod. The target table is case-sensitive.
Datasource:o.ora112
HR.EMP "Region1"."Emp" sysprod@r.mydb
Configure SharePlex and the database on the target system as follows.
Make certain to download the correct ODBC driver for your database.
On the target system, configure ODBC connection information for use by Post to connect to the target database. You have the following options for configuring this connection information:
On Unix and Linux, you can do either of the following:
Configure a user or system DSN on the target system according to the instructions provided with the database. Test the DSN by using it to connect to the target database. If the connection is successful, copy the ODBC configuration files to the odbc subdirectory of the SharePlex variable-data directory. Set the LD_LIBRARY_PATH environment variable to the location of the database ODBC driver.
or...
Set the ODBC connection information in the Post configuration. See Set connection information with the connection command.
Use the connection command to:
To set connection information
Execute the connection command with the set option, once for each keyword.
connection r.database_name set keyword=value
Keyword | Value to enter |
---|---|
user |
The database user assigned to SharePlex |
password |
The password for the SharePlex user |
dsn |
The DSN of the database. IMPORTANT! user, password, and dsn are the only required keywords if a DSN exists. |
Keyword | Value to enter |
---|---|
user |
The database user assigned to SharePlex |
password |
The password for the SharePlex user |
port |
The database port number. |
server |
The name or IP address of the database server. |
driver |
The full path to the ODBC driver on the database server. |
Keyword | Value to enter |
---|---|
user |
The database user assigned to SharePlex |
password |
The password for the SharePlex user |
connect_string | A user-defined connection string. When using your own connection string, make certain it includes all of the required elements to make a successful ODBC connection, but omit the user name and password. Use the connection command with the user and password options to supply user information. |
connection r.mydb set user=myuser
connection r.mydb set password=mypassword
connection r.mydb set dsn=mydsn
connection r.mydb set user=myuser
connection r.mydb set password=mypassword
connection r.mydb set port=1234
connection r.mydb set server=server1
connection r.mydb set driver=/database/ODBC/lib/databasedriver.so
connection r.mydb set user=myuser
connection r.mydb set password=mypassword
connection r.mydb set connect_string=”driver=/database/ODBC/lib/databasedriver.so;server=server1;port=1234;uid=myuser;pwd=mypassword”
Use connection with the reset option to remove SharePlex connection settings.
To remove a specific connection value
connection r.database_name reset keyword
To remove all connection values
connection r.database_name reset
connection r.mydb reset port
connection r.mydb reset
Use connection with the show option to view SharePlex connection settings.
To view connection values for a database
connection r.database_name show
To view connection settings for all local databases
connection show all
SharePlex can post replicated Oracle data to a HANA target database through an Open Database Connectivity (ODBC) interface. These instructions guide you through the configuration processes that are required to support this target.
Note: For the datatypes and operations that are supported when using SharePlex to replicate to a HANA target, see the SharePlex Release Notes.
Configure SharePlex and the database on the source system as follows.
To replicate to an Open Target target, enable PK/UK supplemental logging in the Oracle source database. SharePlex must have the Oracle key information to build an appropriate key on the target.
To replicate to an Open Target database target, set the SP_OCT_USE_SUPP_KEYS parameter to a value of 1. This parameter directs SharePlex to use the columns set by Oracle's supplemental logging as the key columns when a row is updated or deleted. When both supplemental logging and this parameter are set, it ensures that SharePlex can always build a key and that the SharePlex key will match the Oracle key.
See the SharePlex Reference Guide for more information about this parameter.
On the source, create a SharePlex configuration file that specifies capture and routing information. The components that are required in a configuration file vary, depending on your replication strategy. However, the most important part of the configuration file as it relates to replication to an Open Target target is the portion of the routing map after the @ symbol.
Note: See Create configuration files for additional information about creating a configuration file.
To configure replication to an Open Target target, use the following syntax in the configuration file:
Datasource:o.SID | ||
src_owner.table |
tgt_owner.table |
host@r.database_name |
where:
* Important! If target owner or table name is defined in the database as anything other than UPPERCASE, be certain to:
The following configuration file replicates table HR.EMP from Oracle instance ora112 to target table Region1.Emp in database mydb on target system sysprod. The target table is case-sensitive.
Datasource:o.ora112
HR.EMP "Region1"."Emp" sysprod@r.mydb
If you have not done so already, install the appropriate ODBC driver for the target HANA database.
If you did not do so when you installed SharePlex, run the
SharePlex can post replicated Oracle data to a Teradata target database through an Open Database Connectivity (ODBC) interface. These instructions guide you through the configuration processes that are required to support this target.
Note: For supported Teradata versions and drivers and the datatypes and operations that are supported when using SharePlex to replicate to a Teradata target, see the SharePlex Release Notes.
Configure SharePlex and the database on the source system as follows.
To replicate to an Open Target target, enable PK/UK supplemental logging in the Oracle source database. SharePlex must have the Oracle key information to build an appropriate key on the target.
To replicate to an Open Target database target, set the SP_OCT_USE_SUPP_KEYS parameter to a value of 1. This parameter directs SharePlex to use the columns set by Oracle's supplemental logging as the key columns when a row is updated or deleted. When both supplemental logging and this parameter are set, it ensures that SharePlex can always build a key and that the SharePlex key will match the Oracle key.
See the SharePlex Reference Guide for more information about this parameter.
On the source, create a SharePlex configuration file that specifies capture and routing information. The components that are required in a configuration file may vary, depending on your replication strategy. The following template shows the basic required components to replicate to a Teradata target.
Note: See Create configuration files for additional information about creating a configuration file.
Datasource:o.ora_SID | ||
oracle_schema.src_table |
teradata_db.targ_table |
target_host@r.teradata_db |
where:
* Important! If target owner or table name is defined in the database as anything other than UPPERCASE, be certain to:
If you did not do so when you installed SharePlex, run the
See the SharePlex Reference Guide for more information about this utility.
SharePlex can connect to a database that supports Open Database Connectivity (ODBC). For the platforms, datatypes and operations that are supported by SharePlex, see the SharePlex Release Notes.
Note: The SharePlex-supported Open Target targets are listed in the SharePlex Release Notes. Other targets may be in beta testing. For more information about the SharePlex beta program, see the SharePlex Release Notes.
Configure SharePlex and the database on the source system as follows.
To replicate to an Open Target target, enable PK/UK supplemental logging in the Oracle source database. SharePlex must have the Oracle key information to build an appropriate key on the target.
To replicate to an Open Target database target, set the SP_OCT_USE_SUPP_KEYS parameter to a value of 1. This parameter directs SharePlex to use the columns set by Oracle's supplemental logging as the key columns when a row is updated or deleted. When both supplemental logging and this parameter are set, it ensures that SharePlex can always build a key and that the SharePlex key will match the Oracle key.
See the SharePlex Reference Guide for more information about this parameter.
On the source, create a SharePlex configuration file that specifies capture and routing information. The components that are required in a configuration file vary, depending on your replication strategy. However, the most important part of the configuration file as it relates to replication to an Open Target target is the portion of the routing map after the @ symbol.
Note: See Create configuration files for additional information about creating a configuration file.
To configure replication to an Open Target target, use the following syntax in the configuration file:
Datasource:o.SID | ||
src_owner.table |
tgt_owner.table |
host@r.database_name |
where:
* Important! If target owner or table name is defined in the database as anything other than UPPERCASE, be certain to:
The following configuration file replicates table HR.EMP from Oracle instance ora112 to target table Region1.Emp in database mydb on target system sysprod. The target table is case-sensitive.
Datasource:o.ora112
HR.EMP "Region1"."Emp" sysprod@r.mydb
Configure SharePlex and the database on the target system as follows.
Make certain to download the correct ODBC driver for your database.
On the target system, configure ODBC connection information for use by Post to connect to the target database. You have the following options for configuring this connection information:
On Unix and Linux, you can do either of the following:
Configure a user or system DSN on the target system according to the instructions provided with the database. Test the DSN by using it to connect to the target database. If the connection is successful, copy the ODBC configuration files to the odbc subdirectory of the SharePlex variable-data directory. Set the LD_LIBRARY_PATH environment variable to the location of the database ODBC driver.
or...
Set the ODBC connection information in the Post configuration. See Set connection information with the connection command.
Use the connection command to:
To set connection information
Execute the connection command with the set option, once for each keyword.
connection r.database_name set keyword=value
Keyword | Value to enter |
---|---|
user |
The database user assigned to SharePlex |
password |
The password for the SharePlex user |
dsn |
The DSN of the database. IMPORTANT! user, password, and dsn are the only required keywords if a DSN exists. |
Keyword | Value to enter |
---|---|
user |
The database user assigned to SharePlex |
password |
The password for the SharePlex user |
port |
The database port number. |
server |
The name or IP address of the database server. |
driver |
The full path to the ODBC driver on the database server. |
Keyword | Value to enter |
---|---|
user |
The database user assigned to SharePlex |
password |
The password for the SharePlex user |
connect_string | A user-defined connection string. When using your own connection string, make certain it includes all of the required elements to make a successful ODBC connection, but omit the user name and password. Use the connection command with the user and password options to supply user information. |
connection r.mydb set user=myuser
connection r.mydb set password=mypassword
connection r.mydb set dsn=mydsn
connection r.mydb set user=myuser
connection r.mydb set password=mypassword
connection r.mydb set port=1234
connection r.mydb set server=server1
connection r.mydb set driver=/database/ODBC/lib/databasedriver.so
connection r.mydb set user=myuser
connection r.mydb set password=mypassword
connection r.mydb set connect_string=”driver=/database/ODBC/lib/databasedriver.so;server=server1;port=1234;uid=myuser;pwd=mypassword”
Use connection with the reset option to remove SharePlex connection settings.
To remove a specific connection value
connection r.database_name reset keyword
To remove all connection values
connection r.database_name reset
connection r.mydb reset port
connection r.mydb reset
Use connection with the show option to view SharePlex connection settings.
To view connection values for a database
connection r.database_name show
To view connection settings for all local databases
connection show all
To support the accurate posting of replicated Oracle ALTER TABLE commands to the correct datatypes in an Open Target target, you need to map Oracle datatypes to the datatypes of the target database. Use the target command with the set datatype option to perform this mapping.
Note: For DML operations, SharePlex queries the target database to determine the appropriate datatype mapping for replicated data.
To map datatypes
target r.database [queue queuename ] set datatype src_datatype=tgt_datatype
Where: src_datatype is the Oracle datatype and tgt_datatype is the target datatype to which you are mapping the Oracle datatype.
See the SharePlex Release Notes for mapping options.
For more information about the target command, see the SharePlex Reference Guide.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy