Chat now with support
Chat with Support

SharePlex 9.0.2 - Preinstallation Checklist

Post to PaaS cloud from an intermediate system

These instructions help you set up SharePlex to replicate to a target cloud database from an intermediary server that runs the SharePlex Import and Post components.

See also:

Post to PaaS cloud from the source server

Overview of SharePlex setup on cloud databases

Source Oracle to cloud Oracle

  1. Complete the SharePlex preinstallation checklist.

  2. On the source server, install SharePlex for the source database. See:

  3. On the source server, run ora_setup to establish connection information for the source database. See Database Setup for Oracle. Important:

    1. When asked whether this is a bequeath connection, enter Y, unless this system is RAC.

    2. When asked if the current SID will be used as a source, enter Y.

  4. On the intermediary server, install the Oracle binaries. Do not create an Oracle instance.

  5. On the intermediary server, add an entry in the oratab file that points to the local Oracle home, and create a dummy entry for the ORACLE_SID. Make certain to specify N so that the startup scripts do not attempt to start the dummy instance.

    orcldb:/u01/app/oracle/product/12.1.0/dbhome_1:N

  6. On the intermediary server, add an entry in the tnsnames.ora file that points to the target cloud database.
  7. On the intermediary server, install SharePlex for the target cloud database. When prompted for the ORACLE_SID, specify the tns_alias that you created for the target cloud database. See:

  8. On the intermediary server, run ora_setup to establish connection information for the target cloud database. Run it as the master user that was created when the cloud service was created. This user has the required DBA privileges to establish connection information for the target database. Important:

    1. When asked whether this is a bequeath connection, enter N. This directs SharePlex to use TNS to connect to the target cloud database.
    2. When prompted to specify the tns_alias, specify the one that you created for the target cloud database.
    3. When asked if the current SID will be used as a source, enter N.

  9. Specify the following in the routing map of the SharePlex configuration file:

    • the name of the intermediary server as the target host.

    • the ORACLE_SID of the target cloud database.

    In the following example, intermediary1 is the intermediary server and orcldb1 is the tns_alias of the target cloud database.

    datasource:o.orcldbprim

    #source tables

    target tables

    routing map

    splex.demo_src

    splex.demo_dest

    intermediary1@o.orcldb1

Source Oracle or SQL Server to cloud Open Target

  1. Complete the SharePlex preinstallation checklist.

  2. On the source server, install SharePlex for the source database. See:

  3. On the source server, run the appropriate database setup utility for the source database. See:

    Important:

    1. (Oracle setup only) When asked whether this is a bequeath connection, enter Y to use bequeath, unless this system is RAC.
    2. Reply Y when asked if the database or SID will be used as a source.

  4. On the intermediary server, install the appropriate ODBC client of the target cloud database.
  5. On the intermediary server, install SharePlex for the target cloud database. See:

  6. On the intermediary server, run the appropriate database setup utility for the target cloud database. See Database Setup Utilities.

    Important:

    • If the target is Aurora, use the mysql_setup utility.

    • If the target is SQL Server, reply N when asked if this database will be used as a source.
    • (All targets) Specify the full target database name when prompted for the connection string.
  7. Specify the following in the routing map of the SharePlex configuration file:

    1. the name of the intermediary server as the target host.

    2. the name of the cloud database as the target database.

    In the following example using a MySQL target, intermediary3 is the intermediary system and sptest3 is the target cloud database.

    datasource:o.orcldbprim

    #source tables

    target tables

    routing map

    HR.EMP

    "sptest3"."emp"

    intermediary3@r.sptest3

For more information, see Configure SharePlex to replicate data in the SharePlex Administration Guide.

Assign SharePlex users and authorization

Contents

Overview

The SharePlex security groups provide access control to the SharePlex command and control system. Without proper configuration of these groups, anyone with permissions on the system can use the commands that view, configure, and control data replication.

Overview of SharePlex security groups

To monitor, control, or change SharePlex replication, a person must be assigned to one of the SharePlex security groups on the systems where he or she will be issuing commands. Each group corresponds to an authorization level, which determines which SharePlex commands a person can issue. To execute a command, a user must have that command’s authorization level or higher.

Use the authlevel command to determine your authorization level for issuing SharePlex commands on a system.

Description of the SharePlex security groups

Refer to the following table to determine the group and authorization level that you want to grant each SharePlex user.

User Authorization Levels and Roles
Auth level User type User group User roles
1 Administration spadmin*

You need at least one user with Administrator rights on each source and target system.

Can issue all SharePlex commands. Commands that can only be issued by a SharePlex Administrator are:

  • startup, shutdown
  • all configuration commands relating to an active configuration
  • all parameter commands except list param
  • start capture
  • stop capture
  • abort capture
  • truncate log

The SharePlex Administrator user must be in the Oracle dba group. For Oracle RAC and ASM 11gR2 and above, the user must also be in the Oracle Inventory group. For example: $ useradd –g spadmin –G dba,oinstall. The membership in Oracle Inventory group must be listed explicitly in the etc/group file.

On Unix and Linux, unless you install SharePlex as a root user, the SharePlex Administrator user and the SharePlex admin group must exist prior to installation.

2 Operator spopr Can issue all SharePlex commands except those listed above.
3 Viewer spview Can view lists, status screens, and logs to monitor replication only.

Note: The default name for the SharePlex administrator group is spadmin, but you can designate any group or specify any name for that group during installation.

Create and populate SharePlex groups on Unix and Linux

Where and when to create the SharePlex groups on Unix and Linux depends on whether you install SharePlex as a root or non-root user.

  • If you install as non-root, create the groups in the /etc/group file before you run the SharePlex installer. In a cluster, create them on all nodes.*
  • If you install SharePlex as a root user, you can direct the installer to create the groups in the /etc/group file. If you install in a cluster, the installer creates the groups on the primary node, but you must create them yourself on the other nodes.

* The groups must exist because the installer adds the SharePlex Administrator user to the spadmin group during the installation process. In a cluster, this user is only added to the primary node. You must add the SharePlex Administrator user to the other nodes.

To create the groups in /etc/group

# groupadd spadmin

# groupadd spopr

# groupadd spview

To assign a user to a group

  1. Open the /etc/group file.
  2. Add the Unix or Linux user name to the appropriate group. To assign a list of user names to a group, use a comma-separated list (see the following example).

    spadmin:*:102:spadmin,root,jim,jane,joyce,jerry

    If the password field is null, no password is associated with the group. In the example, the asterisk (*) represents the password, “102” represents the numerical group ID, and spadmin is the group. The group ID must be unique.

  3. Save the file.

Users can verify their authorization levels by issuing the authlevel command in sp_ctrl.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating