rs_subcmp
An executable program that compares the data of a replicated table to the primary version of the table. rs_subcmp also performs schema comparison between replicated and primary tables and between replicated and primary databases. These features aid in finding—and optionally reconciling—missing, orphaned, and inconsistent rows and schemas. On UNIX systems, this program is called rs_subcmp. On Windows systems, the program is called subcmp.
The rs_subcmp program is located in the bin subdirectory of the release directory. See the Replication Server installation and configuration guides for your platform for more information.
For rs_subcmp to work, the SYBASE environment variable, the library path environment variable, and the SYBASE_JRE6 must be set. If you use rs_subcmp for schema comparison, ensure that rs_subcmp can locate the ddlgen executable file and that ddlgen can successfully run in your Replication Server environment. See the Usage section for instructions.
rs_subcmp is intended to reconcile SAP databases only. You cannot use rs_subcmp for schema comparisons of Adaptive Server 15.7 SP100 and later. Use the SAP® Replication Server® Data Assurance Option for schema comparisons of Adaptive Server 15.7 SP100 or later. See the Replication Server Data Assurance Option documentation.
rs_subcmp [-R | -r] [-v] [-V] [-z[1 | 2] [-g] [-h]] [-f <config_file>] [-F] -S <primary_ds> [-D <primary_db>] -s <replicate_ds> [-d <replicate_db>] -t <table_name> [-T <primary_table_name>] -c <select_command> [-C <primary_select_command>] -u <user> [-U <primary_user>] [-p <passwd>] [-P <primary_passwd>] [-B <primary_init_batch>] [-b <replicate_init_batch>] [-n <num_iterations>] [-w <wait_interval>] [-e <float_precision>] [-E <real_precision>] [-k <primary_key_column> [-k <primary_key_column>]...] [-i <identity_column>] [-l <text_image_column_name >[-l <text_image_column_name>]...] [-L <text_image_length_in_kilobytes>] [-N <text_image_column_name >[-N <text_image_column_name>]...] [-Z <language>] [-o <sort_order>] [-O <sort_order>] [-J <rs_subcmp_charset>] [-j <rep_charset>] [-a <replicate_column_name> <primary_column_name > [-a <replicate_column_name> <primary_column_name>]...] [-q <unicode_sort_order>] [-Q <unicode_sort_order>] [-x <schema_flag>] [-X <filter_flag>] [-I <interface_file>] [-H <normalization_option>]
Reconciles the replicate data with the primary data, making a final verification of data inconsistencies at the primary database. rs_subcmp inserts, deletes, and updates rows at the replicate database so that the replicate data matches the primary data.
Reconciles the replicate data with the primary data, without making a final verification of data inconsistencies at the primary database, as -R does. rs_subcmp inserts, deletes, and updates rows at the replicate database so that the replicate data matches the primary data.
Prints version information.
(Visual) prints the results of the comparison on the display (standard output). If you do not use the -V flag, rs_subcmp does not report differences between rows. Values of <text>, <unitext>, or <image> data are not printed. Instead, rs_subcmp reports whether the inconsistency is in the <text>, <unitext>, or <image> columns or in the columns of other datatypes.
Enables trace. -z1, the default, provides basic trace information, such as comparisons of column headings. -z1 also prints information about numeric precision differences. -z2 provides trace information on comparisons of all rows and commands.
Specifies the name of the configuration file for rs_subcmp.
Displays the format (syntax) to use for the <config_file>. A configuration file must use the syntax displayed with the -F option, and must contain all required syntax parameters.
The name of the data server with the primary data for the subscription.
The name of the database where the primary data for the subscription is stored.
The name of the data server with the replicate copy of the data.
The name of the database with the replicate copy of the data.
The name of the table in the primary and replicate databases with the data to be compared. If the name is different in the databases, use the -T option to specify the name of the table in the primary database. You can include table owner name information here.
The name of the table in the primary database. Use this option when the table name is different in the primary and replicate databases. You can include table owner name information here.
A select command that retrieves the subscription’s data from both the primary and replicate copies of the data. Use -C to specify a different command for the primary data. select commands must order rows based on the primary key.
You can include columns with text, unitext, or image datatypes in the select command, with the following requirements:-
Columns with text, unitext, or image datatypes cannot be primary key columns.
-
You must place columns with text, unitext, or image datatypes at the end of the select list.
-
By default, the replicate table does not allow null values for text or image columns. You must include the -N flag in the rs_subcmp executable to indicate that a null value is allowed in the text, unitext, or image column of the replicate table.
-
A select command that retrieves the subscription data from the primary copy of the data. Use this option and -c when you need a different select command for the primary and replicate databases. select commands must order rows based on the primary key.
The login name used to log into the primary and replicate data servers. If you need different login names, use the -U option to specify a different primary data server login name.
The login name used to log into the primary data server. Use this option and the -u option when different login names are required for the primary and replicate data servers.
The password to use with the <user> login name and, if supplied, the <primary_user> login name. If you omit this option, rs_subcmp uses a null password. If you specify a different password for the <primary_user> login name, specify it with the -P option.
The password to use with the <primary_user> login name.
A command batch to be executed when initially connecting to the primary database. The batch can be used for any purpose, such as to set the isolation level. The batch is run after rs_subcmp logs into the primary database.
A command batch to be executed when initially connecting to the replicate database. The batch can be used for any purpose, such as to turn off triggers when running rs_subcmp in a warm standby application, or to set the isolation level. The batch is run after rs_subcmp logs into the replicate database.
The number of times that rs_subcmp examines the inconsistent rows it finds. The default is 10 iterations. The first iteration may find many inconsistencies due to normal time lag in replication. Additional iterations allow rs_subcmp to distinguish true inconsistencies from the inconsistent rows that are corrected through normal replication activity.
The number of seconds rs_subcmp waits before beginning another iteration. The default is 5 seconds.
Sets the number of decimal places in exponential notation that floating point values are expected to agree. By default, this is set to the maximum precision supported by the platform.
Sets the number of decimal places in exponential notation that real values are expected to agree. By default, this is set to the maximum precision supported by the platform.
A column name that is part of the primary key for the table. The primary key must be unique and it cannot be a text, unitext, or image column. Use the -k option for each column in the primary key. If the primary and replicate column names are different, the name specified here is the replicate column name.
The name of the <xidentity> column in the replicate table.
Turns off logging of updates to a replicate text, unitext, or image column. By default, text, unitext, or image column updates are logged.
Sets the longest value the data server returns for text, unitext, or image columns. The default value is 2048K.
Indicates that a null value is allowed in the text, unitext, or image column of the replicate table. By default, the replicate table does not allow null values for text, unitext, or image columns.
The name of the language in which rs_subcmp generates error and informational messages. If not specified, it uses the language specified in the “default” locale entry for your platform.
The name of the sort order used in your replication system. rs_subcmp uses this information to compare primary key columns.
The name of the sort order used in your replication system. rs_subcmp uses this information to compare all columns.
The name of the character set used by rs_subcmp error and informational messages and in all configuration parameters and command line options. If you do not specify <rs_subcmp_charset>, it is set to the character set specified in the “default” locale entry for your platform.
The name of the character set used by the replicate data server. The rs_subcmp program uses this character set when comparing and reconciling the replicate and primary versions of a table. If you do not specify a <rep_charset,> it is set to the <rs_subcmp_charset> character set.
Specifies the primary column name associated with a replicate column. Use this option if a replicate column name is different from that of the primary column.
NoteWhen you use the -a option, the replicate column name must come before the associated primary column name.
Specifies the Unicode sort order rs_subcmp uses to compare Unicode primary key columns.
Specifies the Unicode sort order rs_subcmp uses to compare all Unicode columns.
- Specifies the rs_subcmp comparison type. The possible values of the <schema_flag> are:
0 – data comparison. This is the default value.
1 – database schema comparison between two databases.
2 – table schema comparison between two tables.
Specifies the schema types and subtypes included or excluded from the comparison. If the value starts with “+”, only the schema types are selected for comparison, and the subschema types are ignored. Otherwise, the schema types and subschema types are both not selected and not used for comparison. For a list of schema types and schema subtypes supported by rs_subcmp, see "Schema types supported by rs_subcmp" table and "Schema subtypes supported by rs_subcmp" table.
Specifies the interface file location. For more information on the interface file, see the Replication Server configuration guides for your platform.
Creates reconciliation file for inconsistent data.
Performs fast comparison.
Indicates how to normalize the data when performing fast comparison. For a list of normalization options supported by rs_subcmp, see "Normalization options supported by rs_subcmp" table.
Starts rs_subcmp using a configuration file called titleauthor.cfg.
rs_subcmp -ftitleauthor.cfg
The configuration file consists of the following:# titleauthor.cfg - Reconcile # SYDNEY_DS.pubs2.dbo.titleauthor with # TOKYO_DS.pubs2.dbo.titleauthor. # PDS = TOKYO_DS RDS = SYDNEY_DS PDB = pubs2 RDB = pubs2 PTABLE = titleauthor RTABLE = titleauthor PSELECT = select au_id, title_id, au_ord,\ royaltyper from titleauthor order by au_id,\ title_id RSELECT = select au_id, title_id, au_ord,\ royaltyper from titleauthor order by au_id,\ title_id PUSER = repuser RUSER = repuser PPWD = piglet RPWD = piglet KEY = au_id KEY = title_id RECONCILE = Y VISUAL = Y NUM_TRIES = 3 WAIT = 10
rs_subcmp compares the primary and replicate tables called titleauthor and generates the following output:
$SYBASE/bin/rs_subcmp -f ttl_au.cmp INCONSISTENT ROWS: _________Replicate row________ au_id title_id au_ord royaltyper ------------------------------------------- 672-71-3249 TC7777 1 40 __________Primary row_________ au_id title_id au_ord royaltyper ------------------------------------------- 672-71-3249 TC7777 1 50
Starts rs_subcmp using a configuration file called subcmp.cfg. Command line flags override the configuration file settings, to reconcile differences in the primary and replicate versions of the authors table, performing a final verification.
rs_subcmp -R -fsubcmp.cfg -STOKYO_DS -Dpubs2 \ -sSYDNEY_DS -dpubs2 -tauthors
The primary data server and database are TOKYO_DS and pubs2. The replicate data server and database are SYDNEY_DS and pubs2.
- Compares the schema of the authors table on two different servers, PASE and R2ASE, each having a database named pubs2 using a configuration file called config.cfg file:
rs_subcmp -f config.cfg
The configuration file contains:PDS = PASE RDS = R2ASE PDB = pubs2 PTABLE = authors RTABLE = authors PUSER = sa RUSER = sa PPWD = RPWD = SCHEMAFLAG = 1
- Compares schema between two databases without a configuration file:
rs_subcmp -Spds -srds -Dpdb -drdb -Usa -Psa_pwd -usa -psa_pwd -x1 - Compares schema of two databases excluding index, trigger, and datatype:
rs_subcmp -Spds -srds -Dpdb -drdb -Usa -Psa_pwd -usa -psa_pwd -x1 -XitD - Compares all table schemas and user schemas:
rs_subcmp -Spds -srds -Dpdb -drdb -Usa -Psa_pwd -usa -psa_pwd -x1 -X+TU
Run rs_subcmp when primary changes do not occur.
- Set environment variables for rs_subcmp to work:
-
SYBASE – set to the release directory
-
SYBASE_JRE6 – set to either the 32-bit or 64-bit JRE location:
Table 1: Platform and SYBASE_JRE6 Variable Location Platform SYBASE_JRE6 Variable Location 32-bit UNIX /$SYBASE(ASE)/shared/JRE-6_0_24_32BIT 64-bit UNIX /$SYBASE(ASE)/shared/JRE-6_0_24_64BIT 32-bit Windows \%SYBASE%\shared\JRE-6_0_24_32BIT 64-bit Windows \%SYBASE%\shared\JRE-6_0_24_64BIT -
Library path variable – set to $SYBASE/$SYBASE_OCS/lib for UNIX or %SYBASE%\%SYBASE_OCS%\lib for Windows
Each supported operating system may have a different library path variable:Table 2: Operating System and Library Path Variable Operating System RS6000 LIBPATH HP UX SHLIB_PATH Linux LD_LIBRARY_PATH Solaris LD_LIBRARY_PATH Windows PATH
-
For rs_subcmp schema comparison to work, set the The DDLGENLOC and SYBROOT environment variables.
rs_subcmp must be able to locate and successfully run the ddlgen executable file for schema comparison. If <DDLGENLOC> is not set, rs_subcmp looks for ddlgen at its default location, which is %SYBASE%\ASEP\bin\ddlgen. To ensure that ddlgen runs successfully, the environment variables that ddlgen uses must be set correctly.Note If the ddlgen is not at its default location, you must set the <DDLGENLOC> to the full path such as %SYBASE%\ASEP\bin\ddlgen.The SYBROOT environment variables must also be set to the SYBASE environment variable.
- The following requirements apply to rs_subcmp:
If you provide a configuration file and also use command line options, the command line values override the values in the configuration file.
The lowercase options -d, -c, -u, -p, and -t provide values for both primary and replicated data. Use the uppercase options to override the values for primary data.
The only required uppercase option is -S.
The primary key specified with -k must be unique. If you do not specify any primary key columns with the -k option, all columns are considered to be part of the primary key.
Use a positive integer in -L to specify a new value, overwriting the default value of 26K, for the byte length of text and image columns:
-L = <<new_value>>
For instance, if you want text and image columns to be 65,536 bytes, enter:
-L = <64>
- These options can be used to specify a non-default table owner or a different primary replicate table or column name:
For options -t, -T, -c, and -C, table owner information can be included (for example, ling.authors).
Owner, table, and column names specified for the -c option should be those of the replicate table.
Owner, table, and column names specified for the -C option should be those of the primary table.
The column name specified for the -k option is the column name of the replicate table.
rs_subcmp creates a report file after every schema comparison. The report file details the comparison result between two tables or two databases. The report file is named reportPROCID.txt. If inconsistencies exist, rs_subcmp creates a reconciliation script named reconcilePROCID.sql. The report file and the reconciliation script are saved in the same directory from which rs_subcmp executed.
The reconciliation file’s SQL statements cannot contain <text>, <unitext>, or <image>.
rs_subcmp creates a reconciliation file if you specify the -g option. The file is named reconcile_file_PROCID.sql and is located at the current working directory.
Return codes
The following return codes can be returned by rs_subcmp:
Return Code |
Meaning |
|---|---|
0 |
The replicated and primary tables are the same. |
1 |
An error occurred while executing rs_subcmp. |
2 |
The replicated and primary tables are different. |
Configuration file
You can create a file containing rs_subcmp parameters and specify it on the command line using the -f flag. Each line in the configuration file consists of a parameter name, an equal sign (=), and a value.
rs_subcmp configuration file parameters lists the parameters that can be used in the rs_subcmp configuration file and the corresponding command line option for each parameter.
Configuration parameter |
Command-line option |
Value |
|---|---|---|
<PDS> |
-S |
Primary data server name |
<RDS> |
-s |
Replicate data server name |
<PDB> |
-D |
Primary database name |
<RDB> |
-d |
Replicate database name |
<PTABLE> |
-T |
Primary table name |
<RTABLE> |
-t |
Replicate table name |
<PUSER> |
-U |
Primary user name |
<RUSER> |
-u |
Replicate user name |
<PPWD> |
-P |
Primary password |
<RPWD> |
-p |
Replicate password |
<KEY> |
-k |
Primary key element in replicate table |
<PINITBATCH> |
-B |
Primary database connection initialization batch. Can span multiple lines if newline characters are preceded by a “\” (backslash). Up to 1024 characters per line and 64K characters total are allowed. |
<RINITBATCH> |
-b |
Replicate database connection initialization batch. Can span multiple lines if newline characters are preceded by a “\” (backslash). Up to 1024 characters per line and 64K characters total are allowed. |
<PSELECT> |
-C |
Primary select command. Can span multiple lines if newline characters are preceded by a “\” (backslash). Up to 1024 characters per line and 64K characters total are allowed. |
<RSELECT> |
-c |
Replicate select command. Can span multiple lines if newline characters are preceded by a “\” (backslash). Up to 1024 characters per line and 64K characters total are allowed. |
<RECONCILE> |
-r |
Reconcile differences (Y or N) |
<RECONCILE_CHECK> |
-R |
Reconcile differences with primary verification (Y or N) |
<TRACE> |
-z |
Enable trace with optional level (optional integer) |
<FPRECISION> |
-e |
Expected floating point precision (integer—default is platform-dependent) |
<RPRECISION> |
-E |
Expected real precision (integer—default is platform-dependent) |
<WAIT> |
-w |
Seconds between comparisons (integer—default is 5 seconds) |
<NUM_TRIES> |
-n |
Number of comparisons (integer—default is 10 iterations) |
<VISUAL> |
-V |
Print results (Y or N) |
<IDENTITY> |
-i |
<identity> column name in replicate table |
<TXT_IMG_LEN> |
-L |
The longest value, in kilobytes, the data server returns for <text>, <unitext>, or <image> columns. |
<NO_LOG> |
-l |
Do not log updates for this replicate <text>, <unitext>, or <image> column |
<NULLABLE> |
-N |
The <text>, <unitext>, or <image> column in the replicate table accepts null values. |
<LANGUAGE> |
-Z |
Language of rs_subcmp error and informational messages |
<SORT_ORDER> |
-o |
Use the specified sort order to compare primary key columns. |
<SORT_ORDER_ALL_COLS> |
-O |
Use the specified sort order to compare all columns. |
<SCHARSET> |
-j |
Character set of rs_subcmp |
<RCHARSET> |
-J |
Character set of the replicate data server |
<REP_PRI_COLNAME> |
-a |
Replicate-Primary column name pair |
<UNICODE_SORT_ORDER> |
-q |
The Unicode sort order rs_subcmp uses to compare Unicode primary key columns. |
<UNICODE_SORT_ORDER_ALL_COLS> |
-Q |
The Unicode sort order rs_subcmp uses to compare all Unicode columns. |
SCHEMAFLAG |
-x |
The rs_subcmp comparison type. |
<FILTER> |
-X |
The filter used to indicate the schema and schema subtypes included or excluded in the schema comparison. See Schema types supported by rs_subcmp and Schema subtypes supported by rs_subcmp for a list of schema types and schema subtypes supported by rs_subcmp. |
<IFILE> |
-I |
The interface file location. |
<RECONCILE_FILE> |
-g |
Indicates whether to create a reconciliation file or not. Values:
Default: N |
<FASTCMP> |
-h |
Indicates whether to perform fast comparison or not. Values:
Default: N |
<HASH_OPTION> |
-H |
Indicates the normalization option used for fast comparison. If this parameter is not included in the configuration file, rs_subcmp normalizes the data using native byte order and character set. See "Normalization options supported by rs_subcmp" table for a list of the normalization options supported by rs_subcmp. |
Requirements for select commands
The select commands specified by -c (RSELECT) and -C (PSELECT) must return columns with the same names and datatypes from both the primary and the replicate databases.
You must have a clustered index on the primary key or an order by clause in the select command. select commands must order rows based on the primary key. If rs_subcmp does not receive rows in the correct order, it may delete rows in the replicate table.
Do not select <rs_address> datatypes with the -c or -C options. If replicate tables contain columns using the <rs_address> datatype, the primary and replicate versions of these columns may not be identical. Replication Server filters out updates to these columns so as not to replicate them unnecessarily.
How rs_subcmp works
- rs_subcmp logs into the primary and replicate databases and executes the supplied select commands. It verifies that the commands return the same columns, based on the name and datatype of each column. If the returned columns match, rs_subcmp compares the primary and replicate rows and creates these lists:
Missing rows – rows at the primary, but not at the replicate
Orphaned rows – rows at the replicate, but not at the primary
Inconsistent rows – rows at the replicate and the primary with matching primary keys, but differences in other columns
- After the three lists are compiled rs_subcmp iterates for the specified number of times, checking:
If missing rows appear at the replicate
If orphaned rows disappear from the replicate
If inconsistent rows match
If the new replicate row value matches the primary row value from the previous iteration
After the specified number of iterations, the contents of the three lists are printed to the standard output if you specified the -V option.
Reconciling inconsistencies
rs_subcmp reconciles missing, orphaned, and inconsistent rows if you specify the -R or -r option.
- If you specify the -r option, rs_subcmp reconciles the primary and replicate copies. It passes the final lists and modifies the replicate table as follows:
Inserts rows remaining in the missing rows list
Deletes rows remaining in the orphaned rows list
Updates inconsistent rows to match the primary rows
- If you specify the -R option, rs_subcmp reconciles the replicate table to the primary version in the same way as with the -r option. However, before it inserts a missing row or deletes an orphaned row, it logs into the primary database and performs a select on the row to verify that:
The row still exists (in the case of a missing row in the replicate table), or
The row does not exist (in the case of an orphaned row in the replicate table).
Reconciling IDENTITY columns
If the values in an <identity> column for a row are inconsistent, rs_subcmp reconciles them by deleting the row in the replicate database before inserting the row from the primary database.
Reconciling text, unitext, or image datatypes
- Unlike other datatypes, inconsistencies in <text>, <unitext>, or <image> values are not stored in a list. To reconcile a missing or inconsistent row that contains a <text> or <image> value, rs_subcmp logs back into the primary database and re-executes the select statement. If the inconsistent or missing row is found, rs_subcmp modifies the replicate table by updating or inserting the row. However, if the inconsistent or missing row is not found in the primary table, rs_subcmp takes the following actions:
For an inconsistent row, rs_subcmp deletes the row from the replicate table
For a missing row, rs_subcmp takes no action
Using the Adaptive Server option set textsize as part of the select statement can limit the amount of text compared. For example, the following example shows the effect of setting the textsize to 10. The first select statement returns 30 characters of <text>:
set textsize 30 select * from zetext a b c -------- --------- ----------- abba apples odd one here beta banana rotten caro celery not carrots
The next select statement sets the <size> of the text to 10:
1> set textsize 10 select * from zetext 2> go a b c
-------- --------- ------------ abba apples odd one beta banana rotten caro celery not carrots --------------------------------------------------- (3 rows affected)
Using rs_subcmp in international environments
rs_subcmp provides support for international environments with the -Z<language>, -o <sort_order>, -O <sort_order>, -q <unicode_sort_order>, -Q <unicode_sort_order>, -J <rs_subcmp_charset>, and -j <rep_charset> options.
rs_subcmp performs character set conversion when comparing and reconciling the replicate and primary versions of a table. The method is similar to how Replication Server converts character sets, so you can expect to see similar results.
For example, if the primary and replicate data server’s character sets are incompatible, no conversion takes place. If the character sets are incompatible but a single character from the primary data server’s character set has no representation in the replicate server’s character set, the character is replaced with a “?” and processing continues.
rs_subcmp uses the character set of the replicate data server in all operations involving user data. To specify the replicate data server’s character set, use the -j command line option or the <RCHARSET> configuration file parameter.
Noters_subcmp does not have a parameter for the primary data server’s character set because all data operations are done in the replicate data server’s character set. The program depends on the primary data server to convert all character data to the replicate data server’s character set. This is comparable to how Replication Server works during subscription materialization.
You can also specify a character set for rs_subcmp if it is different from the replicate data server’s character set. To do this, use the -J command line option or the <SCHARSET> configuration file parameter. When you specify a character set, rs_subcmp converts its string-type configuration parameters from the rs_subcmp character set to the replicate data server’s character set.
Requirements for character sets and sort orders
- The following requirements apply for specifying character sets and sort orders in rs_subcmp:
All characters in object names (including servers, databases, tables, and column names) must be compatible with the <rs_subcmp_charset> and <rep_charset> character sets; otherwise rs_subcmp will fail to execute.
If the character sets of the replicate and primary data servers differ, the replicate data server’s character set must be installed at the primary data server. This enables the primary data server to do character set translation.
If the replicate and primary data servers use different sort orders and the where clause of the select statement includes <character> or <text> datatypes, results may be confusing. To avoid confusion, run rs_subcmp first without the -r or -R (reconcile) options and with the -V (visual) option to see the potential effects on your data.
Using sort orders
You can specify nonUnicode sort order in two ways: using the -o option or using the -O option.
- If you specify the -o option, rs_subcmp:
Performs a simple binary comparison of the primary key columns.
If the primary keys match, rs_subcmp performs a binary comparison of the remaining columns. If they don’t match, an inconsistent row is reported.
- If the primary key columns do not match, rs_subcmp compares them using the specified sort order.
If the primary key columns don’t match, the row is reported missing or orphan.
If the primary key columns test equal using the sort order, the row is reported inconsistent.
- If you specify the -O option, rs_subcmp:
-
Performs a column comparison using the specified sort order for all columns of types <char>, <varchar>, and <text>.
-
Does not perform a binary comparison.
-
If no sort order is specified, rs_subcmp performs a simple binary comparison on each column of the primary and replicate row.
Using Unicode sort orders
You can specify Unicode sort order in two ways: using the -q option or using the -Q option.
- If you specify the -q option, rs_subcmp:
Performs a simple binary comparison of the Unicode primary key columns.
If the primary keys match, rs_subcmp performs a binary comparison of the remaining columns. If they don’t match, an inconsistent row is reported.
- If the primary key columns do not match, rs_subcmp compares them using the specified sort order.
If the Unicode primary key columns don’t match, the row is reported missing or orphan.
If the primary key columns test equal using the sort order, the row is reported inconsistent.
- If you specify the -Q option, rs_subcmp:
Performs a column comparison using the specified sort order for all Unicode columns.
Does not perform a binary comparison.
If no sort order is specified, rs_subcmp performs a simple binary comparison on each Unicode column of the primary and replicate row.
Type |
Description |
|---|---|
A |
All aliases in the database. |
D |
All defaults in the database. |
E |
All user-defined datatypes in the database. |
G |
All groups in the database. |
R |
All rules in the database. |
T |
All user tables in the database. Includes table elements such as indexes, keys, constraints, and triggers. |
U |
All users in the database. |
V |
All views in the database. |
P |
All procedures in the database. |
Type |
Description |
|---|---|
c |
Constraint |
d |
Bind default |
f |
Foreign key |
g |
Grant |
i |
Index |
m |
Procedure mode |
p |
Primary key |
r |
Bind rule |
t |
Trigger |
Normalization option |
Description |
|---|---|
lsb |
Normalizes all byte-order-dependent data to lsb-first (little-endian) byte order. |
msb |
Normalizes all byte-order-dependent to msb-first (big-endian) byte order. |
unicode |
Normalizes the character data to Unicode (UTF-16). |
unicode_lsb |
Normalizes lsb in conjunction with Unicode for platform independence. |
unicode_msb |
Normalizes msb in conjunction with Unicode for platform independence. |