Show TOC

configure replication serverLocate this document in the navigation structure

Sets characteristics of the SAP Replication Server, including network-based security, and configures the ERSSD.

Syntax
configure replication server {
	set <repserver_param> to '<value>' |
	set <route_param> to '<value>' |
	set <database_param> to '<value>' |
	set <logical_database_param> to '<value>' |    
    set <password_param> to '<value>' |
 <maintenance_user_password_param> to '<value>' |
	set <security_param> to '<value>' |
	set <id_security_param> to '<value>' |
	set <security_services> [to] 'default'} |      
    set <user_authentication_source> to '<value>' |
    set <parameter> to 'parameter_value' | 
    set ddl_datatype_map from {ORA|MSSQL|UDB}.{<pdatatype> | <pdatatype(n)> | <pdatatype(precision,scale)> | } to {HDB}.{NULL | <rdatatype> | <rdatatype>[multi]| <rdatatype(n)> | <rdatatype(precision,scale)>        
    set dsi_ddl_create_column_table to {'on' | 'off'}
    set num_concurrent_subs to <num_subs> [nowait]
Parameters
repserver_param

Parameter that affects the Replication Server. See Replication Server configuration parameters and ERSSD configuration parameters .

value

A setting for a configuration parameter.

Table 1: Replication Server Configuration Parameters

repserver_param

Value

audit_enable

Set audit_enable on to enable command auditing. Default is off.

audit_dest

Specifies the file name and path for the command auditing log if you enable command auditing.

Default is log.

In Unix, Replication Server creates the log file with 0600 permissions if the file does not exist. If you create your own log file in UNIX with different permissions such as 0666, Replication Server retains your permissions.

block_size to '<value>' with shutdown

Specifies the queue block size which is the number of bytes in a contiguous block of memory used by stable queue structures.

Range of values allowed: 16KB, 32KB, 64KB, 128KB, or 256KB

Default: 16KB

Note

When you execute the command to change the block size, Replication Server shuts down. You must include the “with shutdown” clause after specifying the block size in versions prior to Replication Server 15.6. In version 15.6 and later the “with shutdown” clause is optional; you need not restart Replication Server for the change in queue block size to take effect. You should change this parameter only with the configure replication server command. Doing otherwise corrupts the queues.

License: Separately licensed under the Advanced Services Option.

See Replication Server Administration Guide Volume 2 > Performance Tuning > Replication Server – Advanced Services Option for instructions.

.block_sub_for_repdef_in_pub

Specifies whether to block or allow subscriptions to the replication definition used in an article and a publication.

Valid values are: off and on

Default: off

Enable this parameter at the primary Replication Server; the server does not require a restart.

cm_fadeout_time

The number of seconds of idle time before Replication Server closes a connection with the RSSD. A value of –1 specifies that a connection will never be closed.

Default: 300 seconds

Minimum: 1 second

Maximum: 2,147,483,648 seconds

cm_max_connections

The maximum number of outgoing connections available to the connection manager. The value must be greater than 0.

Default: 64

current_rssd_version

The Replication Server version supported by this RSSD. The Replication Server checks this value at startup.

Note

Do not change the value for this parameter. This value should only be modified by the rs_init program when you upgrade or downgrade.

Default: N/A

create_repdef_without_lock

Set this to on to allow SAP Replication Server to create table replication definitions for different tables in parallel. This decreases the time taken to create table replication definitions. Valid values are:
  • on
  • off (default)
Note If you want to create multiple replication definitions for a specific table, you must set create_repdef_without_lock to off.

create_repdef_without_func

Set this to on to allow SAP Replication Server to create a table replication definition without creating the corresponding table level function and function strings. This decreases the time taken to create a table replication definition. Valid values are:
  • on (default)
  • off
Note If create_repdef_without_func is on and you want to customize a function string for a table replication definition, use the create function string command.

deferred_queue_size

The maximum size of an Open Server deferred queue. If Open Server limits are exceeded, increase the maximum size. The value of deferred_queue_size must be greater than 0.

Note

You must restart the Replication Server for any changes to this parameter to take effect.

Default: 2048 on Linux and HPIA32;               1024 on other platforms

dist_direct_cache_read

Enables the distributor (DIST) thread to read SQL statements directly from the Stable Queue Thread (SQT) cache. This reduces the workload from SQT and the dependency between the two, and improves the efficiency of both SQT and DIST

Default: off

License: Separately licensed under the Advanced Services Option. See Replication Server Administration Guide Volume 2 > Performance Tuning > Advanced Services Option.

ha_failover

Enables or disables SAP Failover support for new database connections from the Replication Server to Adaptive Servers. Values are:
  • on - Failover is enabled

  • off - Failover is disabled

Default: off

id_server

The name of the ID Server for this Replication Server.

Note

Do not change the value of this parameter. id_server is set when you run rs_init and should only be modified by the rs_init program when you upgrade or downgrade Replication Server.

Default: N/A

init_sqm_write_delay

Write delay for the Stable Queue Manager if queue is being read.

Default: 100 milliseconds

init_sqm_write_max_delay

The maximum write delay for the Stable Queue Manager if the queue is not being read.

Default: 1000 milliseconds

mat_load_tran_size

Specifies the optimal transaction or batch size for initial load during direct load materialization.

Valid values: 10 – 2147483646

Default: 10000

max_mat_load_threads

Specifies the maximum number of load threads for each table being materialized.

Valid values: 1 – 80

Default: 5

Replication Server begins direct load materialization with one load thread for each table and spawns more threads as necessary up to the number specified by this parameter.

max_mat_load_threads is a local SAP Replication Server and database connection parameter.

The value of this parameter and num_concurrent_subs control resource use for direct load materialization. When a subscription is created with num_of_select selects, and num_of_select is more than 1, the apply threads are divided equally among the select threads. The maximum number of apply threads for each select thread is 20.

mem_reduce_malloc

Enable to allocate memory in larger chunks, which reduces the number of memory allocations and leads to improved Replication Server performance.

Default: off

License: Separately licensed under the Advanced Services Option. See Replication Server Administration Guide Volume 2 > Performance Tuning > Replication Server – Advanced Services Option.

mem_thr_dsi

Specifies the percentage of the total memory used to force the DSI thread to stop populating the SQT cache.

Default: 80% of memory_limit value.

Range: 1 – 100

mem_thr_exec

Specifies the percentage of the total memory used to force the EXEC thread to stop receiving commands from RepAgent.

Default: 90% of memory_limit value.

Range: 1 – 100

mem_thr_sqt

Specifies the percentage of the total memory used to force the SQT thread to flush the largest transaction from its cache if possible.

Default: 85% of memory_limit value.

Range: 1 – 100

mem_warning_thr1

Specifies the threshold percentage of the total memory used before the first warning message is generated. See memory_limit.

Default: 80% of memory_limit value.

Range: 1 – 100

mem_warning_thr2

Specifies the threshold percentage of the total memory used before the second warning message is generated. See memory_limit.

Default: 90% of memory_limit value.

Range: 1 – 100

memory_control

Manages the memory control behavior of threads that require significant amount of memory. See memory_limit.

Values are:
  • on – enables memory control
  • off – disables memory control

Default: on

memory_limit

The maximum total memory the Replication Server can use, in megabytes.

Values for several other configuration parameters are directly related to the amount of memory available from the memory pool indicated by memory_limit. These include md_sqm_write_request_limit, queue_dump_buffer_size, sqt_max_cache_size, sre_reserve, and sts_cachesize.

Default: 2,047MB

For 32-bit Replication Server:
  • Minimum – 0

  • Maximum – 2,047MB

For 64-bit Replication Server:
  • Minimum – 0

  • Maximum – 2,147,483,647

When memory_control is:
  • on – Replication Server does not shut down when memory consumption exceeds memory_limit
  • off – Replication Server automatically shuts down when memory consumption exceeds memory_limit
Monitor memory usage and increase memory_limit if required.

Replication Server shuts down when it exceeds the defined value of available memory in memory_limit. Monitor memory usage and increase memory_limit if required.

In Replication Server, the threads that require significant amount of memory are:
  • DSI
  • EXEC
  • SQT
These threads execute memory control by performing a memory usage check before receiving or processing new data. During memory control, if the memory usage is found to be high, thread functioning is adjusted by:
  • Stopping the thread from grouping new data, and cleaning and processing existing data; or,
  • Making the thread go into a sleep mode such that it does not receive new data until memory is available.

If the value you set is larger than 2,047MB, downgrading resets the value to 2,047MB to protect against overflow.

minimum_rssd_version

The minimum version of the Replication Server that can use this RSSD. When the current_rssd_version is greater than the version of the Replication Server, this value is checked when the Replication Server is started.

Note

Do not change the value for this parameter. This value should only be modified by the rs_init program when you upgrade or downgrade.

Default: N/A

nrm_thread

Enables the NRM thread which Replication Server can use to normalize and pack Log Transfer Language (LTL) commands in parallel with parsing by the RepAgent Executor thread. Parallel processing by the NRM thread reduces the response time of the RepAgent executor thread. The NRM thread is a thread split from RepAgent executor thread.

Use the configure replication server command to set nrm_thread to on before you use exec_nrm_request_limit.

Default: off

License: Separately licensed under the Advanced Services Option. See Replication Server Administration Guide Volume 2 > Performance Tuning > Replication Server – Advanced Services Option.

num_client_connections

The maximum number of incoming client connections allowed. If Open Server limits are exceeded, increase the maximum number. The value must be greater than or equal to 30.

Default: 30

num_concurrent_subs

The maximum number of concurrent subscription materialization/dematerialization requests allowed. (Limit applies to atomic and non-atomic materialization only; does not apply to bulk materialization.) Requests over the maximum are fulfilled after other requests have been fulfilled. The minimum value is 1.

Default: 10

num_msg_queues

The maximum number of Open Server message queues allowed. If Open Server limits are exceeded, increase the maximum number. The value must be greater than the num_threads setting.

Default: 300

num_msgs

The maximum number of Open Server message queue messages allowed. If Open Server limits are exceeded, increase the maximum number.

Default: 91,136

num_mutexes

The maximum number of Open Server mutexes allowed. If Open Server limits are exceeded, increase the maximum number. The value must be greater than the num_threads setting.

Default: 1024

num_stable_queues

The maximum number of stable queues allowed (HP9000 only). Each stable queue uses 32,768 bytes of shared memory. The minimum number of stable queues allowed is 32.

Each standby database connection uses an additional 16,384 bytes of shared memory. Every two standby database connections count as one additional stable queue.

Default: 32

num_threads

The maximum number of Open Server threads allowed. If Open Server limits are exceeded, increase the maximum number. The value must be greater than or equal to 20.

Default: 150

oserver

The name of the current Replication Server.

Note

Do not change the value for this parameter. You specified the current Replication Server name when you installed it using rs_init.

Default: N/A

password_encryption

This parameter has been deprecated. Use the create user or alter user commands to implement password security. Use configure replication server to set password parameters at the server level for all Replication Server users.

prev_min_rssd_version

Following an rs_init installation upgrade, this value contains the previous value of minimum_rssd_version.

Note

Do not change the value for this parameter. This value should be modified only by rs_init when you upgrade or downgrade.

Default: N/A

prev_rssd_version

Following an rs_init installation upgrade, this value contains the previous value of current_rssd_version.

Note

Do not change the value for this parameter. This value should be modified only by rs_init when you upgrade or downgrade.

Default: N/A

queue_dump_buffer_size

The maximum command length, in bytes, used by the sysadmin dump_queue command. Commands larger than the specified length are truncated. The range is 1000 to 32,768.

Default: 32,768 bytes

quotes_in_identifiers

Determines Replication Server behavior when quotes are used in the table or column identifiers sent by a RepAgent.

Valid values are:
  • block – searches for quotes in the table names and column names when a command is executed.
  • ignore – ignores the quotes in the table names and column names when a command is executed.

Default: block

When quotes_in_identifiers is block, and a command with quotes in identifiers is sent by a RepAgent, an error message is written to the Replication Server log file, and the RepAgent is suspended.

This parameter takes effect immediately and does not require a restart.

rec_daemon_sleep_time

Specifies the sleep time for the recovery daemon, which handles “strict” save interval messages in warm standby applications and certain other operations.

Default: 2 minutes

rssd_error_class

Error class for the RSSD.

Default: rs_sqlserver_error_class

send_enc_password

Ensures that all Replication Server client connections are made with encrypted passwords—except for the first connection to the RSSD. Values are “on” and “off.”

See the Replication Server Administration Guide Volume 1 for more information.

Default: off

send_timestamp_to_standby

Specifies whether to send timestamp columns to the replicate database when there is no replication definition. Values are on and off.

See the Replication Server Administration Guide Volume 1 for more information.

Default: off

smp_enable

Enables symmetric multiprocessing (SMP). Specifies whether Replication Server threads should be scheduled internally by Replication Server or externally by the operating system. When Replication Server threads are scheduled internally, Replication Server is restricted to one machine processor, regardless of how many may be available. Values are “on” and “off.”

Default: on

sqm_async_seg_delete

Set sqm_async_seg_delete to on to enable a dedicated daemon for deleting segments and improve performance for inbound and outbound queue processing.

Default: on

You must restart Replication Server for any change to the parameter setting to take effect.

If sqm_async_seg_delete is on, Replication Server may require a larger partition. Use alter partition to expand a partition. See:
  • Replication Server Configuration Guide > Preparation for Installing and Configuring Replication Server > Plan the Replication System > Initial Disk Partition for Each Replication Server.
  • Replication Server Administration Guide Volume 1 > Replication Server Technical Overview > Transaction Handling with Replication Server > Stable Queues > Partitions for Stable Queues.

sqm_cache_enable

Sets server-wide stable queue caching. Values are on and off.

Default: on

sqm_cache_size

Sets server-wide stable queue cache size by specifying the number of pages in cache where the size of a page is specified by sqm_page_size.

Enclose the number of pages in single quotes or double quotes.

Range is 1 to 4096.

Default: 16

sqm_page_size

Sets the server-wide stable queue page size by specifying the number of 16KB blocks in a page.

Configuring the page size also sets the I/O size of SAP Replication Server. For example, setting page size to 4 instructs SAP Replication Server to write to the stable queue in 64K blocks.

Configuring the page size also sets the I/O size of SAP Replication Server.

Enclose page sizes in single quotes or double quotes.

The range is 1 to 64.

Default: 4

sqm_reader_first

Set sqm_reader_first on at the server level for all queues to ensure the stable queue manager (SQM) reader always reads all commands from the SQM cache.

Default: off

You must enable the SQM cache with sqm_cache_enable before you set sqm_reader_first to on.

You can also use alter queue to set sqm_reader_first on at the queue level for either the inbound or outbound queue. Setting sqm_reader_first at the queue level overrides any server-level setting that you set using configure replication server.

See Ensuring SQM Reader Reads All Commands in Cache in the Administration Guide Volume 2 to configure sqm_reader_first.

sqm_recover_segs

Specifies the number of stable queue segments Replication Server allocates before updating the RSSD with recovery QID information.

See Specify the Number of Stable Queue Segments Allocated in the Administration Guide Volume 2.

SAP recommends that you increase the value of sqm_recover_segs to improve performance.

Default: 1

Minimum: 1

Maximum: 2,147,483,648

sqm_warning_thr1

Percent of partition segments (stable queue space) to generate a first warning. The range is 1 to 100.

Default: 75

sqm_warning_thr2

Percent of partition segments used to generate a second warning. The range is 1 to 100.

Default: 90

sqm_warning_thr_ind

Percent of total partition space that a single stable queue uses to generate a warning. The range is 51 to 100.

Default: 70

sqm_write_flush

Specifies whether data written to memory buffers is flushed to the disk before the write operation completes. Values are:
  • on – data written to the memory buffer is flushed to the disk.

  • off – data written to the memory buffer is not flushed to the disk.

  • dio – enables direct I/O and allows Replication Server to read and write to the disk without file system buffering. Available only in Solaris (SPARC) and Linux.

Default: on

sqt_init_read_delay

The length of time an SQT thread sleeps while waiting for an SQM read before checking to see if it has been given new instructions in its command queue. With each expiration, if the command queue is empty, SQT doubles its sleep time up to the value set for sqt_max_read_delay.

Default: 1 ms

Minimum: 0 ms

Maximum: 86,400,000 ms (24 hours)

sqt_max_cache_size

Use sqt_max_cache_size for sizing the SQT cache to the maximum SQT cache memory, in bytes.

For 32-bit Replication Server:
  • Default – 1,048,576

  • Minimum – 0

  • Maximum – 2,147,483,647

For 64-bit Replication Server:
  • Default – 20,971,520

  • Minimum – 0

  • Maximum – 2,251,799,813,685,247

If the value you set is larger than 2,147,483,647 bytes, downgrading resets the value to 2,147,483,647 bytes to protect against overflow.

sqt_max_read_delay

The maximum length of time an SQT thread sleeps while waiting for an SQM read before checking to see if it has been given new instructions in its command queue.

Default: 1 ms

Minimum: 0 ms

Maximum: 86,400,000 ms (24 hours)

sre_reserve

The amount of additional space to allocate for new subscriptions. For example, 100 (100%) means double the current space. The range is 0 to 500.

To update the sre_reserve parameter for a replication definition, insert into or update the <rs_config> system table directly.

Default: 0

stats_reset_rssd

Indicates whether RSSD truncates previous sampling data or overwrites it with new information.

Values: on – overwrite old sampling data with new information.

off – keep previous sampling data.

Default: on

stats_sampling

Enables sampling counters.

Default: off

stats_show_zero_counters

Specifies whether the admin stats command reports counters with zero observations for a specified sample period.

The values are:
  • on – counters with zero observations are reported.

  • off – counters with zero observations are not reported.

Default: off

sts_cachesize

The total number of rows cached for each cached RSSD system table. Increasing this number to the number of active replication definitions prevents Replication Server from executing expensive table lookups.

Default: 1000

sts_full_cache_<RSSD_system_table_name>

Specifies an RSSD system table that is to be fully cached. Fully cached tables do not require access to the RSSD for simple select statements.

Enter sts_full_cache_, leave no space, and follow with the table name.

Tables with sts_full_cache set to on by default and that Replication Server fully caches:
  • rs_clsfunctions
  • rs_repobjs
  • rs_users

See Replication Server Administration Guide Volume 2 > Performance Tuning > Suggestions for Using Tuning Parameters > Cache System Tables > System Tables that Can Be Cached for a list of all RSSD tables that can be fully cached.

sub_daemon_sleep_time

Number of seconds the subscription daemon sleeps before waking up to recover subscriptions. The range is 1 to 31,536,000.

Default: 120 seconds

unicode_format

Supports sending unicode data in U&” format which removes the limitation of UTF-8 character set in Replication Server.

Set unicode_format to one of these values:
  • string – unicode characters are converted to character string format. For example, the string “hello” is sent out as “hello”. In this case Replication Server requires UTF-8.
  • ase – unicode characters are sent out in U&’’ format. For example, the string “hello” is sent out as “U&'\0068\0065\006c\006c\006f’ ”. The two-byte unicode value is sent in network order as required by Adaptive Server Enterprise. In this case Replication Server can use a character set other than UTF-8.

Default: string

varbinary_strip_trailing_zeros

Set varbinary_strip_trailing_zeros to on to strip trailing zeros from varbinary values. If you set to off, Replication Server replicates the trailing zeros in varbinary values.

You need not restart Replication Server, or suspend and resume connections for any change in the parameter to take effect.

Default: on

varchar_truncation

Enables truncation of <varchar> columns at the primary or replicate Replication Server. Set varchar_truncation at the replicate Replication Server when a character set conversion takes place at both Replication Servers.

Default: off

worker_thread_num

Specifies the number of worker threads available to the global task manager which can then assign the threads to process tasks scheduled by SAP Replication Server modules.

Default: 4

Minimum: 2

Maximum: 32

See Controlling the Number of Worker Threads in the Administration Guide Volume 2.

Tune the value of worker_thread_num only when you enable parameters that use worker threads such as when you enable distributed application of transactions in DSI or parallel processing in DIST. In the Administration Guide Volume 2, see:
  • Parallel Processing in DIST
  • Distributed Application of Transactions in the DSI Thread
route_param

Affects routes. See Configuration parameters affecting routes for a list and description of route parameters. configure replication server sets parameter values for all routes that originate at the source Replication Server.

database_param

Affects connections. See Parameters affecting database connections for a list and description of connection parameters. configure replication server sets parameter values for all connections that originate at the source Replication Server.

logical_database_param

Affects logical connections. See Configuration parameters affecting routes for a list and description of parameters. configure replication server sets parameter values for all logical connections that originate at the source Replication Server

password_param
Affects password security parameters. See Password Parameters for a list and description of parameters.
Table 2: Password Parameters
<password_parameter> Description and <value>
min_password_len

Minimum number of characters required.

  • 0 – no minimum length.
  • Range – 6 to 16 (default 6).
max_password_len

Maximum number of characters. Always set max_password_len to a value greater than min_password_len.

Range – 13 to 30 (default 30).

password_lowercase_required

Whether lowercase characters are required.

  • True – required.
  • False – not required (default).
password_uppercase_required

Whether uppercase characters are required.

  • True – required.
  • False – not required (default).
password_numeric_required

Whether a numeric character is required.

  • True – required.
  • False – not required (default).
password_special_required

Whether a special character is required.

  • True – required.
  • False - not required (default).
simple_passwords_allowed

If you set this option (or "simple_passwords_allowed") to false, Replication Server does not allow the password to contain the user name or any values from a user password dictionary.

  • True – allowed (default).
  • False – not allowed.
You can create the password dictionary in the RSSD in the rs_dictionary system table. The table does not store default values. You must create your own scripts to insert values into the table. For example:
insert into rs_dictionary (words) values (“abcd”);
 insert into rs_dictionary (words) values (“1234”);
disallowed_prev_passwords

Number of previous passwords that cannot be reused when the user changes his or her password.

  • 0 – previous passwords allowed.
  • Range – 0 to 32,767 (default 0).

The parameter value does not apply to a user password when the administrator is resetting the password.

password_expiration

Number of days after which the password expires.

  • 0 – password never expires (default).
  • Range – 0 to 32,767.

You can use password_expiration with alter user and create user.

If the password has expired, Replication Server locks the account and notifies the user that the password has expired. If the user does not reset his password, he or she cannot log in once disconnected until the administrator resets the password. The new password must meet all the password requirements.

Passwords do not expire for any user that rs_init creates with connect source permission or the ID user. These passwords override any setting for password_expiration that you set for all users in the Replication Server. Databases, other Replication Servers, and Replication Agents use user IDs with connect source permission.

Administrators set the password to not expire for any user that is created for Replication Agent or an RSI.

initial_password_expiration

Number of days after which the initial password expires.

  • 0 – initial password never expires.
  • Range – 0 to 32,767 (default 0).

An initial password for a user is the password set by the administrator when creating the user or when resetting the user password.

max_failed_logins

Maximum number of failed login attempts Replication Server allows before locking the account.

  • 0 – account never locked.
  • Range – 0 to 32,767 (default 0).

Replication Server locks the account according to the time interval set in password_lock_interval.

password_lock_interval

Number of minutes that an account remains locked if the user reaches the maximum number of login attempts set in max_failed_logins.

  • 0 – account remains locked until administrator resets password.
  • Range – 0 to 32,767 (default 0).
unused_login_expiration

Number of days after which an unused user account expires.

  • 0 – unused account never expires.
  • Range – 0 to 32,767 (default).

Replication Server locks an account that remains unused for longer than unused_login_expiration. The administrator can reactivate the account by resetting the password.

<maintenance_user_password_param>

Affects maintenance user password security. See Table : 3

Table 3: Parameters Affecting Maintenance User Security

<maintenance_user_password_param>

<Value>

hide_maintuser_pwd

Configures password protection for the maintenance user and restricts maintenance user access to Replication Server.

Set hide_maintuser_pwd on to:
  • Periodically generate a new password for the maintenance user for existing connections to a replicate Adaptive Server database.
  • Alter and subsequently periodically regenerate the password at the replicate Adaptive Server database for any new database connections you create.
  • Change and encrypt any password you reenter for the maintenance user.

Default – off.

maintuser_pwd_expiration

Sets the password expiration interval for the maintenance user. Replication Server automatically changes the password when the password expires. You must enable maintenance user password protection by setting hide_maintuser_pwd on before you set a nonzero value for maintuser_pwd_expiration.

Range – 0 to 32,767 days

Default – the default password expiration interval for the maintenance user is the value set in the Replication Server password_expiration option. The default for password_expiration is 0 days which means the password does not expire.

security_param

Affects network-based security. See Parameters affecting network-based security.

Table 4: Parameters Affecting Network-Based Security

<security_param>

<Value>

msg_confidentiality

Indicates whether Replication Server sends and receives encrypted data. If set to “required,” outgoing data is encrypted. If set to “not required,” Replication Server accepts incoming data that is encrypted or not encrypted.

Default: not_required

msg_integrity

Indicates whether data is checked for tampering.

Default: not_required

msg_origin_check

Indicates whether the source of data should be verified.

Default: not_required

msg_replay_detection

Indicates whether data should be checked to make sure it has not been intercepted and resent.

Default: not_required

msg_sequence_check

Indicates whether data should be checked to make sure it was received in the order sent.

Default: not_required

mutual_auth

Indicates whether the remote server must provide proof of identify before a connection is established.

Default: not_required

security_mechanism

The name of the third-party security mechanism enabled for the pathway.

Default: first mechanism listed in the SECURITY section of libtcl.cfg

Note This parameter does not apply to non-ASE and non-IQ connectors like ExpressConnect for SAP HANA DB. For information about these connectors, see the Replication Server Heterogeneous Guide.

send_enc_password

Ensures that all Replication Server client connections are made with encrypted passwords—except for the first connection to the RSSD. Values are “on” and “off.”

Default: off

unified_login

Indicates how Replication Server seeks to log in to remote data servers and accepts incoming logins.

The values are:
  • “required” – always seeks to log in to remote server with a credential.

  • “not_required” – always seeks to log in to remote server with a password.

Default: not_required

use_security_services

Tells Replication Server whether to use security services. If use_security_services is “off,” no security features take effect.

Note

This parameter can only be set by configure replication server. This parameter does not apply to non-ASE and non-IQ connectors like ExpressConnect for SAP HANA DB. For information about these connectors, see the Replication Server Heterogeneous Guide.

use_ssl

Indicates whether Replication Server is enabled for session-based SSL security.

The values are:
  • “on” – Replication Server is enabled for SSL.

  • “off” – Replication Server is not enabled for SSL.

Default: off

id_security_param

Affects network-based security for the ID Server. See Security parameters for connecting to the ID Server for a list and description of these parameters.

Table 5: Security Parameters for Connecting to the ID Server

<security_param>

<Value>

id_msg_confidentiality

Indicates whether Replication Server sends and receives encrypted data packets. If set to “required,” outgoing data is encrypted. If set to “not required,” Replication Server accepts incoming data that is encrypted or not encrypted.

Default: not required

id_msg_integrity

Indicates whether data packets are checked for tampering.

Default: not required

id_msg_origin_check

Indicates whether the source of data packets should be verified.

Default: not required

id_msg_replay_detection

Indicates whether data packets should be checked to make sure they have not been intercepted and resent.

Default: not required

id_ msg_sequence_check

Indicates whether data packets should be checked to make sure they are received in the order sent.

Default: not required

id_mutual_auth

Requires the ID Server to provide proof of identify before Replication Server establishes a connection.

Default: not required

id_security_mech

Specifies the name of the supported security mechanism.

Supported security mechanisms are listed under SECURITY in the libtcl.cfg file. If no name is specified, Replication Server uses the default mechanism.

Default: the first mechanism in the list

id_unified_login

Indicates how Replication Server seeks to connect to ID Server. The values are:
  • required – always seeks to log in to ID Server with a credential.

  • not required – always seeks to log in to ID Server with a password.

Note

Only the “sa” user can log in to Replication Server without a credential if unified_login is “required.” If the security mechanism should fail, the “sa” user can log in and disable unified_login.

Default: not required

set security_services [to] 'default'

Resets all network-based security features for the connection to match the global settings of your Replication Server. It does not reset the use_security_services feature.

If Replication Server supports more than one security mechanism, set security_services [to] 'default' also sets the security mechanism to the default, the first mechanism listed in the SECURITY section of the libtcl.cfg file.

user_authentication_source

Configures the user authentication mechanism.

Table 6: User Authentication Parameters
Parameter Description

rs

Disables LDAP user authentication and uses rs_users table user credentials to authenticate a login request.

any

Indicates Replication Server uses the LDAP server user credentials to authenticate a login request.

If the user account does not exist in the LDAP server or the LDAP server is down, Replication Server uses the rs_users user credentials to authenticate a login request.

This option is used when you are migrating from the rs_users system table authentication to an LDAP authentication.

ldap

Indicates Replication Server uses only the LDAP server to authenticate an user account. The user must exist in the LDAP server.

This option allows the LDAP server to prevent existing users from being authenticated by Replication Server when they do not have valid LDAP user accounts.

Note If Kerberos authentication is enabled in addition to the LDAP user authentication, Replication Server uses Kerberos to authenticate login requests.
ddl_datatype_map

Define mapping for the datatypes in the DDL commands at the replicate Replication Server when replicating and initializing replicate tables during materialization.

pdatatype(n)
Datatype and length of the primary datatype. When the n parameter is a negative number, the datatype with all lengths in the primary database are mapped with the same replicate datatype as indicated in the command.
pdatatype(precision,scale)
Datatype, precision and scale of the primary datatype. When the values of the precision and scale parameters are negative numbers, the datatype with all precisions and scales in the primary database are mapped with the same replicate datatype as indicated in the command. Both precision and scale must have either the same negative value or the same positive value. When you specify a primary datatype that can have precision and scale, you have to specify both precision and scale. For example: NUMBER(1) is not valid.
NULL
Configures the mapping to the default replicate datatype for this particular primary datatype.
multi
When the multi parameter is specified, the length of the replicate datatype equals the primary datatype length multiplied by the multi parameter. When the multi parameter is omitted, the primary datatype and replicate datatype have the same length.
Note
  • The multi parameter works only for datatype length, not for precision and scale.

  • The multi parameter can only be a positive integer.

dsi_ddl_create_column_table
When you set the parameter to on, Replication Server issues the create column table command when sending the create table commands to the replicate database or initializing replicate tables during materialization. The tables are stored in columns into the SAP HANA database.
num_concurrent_subs
Configures the number of the subscriptions that can be processed concurrently.
num_subs
The maximum number of concurrent subscriptions that can be processed. If this number is altered to a bigger number, and if there are pending subscriptions, the subscription daemon starts a few more subscriptions.
nowait
If a database subscription is created with materialization, create, recreate, truncate, or create_or_truncate operations, the newest table-level subscriptions being processed which are not materialized for the database subscription are stopped. If a subscription is already materialized but not yet valid, it is not dropped.
Examples
Example 1

Sets Replication Server to send data in encrypted format:

configure replication server 
 set id_msg_confidentiality to 'required'
Example 2

Sets all security features to match the global settings:

configure replication server 
 set security_services to 'default'
Example 3

Changes the rsi_save_interval parameter to two minutes for all routes originating at the current Replication Server:

suspend route to <each_dest_replication_server
>
 configure replication server
 set rsi_save_interval to '2'
 
 resume route to <each_dest_replication_server>
Example 4

Sets the queue block size to 64.

configure replication server 
set block_size to ‘64’

(Optional) Uses the with shutdown clause to set the block size and shut down the primary Replication Server

configure replication server 
set block_size to ‘64’ with shutdown
Example 5

Enforces the minimum password length as 8 characters for all users:

configure replication server
set min_password_len to '8'
Example 6

Enforces the password expiration interval as 90 days for all users:

configure replication server
set password_expiration to '90'
Example 7
Configures Replication Server to use the LDAP user authentication:
configure replication server
set user_authentication_source to 'ldap'
Example 8

Configures Replication Server to use both rs_users and LDAP user authentication:

configure replication server
set user_authentication_source to 'any'
The user account must exist in the rs_users table before you can execute this command.
Example 9
Configures Replication Server to block subscriptions to a replication definition used in an article and a publication:
configure replication server
set block_sub_for_repdef_in_pub to 'on'
Example 10
Configures the DDL datatype mapping:
configure replication server set ddl_datatype_map from ORA.NUMBER(38,0) to HDB.INTEGER
Example 11
Configures the DDL datatype mapping:
configure replication server set ddl_datatype_map from ORA.CHAR(10) to HDB.NCHAR[]
Example 12
Configures the DDL datatype mapping:
configure replication server set ddl_datatype_map from ORA.CHAR(10) to HDB.NCHAR[2]
Example 13
Configures the DDL datatype mapping:
configure replication server set ddl_datatype_map from ORA.NUMBER(3,2) to HDB.DECIMAL(4,5)
Example 14
Configures the DDL datatype mapping:
configure replication server set ddl_datatype_map from ORA.CHAR(-1) to HDB.NCHAR(20)
Example 15
Configures the DDL datatype mapping:
configure replication server set ddl_datatype_map from ORA.NUMBER(-1, -1) to HDB.decimal
Usage
  • Each parameter has two values: the configured value and the run value. Replication Server uses the configured value when it restarts. The run value is the value the Replication Server is using currently. When you start Replication Server the values are equal.

  • Configured values are stored in the <rs_config> system table in the RSSD.
  • Replication Server shuts down automatically when you set the queue block size with the “set block_size to ‘block_size’ with shutdown” Replication Server parameter. The new block size takes effect after you restart Replication Server. See Replication Server Administration Guide Volume 2 > Performance Tuning > Increasing Queue Block Size .

  • varchar_truncation enables truncation of <varchar> columns at the primary or replicate Replication Server. When incoming <varchar> data exceeds the column length specified in the replication definition, the following occurs:

    Table 7: varchar_truncation
     

    varchar_truncation set at primary Replication Server

    varchar_truncation set at replicate Replication Server

    varchar_truncation set to “on”

    Replication Server truncates incoming data to the length specified in the replication definition.

    Replication Server truncates incoming data to the length specified in the replication definition.

    varchar_truncation set to “off”

    RepAgent prints a message in the Replication Server log, and Replication Server ignores rows that exceed the column length specified in the replication definition.

    Replication Server prints a message in the Replication Server log, and the DSI shuts down.

  • Use ha_failover to enable SAP failover support. In the event of an ASE server failover, all connections from Replication Server to ASE will fail. Replication Server will retry connections. Setting ha_failover to on will allow the new connections to failover to the new ASE server.

  • Use ERSSD configuration parameters to configure backup time, directory location and RepAgent name.

    Table 8: ERSSD Configuration Parameters

    ERSSD Configuration Parameter

    Value

    Default

    erssd_backup_start_time

    Time the backup starts.

    Specified as: “hh:mm AM” or “hh:mm PM”, using a 12-hour clock, or “hh:mm” using a 24-hour clock.

    Default: 01:00 AM

    erssd_backup_start_date

    Date the backup begins.

    Specified as “MM/DD/YYYY”.

    Default: current date

    erssd_backup_interval

    Interval between backups of database and log.

    Specified as “nn hours” or “nn minutes” or “nn seconds”.

    Default: 24 hours

    erssd_backup_dir

    Location of stored backup files.

    Should be a full directory path. Configuring this path causes immediate backup.

    Default: Same directory as the transaction log mirror; initial value specified in rs_init.

    erssd_ra

    Configures Replication Agent name, in order to create a route from the current site to another Replication Server. This server name must exist in the interfaces name.

    <erssd_name>_ra

Replication Server Parameters

  • Replication Server parameters specify default values that affect the local Replication Server.

  • Replication Server parameters are static. You must restart Replication Server for them to take effect.

Route Parameters

  • Route parameters specify default values for all routes that originate at the source Replication Server.

  • You can override default values specified using configure replication server by using alter route to set values for individual routes.

  • You must suspend all routes originating at the current Replication Server before executing the configure replication server command. After you have changed the parameter, you must resume all routes for the change to take effect.

Database Parameters

  • Database parameters specify default values for all connections that originate at the source Replication Server.

  • You can override default values specified using configure replication server by using alter connection to set values for an individual connection.

  • You must suspend all connections originating at the current Replication Server before executing configure replication server. After you change the parameter, resume all connections for the change to take effect.

Logical Database Parameters

  • Logical database parameters specify default values for logical connections that originate at the source Replication Server.

  • You can override default values specified using configure replication server by using configure logical connection to set values for a specific logical connection.

  • Logical database parameters are dynamic. They take effect immediately.

Network-Based Security Parameters

  • With the exception of use_security_services and use_ssl, security parameters configured with configure replication server are dynamic; they take effect immediately.

  • use_security_services and use_ssl are static. If you change their values, you must restart Replication Server for the change to take effect.

  • Default network-based security parameters set with configure replication server specify values for all incoming and outgoing pathways related to the current Replication Server.

  • You can override default security settings specified using configure replication server by using alter route or alter connection to reset security values for individual outgoing pathways.

  • If unified_login is set to “required,” only the “sa” user can log in to the Replication Server without a credential. If the security mechanism should go down, the “sa” user can log in to Replication Server with a password and disable unified_login.

  • A Replication Server can support more than one security mechanism. Each supported mechanism is listed in the libtcl.cfg file under SECURITY.

  • Both ends of a route must use compatible Security Control Layer (SCL) drivers with the same security mechanisms and security settings. It is the replication system administrator's responsibility to choose and set security features for each server. Replication Server does not query the security features of remote servers before it attempts to establish a connection. Network connections fail if security features at both ends of the pathway are not compatible.

  • Message encryption is a costly process with severe performance penalties. In most instances, it is wise to set msg_confidentiality to “required” only for certain pathways. Alternatively, choose a less costly feature, such as msg_integrity, to ensure security.

ddl_datatype_map

  • For a specific DDL command, Replication Server first finds the exact match of datatype, length, precision, and scale in the datatype mapping. If this match cannot be found, Replication Server finds the match in the generic map, which is specified with negative numbers in length, precision, and scale. Otherwise, the default datatype mapping is used.

  • If you do not configure datatype mapping, the default mapping takes effect. Refer to Datatype Mapping Changes in the SAP Replication Server New Features Guide for details of default mapping.

  • The datatype that has properties of length, precision, or scale has to be specified with explicit length, precision, and scale for the mapping.
  • The datatype mapping does not take effect in the SAP Business Suite when cluster table replication is enabled.
  • When you change Replication Server from previous versions to 15.7.1 SP204 without upgrading, you need to grant RSSD_primary_user the sa role to restart the Replication Server for the first time.
  • The datatype for the primary database in the mapping matches the datatype stored in the database system except for the datatypes listed in the following table:
    Table 9: Special Cases in DDL Datatype Mapping
    Primary Database Primary Table Datatype Primary Datatype in DDL Datatype Mapping Comments
    Oracle Integer NUMBER(38,0)  
    Binary Float Binary_Float(-2147483647)  
    Timestamp(n) Timestamp(n) The n parameter is defined in the column DATA_SCALE in the table USER_TAB_COLUMNS
    Nchar(n)/nvarchar2(n) Nchar(n)/nvarchar2(n)  

    Float

    float(126,0)

    Binary_float

    BINARY_FLOAT(-1,-1)

    IBM DB2 UDB

    Time(n)/Timestamp(n)

    Time(n)/Timestamp(n)

    The n parameter matches the scale provided in the table SYSCOLUMNS

    Large Objects

    Large Objects(n)

    The n parameter is defined in column LongLength in the table SYSCOLUMNS

    Char(10) for bit data

    CHARACTERFORBITDATA(10)

    varchar(1000) for bit data

    VARCHARFORBITDATA(1000)

    long varchar for bit data

    LONG VARCHARFORBITDATA(32700)

    Microsoft SQL Server

    Varchar(max)

    Varchar(2147483647)

    Varbinary(max)

    Varbinary(2147483647)

    Nvarchar(max)

    Nvarchar(1073741823)

    Text

    Text(2147483647)

    Image

    Image(2147483647)

    Ntext

    Ntext(1073741823)

    Nchar(n)/nvarchar(n)

    Nchar(n)/nvarchar(n)

    Time

    Time(n)

    The n parameter is defined in column precision in the database system table sys.columns

    Timestamp

    Timestamp

    Float

    float(126,0)

     

    uniqueidentifier

    uniqueidentifier(36)

    Varchar(max)

    "Varchar(max)"(2147483647)

    Varbinary(max)

    "Varbinary(max)"(2147483647)

    Nvarchar(max)

    "Nvarchar(max)"(1073741823)

Permissions

configure replication server requires “sa” permission.