The SP303 release lets you:
- Provide the statistics on a subscription at the table and database levels.
- Specify the order of materialization using the in order parameter.
- Specify the number of select threads for each table.
Let’s take a closer look at these enhancements:
- Now you can get detailed information about table/database subscriptions using the with statistics parameter. For example, the number of select threads used in materialization, Initial Load Data, Catchup Data and so on. This change affects two commands – check subscription and check database subscription.
- check subscription command example: The following example checks the status of the subscription <titles_sub> for the replication definition titles_rep, where the replicate database is SYDNEY_DS.<pubs2>:
check subscription titles_sub
with replicate at SYDNEY_DS.pubs2 with statistics
- check database subscription command example: The command can be used to check the status of database subscription and the database tables with specific materialization state. For example, tables for which materialization is pending, valid, or failed.
The following example checks the status of the subscription (sub1) using with statistics parameter for the replicate data server (Rep_ds1) and replicate database (Rep_db1):
check database subscription sub1, Rep_ds1, Rep_db1, with statistics
- Materialization in user-specified order: This enhancement is related to database replication definition, and it affects the create database replication definition command.
For this command, a new parameter (in order) sets the order in which tables within a file are materialized. A user-specified file (text file) lists the tables to be materialized. In this example, the file <reptablelist.txt> provides the order of table materialization.
create database replication definition <db_repdef> with primary at <ds1>.<pdb1> replicate tables in files (‘/sap/user/<reptablelist.txt>’)in order
- Database materialization with multiple select: In the same file, you can also specify the number of select threads for each table. You can achieve this using the format – S:number.
create database replication definition <db_repdef>
with primary at <ds1>.<pdb1>
replicate tables in files (‘/sap/user/<reptablelist.txt>’)in order
A sample file:
In the sample file, table 1 is materialized with two select threads, table 2 with one select thread (default value), and table 3 with four select threads.
For more information on these commands, refer to the SAP Replication Server Reference manual.