Operations Guide

10.1 HotFix 1
- 10.5 HotFix 2
- 10.5 HotFix 1
- 10.5
- 10.2 HotFix 1
- 10.2
- 10.1
- 10.0 HotFix 1
- 10.0

Back Next

updmulti utility

This section provides on how to use the

updmulti

utility.

Prerequisites

updmulti

is a client of the Real Time Web Service. Therefore, the Synchronization Server must be running and the Real Time Web Service must be configured appropriately for the IDT to be synchronized. See the Enabling the Real Time Web Service
for details.

Starting updmulti

You can start

updmulti

from the Console Client by selecting

Tools

Synchronizer

You can specify the

--multi

and

--se=

options in the

Extra Options

field of the Update Synchronizer dialog. The

--se=

parameter nominates the Search Server to use.

Alternatively, you can launch it from the command line. If you use the command line method, be sure to specify the

-5

switch to enable communication and control facilities from the Console.

The command uses the following syntax:

On Windows:

%SSABIN%\updmulti -r<Rulebase> -p<System> -h<Rulebase Server Host>:<Port> -e<IDT>
--se=<Search Server Host>:<Port> [Optional Switches]

On UNIX:

$SSABIN/updmulti -r<Rulebase> -p<System> -h<Rulebase Server Host>:<Port> -e<IDT>
--se=<Search Server Host>:<Port> [Optional Switches]

where

Rulebase: Rulebase connection string. Use one of the following formats for the rulebase connection string:
odb:0:userid/password@service
iir:rb
System: Name of the system to synchronize.
IDT: Specifies the IDT that you want to process. Ensure that the IDT is available in the specified system.
Rulebase Server Host:Port: Host name and port of the Rulebase Server.
If you use Rulebase Server Groups, you can replace this parameter with the
-g<Rulebase Server Group Name>,<Rulebase Connection String>
parameter.
If you use Apache ZooKeeper, you can replace this parameter with the
-z<Host Name1>:<Port1>[,<Host Name2>:<Port2>,<Host Name3>:<Port3>…, <Host NameN>:<PortN>]
parameter.
Search Server Host:Port: Optional. Host name and port of Search Server that you use to run searches. If you use multiple Search Servers, use this parameter to specify the Search Server.

Optional Switches

The following parameters are supported:

-cMaxCycles: Specifies the maximum number of duty cycles to run before shutting down. Not relevant for Flat-File input. The default is to run until instructed to shut down (see Stopping updmulti
).
-fFlatFile: The name of the transaction file when using flat file synchronization.
-g<Rulebase Server Group Name>,<Rulebase Connection String>: Name of the Rulebase Server Group and the rulebase connection string.
-z<Host Name1>:<Port1>[,<Host Name2>:<Port2>,<Host Name3>:<Port3>…, <Host NameN>:<PortN>]: List of ZooKeeper servers based on the host name of the ZooKeeper server and the port on which the host listens for connections.
-i[IDT[,IDX]]: Check the integrity of all IDTs and IDXs in this system, or a particular IDT and IDX. See the Integrity Checking
section for details.
-k: Display erroneous records in detail. Used in conjunction with
-i
.

-l: Assume case of system name in txn file/table matches the case of the system name specified with the
-p
parameter. When not specified, a case insensitive (more expensive) select and compare mechanism is used.
-mRate: Commit rate (defaults to 100). This parameter is relevant for flat-file synchronization only. Determines how frequently 2 phase commit records are saved. To set the commit rate for Synchronization Server, add the
txn_commit_rate
parameter to its configuration file. For more information, see Configuration Settings.

-n: Treats the transaction file as a text file where records are separated by a newline. Without this option, the transaction file is interpreted as a binary file.

-oTime: Collect Optimizer statistics every Time seconds.
-Sn: Disconnects the connection to the source database and reconnects to it after the specified number of duty cycles.

-tTimeOut: Specifies the number of seconds between duty cycles. The default value is 60 seconds. A value suffixed with ms is treated as milliseconds.
-vpsui: Verbosity (p=progress, s=stats, u=usage, i=info)
-yMax[,Wait]: Fault tolerance feature. Synchronizer automatically restarts Max times in case of failure. For more information, see the Restarting Automatically section.
-zTxn: Transaction sequence number to skip.
-ZTxn: Transaction sequence number to delete.
-5<Job Number>:<Console Server Host Name>:<Console Server Port Number>: Required when you use flat-file synchronization. Indicates that the specified job connects to the Console Server through the specified port number. Use this parameter to enable the progress messages and the ability to shut down the synchronizer from the console. Specify the job number as 0 to connect to the Console Server and register the job as an anonymous job. Other job numbers are reserved for the jobs that the console launches.
--offset=nnn: This is an optional parameter which applies to flat-file processing only. This number, if present, is added to the sequence number of each record processed. May be used to ensure global uniqueness of flat-file transactions.
--parallel=n: Optional. Applicable only for Oracle. Indicates the number of threads that you want to use for the synchronization process. Use this parameter to perform parallel processing for improved performance.
--rbcheck: Requests periodic checks of Rulebase Server connectivity and to abort when inaccessible. Under normal circumstances,
updmulti
accesses the RB Server very seldom, and is therefore unaware that it may have stopped. This option is useful to automatically stop
updmulti
when the servers have been stopped with a hard shut down.
--validate: When synchronizing data using flat file or NSA table to Identity Table.; By default,
updmulti
performs the following validation checks:

Field
Validation

Numeric - N
Checks for a numeric value that aligns to the right and has leading zeros instead of spaces.

Character String - C
Checks for spaces. Does not allow a null value (0x0000) as a padding character.

Unicode String - W
Checks if the Unicode spaces (0x0020) has padding. Does not allow a null value (0x0000) as a padding character.; Use the
--validate
option to validate the data. The following validations are optional as the errors calculated here are based on percentage of occurrence:

Field
Validation

Character String - C
Counts the number of rows where values in column are using full buffer. Reports an error when 99% of data meets this condition. This may not be an error and could be due to data truncation.

Unicode String - W
Counts the number of rows where values in column are using full buffer. Reports error when 99% of data meets this condition. This may not be an error and could be due to data truncation.
Count the number of rows where values contains invalid Unicode spaces as padding character, that is mix of endianess 0x2000 and 0x0020. The problem is 0x2000 is also valid Unicode, so if the 75% or more rows are ending with 0x2000 character on a big endian system or 0x0020 on little endian system, then report it as an error.
Count the number of rows where values contains ASCII spaces instead of Unicode spaces as padding character, that is 0x2020 is used instead of 0x0020. Again the problem is 0x2020 is also a valid Unicode, so if the 75% or more rows are ending with 0x2020 character then report it as an error.; When you use the
--validate
option and it results in errors, the data cannot not be rolled back. It is recommended to use this option in a test environment. Ensure that the input data has correct Unicode spaces.
--reader_sz=nnn: Size of reader circular buffer size. The default value is 5000.
--se=<Search Server Host>:<Port>: Host name and port of Search Server to build and maintain persistent IDs. If you use multiple Search Servers, use this parameter to specify the Search Server. For more information about persistent ID, see
Informatica MDM Registry Edition Design Guide
.
--persist=Multi-Search-Name: Specifies the name of the clustering strategy that describes how to perform an initial clustering. The Update Synchronizer terminates after the initial clustering is created. Do not specify this parameter during normal synchronization. For more information about persistent ID, see
Informatica MDM Registry Edition Design Guide
.

Field	Validation
Numeric - N	Checks for a numeric value that aligns to the right and has leading zeros instead of spaces.
Character String - C	Checks for spaces. Does not allow a null value (0x0000) as a padding character.
Unicode String - W	Checks if the Unicode spaces (0x0020) has padding. Does not allow a null value (0x0000) as a padding character.

Field	Validation
Character String - C	Counts the number of rows where values in column are using full buffer. Reports an error when 99% of data meets this condition. This may not be an error and could be due to data truncation.
Unicode String - W	Counts the number of rows where values in column are using full buffer. Reports error when 99% of data meets this condition. This may not be an error and could be due to data truncation. Count the number of rows where values contains invalid Unicode spaces as padding character, that is mix of endianess 0x2000 and 0x0020. The problem is 0x2000 is also valid Unicode, so if the 75% or more rows are ending with 0x2000 character on a big endian system or 0x0020 on little endian system, then report it as an error. Count the number of rows where values contains ASCII spaces instead of Unicode spaces as padding character, that is 0x2020 is used instead of 0x0020. Again the problem is 0x2020 is also a valid Unicode, so if the 75% or more rows are ending with 0x2020 character then report it as an error.

Output goes to the console, and you can redirect it to a log file if required. On Windows, run the following command to start the updmulti utility:

start /min %SSABIN%\updmulti -rodb:0:userid/password@service -p<System> -vp
-h%SSA_RBHOST% --se=%SSA_SEHOST%

The

System

parameter indicates the name of the system that you want to synchronize, and the

odb:0:userid/password@service

string indicates the rulebase connection string. You can also use

iir:rb

as the rulebase connection string, which does not expose the password on the command line.

Stopping updmulti

This section describes about how to stop the

updmulti

utility.

Via Console

updmulti can be shut down from the Console if it was started from either

the Console, or

from a command prompt and the

-5

switch was specified.

The Console sends a message to

updmulti

to c

"stop when the next duty cycle begins".

updmulti

will acknowledge the receipt of the shutdown request by displaying a progress message and will shutdown in due course.

Server Shutdown

The synchronizer periodically checks its communication channel to the Rulebase Server when started with the

--rbcheck

switch. If the Rulebase Server stops for any reason (for example, due to a hard shutdown), the Update Synchronizer terminates with an error condition.

MDM Registry Edition servers do not shut down if the clients are attached, unless you use the hard shutdown option.

Rename Saved Search

Table of Contents

Operations Guide

Operations Guide

updmulti utility

updmulti utility

Prerequisites

Starting updmulti

Optional Switches

Stopping updmulti

Via Console

Server Shutdown