SharePlex 9.0.2 - Preinstallation Checklist

• DBA role and unlimited resource privileges, tablespace privileges, and read privileges to the redo logs.
• Default Oracle profile. By default this profile has the unlimited resource privileges originally assigned by Oracle. If the default has been changed, assign SharePlex a DBA profile with unlimited resource privileges.
• The following grants:

  • To access the data dictionary (outside the DBA roles) if O7_DICTIONARY_ACCESSIBILITY is set to FALSE:

    grant select any dictionary toSharePlexUser;

  • To replicate DDL:

    grant select any table toSharePlexUserwith admin option;

    grant create any view toSharePlexUserwith admin option;

Requirements

• Install the database client on the system where you are running Oracle Setup. Consult the Oracle documentation for the appropriate client version to use with the database.
• Run the Database Setup utility for all source and target Oracle instances in the SharePlex replication configuration.
• Within a cluster, run the Database Setup utility on all nodes of the cluster. This ensures that the SharePlex settings in the Windows Registry include the correct ORACLE_SID.
• For a consolidated replication topography, or other topology with multiple variable-data directories, run the Database Setup utility for each variable-data directory.

• SharePlex supports local BEQUEATH connections or remote connections using a TNS alias. Be prepared to supply Oracle Setup the needed connection values for whichever connection you want to use.

• If the Oracle database is a multitenant container database, run the Database Setup utility for each pluggable database involved in a replication scenario. A SharePlex user and schema objects must exist in each PDB.
• If you run the Database Setup utility when there is an active configuration, the DDL that the setup performs to install or update the SharePlex internal tables will be replicated to the target. To work around this issue, set the SP_OCT_REPLICATE_ALL_DDL parameter to 0 before running the utility, then return the parameter to its previous setting after the setup is complete. This parameter takes effect immediately.

SharePlex schema storage requirements

The Database Setup utility for Oracle installs some database objects for use by SharePlex. The storage requirements for these objects should be satisfied before running Oracle Setup. See the following table.

Required run privileges

The user who runs the Database Setup utility must have the following privileges:

Amazon RDS target

The user who runs the setup utility must be the master user that was created when the RDS instance was created. This user is granted the required DBA privileges automatically.

Non-multitenant (standard) database

The user who runs the setup utility must have DBA privileges, but if support for TDE is required, then this user must have SYSDBA privileges.

Multitenant database

The user who runs the setup utility should have SYSDBA privileges (recommended), but at minimum the user should be a DBA user with privileges for sys.users$ and sys.enc$. The minimum following grants are required for the SharePlex user:

create user c##sp_admin identified by sp_admin;

grant dba to c##sp_admin container=ALL;

grant select on sys.user$ to c##sp_admin with grant option container=ALL;

If TDE support is required for the CDB, then the following additional priviledge is required:

grant select on sys.enc$ to c##sp_admin with grant option container=ALL;

Run Database Setup for Oracle

Important! The Oracle instance must be open before this procedure is performed.

1. (Unix and Linux only) If you are using multiple variable-data directories, export the environment variable that points to the variable-data directory for the SharePlex instance for which you are running Database Setup.

   ksh shell:

   export SP_SYS_VARDIR=/full_path_of_variable-data_directory

   csh shell:

   setenv SP_SYS_VARDIR /full_path_of_variable-data_directory

2. Shut down any SharePlex processes that are running, including sp_cop.

3. Run the Database Setup program from the command prompt of the operating system, using the full path from the SharePlex bin subdirectory.

   Important! On Windows, if you installed SharePlex on any port other than the default of 2100, use the -p option to specify the port number. For example, in the following command the port number is 9400:

   C:\users\splex\bin>ora_setup -p9400

4. Specify whether the system is a source system, a target system, or both a source and target system in the SharePlex configuration.

   Note: This prompt only appears the first time that you run setup for this database.

5. For connection type, select Oracle.
6. Refer to the following table for the prompts and responses to configure SharePlex correctly for the desired connection type, either local using BEQUEATH or remote using a TNS alias.

Table 4: Setup prompts and response

Note about the tns_alias file:

When you set up SharePlex for database connection through a tns_alias and ASM connection locally through a BEQUEATH connection (through OS authentication), it is important to set up the tns_alias file correctly on each node. Assuming a SharePlex database account exists on the primary node, SharePlex will always connect to the primary ASM_SID automatically because it was provided when SharePlex was installed. However, upon failover, SharePlex must query the local v$asm_client view to get the correct ASM_SID of the failover instance. Therefore, ensure that the IP address of a given node is always listed first in the local tns_names file on that node.