/SU source_user |
User name for source (required if it is
other than standard). |
/SP source_password |
User password for
source (required if it is other than standard). |
/TU target_user |
User name for
target (required if it is other than standard). |
/TP target_password |
User password for target (required
if it is other than standard). |
source |
TNS (if source is an Oracle database) or
DSN (if source is a database that is available through ODBC
configured) of an archive containing valid archive records. |
target |
TNS or DSN of archive with
missing records. |
time_start |
Beginning of the time interval
for completing missing archive records. |
time_end |
End of the time interval for
completing missing archive records. |
id |
Historical value identifier (number).
If id=113, then corresponding archive table is DT0000113 (names of
archive tables which are being processed are being listed when the
program runs). |
+id -id +id -id |
Historical value identifier (number), from which (+id), upto which (-id) or for which interval (+id -id) the synchronization will be performed.
If e.g. +113 is specified, then historical values with HOBJ=113 and higher will be synchronized (tables DT0000113, DT0000114 etc).
An interval can be specified using +id -id, e.g. +1 -999 will synchronize the historical values with HOBJ between 1 and 999.
Note: This parameter can be use to parallelize the synchronization of archives (e.g. when loading data to a new archiv). Several
arcsynchro processes can be run in parallel. The first arcsynchro uses parameters +1 -999, the second +1000 -1999 etc. To separate the log files of multiple
arcsynchro processes, we recommend using also the parameter LOGDT.
|
mask |
Mask for the archive variable name. The
mask can contain special characters (? or *) which
allow to synchronize selected variables. Mask is not case sensitive.
Example: The variables H11_Edo, H11re, h111Element matches the mask H11?E*.
The variables H11abEdo, H11Edo, H12_edo doesn't match the mask. |
/A |
Automatic archive synchronisation based on
the information on times when archives were broken down. The times
are stored in the destination archive (the table ARC_HOLE, since the
version D2000 v7.00.031). When starting, the archive
generates new log into the table ARC_HOLE and periodically writes
into it. The structure of the table ARC_HOLE is as follows:
Column |
Description |
Id |
Row identifier. |
From_time |
Beginning of archive hole (blank space). |
To_time |
End of archive hole. |
Status |
Hole status:
- 0 - current hole (From_time is still increasing)
- 10 - holes in archive as well as depository database (if creating depository databases is enabled) that need to be synchronised
- 15 - hole in archive needs to be synchronized, hole closed in depository database (non-standard status)
- 20 - hole closed in archive, depository database has not been synchronized
- 25 - holes closed in archive as well depository database
- 30 - hole, that has been closed, but no values were inserted at synchronization
- -1 - blocked hole (will not be synchronised)
|
If both the archive and depository database are synchronized, the synchronisation is to be performed for the holes with Status=10.
If the archive is only synchronized, the synchronisation is to be performed for the holes with Status=15.
If depository database is only synchronized, the synchronisation is to be performed for the holes with Status=20.
After the synchronisation has been finished successfully (if there is no hole in the source archive that
contains the hole of the destination archive and if there is inserted at least one record during synchronisation), there
will be set:
- Status=15 - there was synchronized depository database only
- Status=20 - there was synchronized the archive only
- Status=25 - both the archive and depository database were synchronized
If no record was inserted, there will be set Status=30 - then the arcsynchro will not attempt to synchronise the same hole again.
|
/AN |
The same functionality as /A, but actual patching is not performed - arcsynchro exits after displaying the list of holes that
need to be synchronized. This parameter enables to find out the number and sizes of holes that need to be synchronized. |
/AX |
The same functionality as /A but value of Status in ARC_HOLE table is not changed after the hole had been patched.
Note: This parameter can be used for patching redundant archives with 3 or more instances. When patching
the hole in
database1 using database2 and database3, two arcsynchro would be activated:
arcsynchro /AX database2 database1
arcsynchro /NU /A database3 database1
First line patches the hole in database1 with data from database2 but keeps the hole marked as
desynchronized.
Second line patches (only inserts, does not update) the hole in database1 with data from database3 and marks the hole as patched.
Usually only one arcsynchro command is needed. Two arcsynchro can handle the situation when also database2 and database3 contain
incomplete data (i.e. archives [2] and [3] were down for some period during the longer time interval while archive [1] was down).
|
/A+ |
For every Historical value the whole history depth will be synchronised (as configured on the object)
up to the present time. This parameter can be used for duplicating the whole archive database into a new database.
Normally this parameter can be replaced by suitably chosen time_start and time_end parameters
(time_start must be sufficiently far in the past to cover maximum configured history depth),
but if the source archive is configured not to delete old values, this would mean that also old values would be synchronized.
Note: Configuration of history depth is queried from source or target database (see the description of /TAD parameter).
|
/TD time_delta |
Size of the hole surroundings in the archive that is to be synchronised.
When writing into the archive, communication can send values with the older or latter timestamp than is the current time. After
breakdown of the archiving process, there are missing latter and older data surrounding the hole. Therefore, it is possible to define
the size of the hole surrounding using the parameter time_delta
(in seconds), that is to be synchronised. Default value time_delta= 10. |
/NU |
If the target archive database already contains the value with timestamp being inserted (therefore insert fails)
the value will not be updated. This parameter is meant to speed-up the synchronisation if the target archive database
contains only holes and not data with different values than the source database.
|
/U |
Updates the tables structures in the archive
database. If at least one of the tables in the archive database is not actual (e.g. ARCHIV_DEF, ARC_HOLE, UTC_OFFSET
tables), the Arcsynchro utility runs without the parameter /U is to be terminated with an error message. The Arcsynchro utility runs with the parameter updates the structures of the tables
in the archive database (it may cause some problems if the new Arcsynchro utility is used for patching holes in an older
application that could not work with the archive database upgraded by using this parameter). |
/UF |
Arcsynchro first attempts to update the value. If no row is modified as a result of update, then insert is performed.
Parameter is implemented only for ODBC version.
Note: parameter can be used for PgSql archives to minimize transaction ID (XID) generation when used against a DSN with "Level of rollback on errors" set to Transaction.
Note: for PgSql starting with version 9.5 it is possible to use parameter /UP to minimize XID generation.
Note: identical functionality in archive is activated by archive parameter SelectBeforeUI.
|
/UP |
Parameter activates usage of SQL command "UPSERT" (combination of Insert and Update SQL commands), which is supported by PostgreSql database starting with version 9.5.
In this case insertion of values into archive and depository databases will be performed by command INSERT .. ON CONFLICT .. DO UPDATE.
Parameter is implemented only for ODBC version.
Note: parameter can be used for PgSql archives to minimize transaction ID (XID) generation when used against a DSN with "Level of rollback on errors" set to Transaction.
Note: for versions of PgSql older than 9.5 it is possible to use parameter /UF to minimize XID generation.
Note: identical functionality in archive is activated by archive parameter Upsert.
|
/PO |
Only primary archives will be synchronized (not the statistical and evaluated
ones). |
/TID tid |
The parameter is only allowed if the id parameter (data synchronization of one object with a particular identifier) is specified.
In that case, values of the object with the id identifier read from the source database are inserted into the target archive database into the tables of the object with identifier tid.
If the data in the depository databases is synchronized, the identifier of the id object will be replaced by the tid identifier when data is inserted into the target depository databases.
Note: The /TID parameter is useful when merging applications and their archives if there is a change in HOBJ of objects (the object ID in the source application and the source archive is different from the target application/archive).
|
/LOGDT |
Instead of using use the default log file name arcsynchro.log arcsynchro will create a log file with a timestamp in its name arcsynchro yyyy-mm-dd hh-mi-ss.log.
For a reason to use this parameter please see this note.
|