Table of Contents

Search

  1. Preface
  2. Introduction
  3. Servers
  4. Console Client
  5. Search Clients
  6. Table Loader
  7. Update Synchronizer
  8. Globalization
  9. Siebel Connector
  10. Web Services
  11. ASM Workbench
  12. System Backup and Restore
  13. Batch Utilities

updsync utility

updsync utility

The updsync is named as
Update Synchronizer
utility. This section provides information on how to start and stop this utility.

Starting updsync

Start the
updsync
utility from the Console Client, use
Tools
Synchronizer
or start from the command line.
If you start it from the command line, 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%\updsync -r<Rulebase> -p<System> -h<Rulebase Server Host>:<Port> [Optional Switches]
On UNIX:
$SSABIN/updsync -r<Rulebase> -p<System> -h<Rulebase 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.
Rulebase Server Host:Port
Host name and port of the Rulebase Server.
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.

Optional Switches

The following parameters are supported:
-cMaxCycles
Specifies the maximum number of duty cycles to run before shutting down. The default is to run until instructed to shut down, see
Stopping updsync
.
-eIDT
Specifies that only transactions that affect the specified IDT will be processed. This permits the synchronization of a single IDT when multiple IDTs have been defined in the System. The default (when
-e
has not been specified) is to synchronize all IDTs in the System.
-fFlatFile
The name of the transaction file when using flat file synchronization.
-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. Transactions stored by triggers in the txn table insert the system name in lower case.
-mRate
Commit rate (defaults to 100).
-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.
--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.
-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 delete.
-5<Job Number>:<Console Server Host Name>:<Console Server Port Number>
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.
--rbcheck
The Update Synchronizer periodically checks its communication channel to the Rulebase Server. Use
--rbcheck
to stop the Update Synchronizer when the Rulebase Server stops with a hard shutdown.
The
-d
option specifies the time duration to retry the connection to the Rulebase Server. If the Informatica Identity Resolution system exceeds the time duration to retrieve connectivity, the Update Synchronizer exits the services.
When you start the the Update Synchronizer with
–rbcheck
,
-d
, and
-y
options, the
-d
option overrides the
-y
option in the case of rule base check failure.
--validate
Validates data when you synchronize the data with Identity Table (IDT) using a flat file or NSA table.
By default, the Update Synchronizer 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 might not be an error and can 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 updsync utility:
start /min %SSABIN%\updsync -rodb:0:userid/password@service -p<System> -vp -h%SSA_RBHOST%
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 updsync

You can stop this utility using the console or through script.

Via Console

You can shut down the Update Synchronizer if you started it from the Console or from a command line with the
-5
switch.
The Console sends a message to the Synchronizer to stop when the next duty cycle begins. The Synchronizer will acknowledge the receipt of the shutdown request by displaying a progress message and will shutdown in due course.

Via Script

Alternatively, you may schedule the Synchronizer to shut down by running the following script to add a Shutdown Request to the transaction file. It will not shut down until it processes the request. This may take a while if there is a backlog of transactions to process. Therefore it is recommended that the Synchronizer be shut down via the Console.
For Win32:
%SSABIN%\syncstop System Uid Pwd Svc [DBType]
For Unix:
$SSABIN/syncstop System Uid Pwd Svc [DBType]
where
System
The name of the System being synchronized.
Uid
The SSA userid defined for UST database.
Pwd
The password for the SSA userid defined for UST database.
Svc
The name of the UST database.
DBType
An optional database type of the UST database specified when the environment variable
SSA_DB_TYPE
is not set. Specify
ora
,
udb
,
myq
or
msq
.
The Update Synchronizer will shut down when the next duty cycle begins.
UDB/DB2: The Win32
syncstop
script must be run from a DB2 Command Window.
The
syncstop
script cannot be used to stop a Synchronizer that is processing transactions from the NSA table. The only supported mechanism in this case is to use the
Stop
button on the Console, or the
--rbcheck
switch.

Server Shutdown

Identity Resolution servers do not shut down if the clients are attached, unless you use the hard shutdown option.

0 COMMENTS

We’d like to hear from you!