/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).

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.

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.

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.

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.

Automatic archive synchronisation based on the information on times when archives were broken down. The times are stored in the destination archive (the table

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).

/ATE
/ATD
/ATA

Archived objects with enabled archiving (/ATE, default), disabled archiving (/ATD) or all (/ATA) will by synchronized. This parameter can be used for duplicating the whole archive database into a new database if copying of old archive objects with disabled archiving is desired. For these objects, the corresponding tables will be created in the target database if they didn't exist.

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).

/UX

Work with old (unupgraded) structures of tables in the archive database. This parameter enables to synchronize data from older D2000 applications (e.g. pre-UTF8 D2000 version 8.0) without need to upgrade the old archive database. This is convenient e.g. when preparing a migration to a new D2000 version using a different database platform for D2000 Archiv.

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 PostgreSQL archives to minimize transaction ID (XID) generation when used against a DSN with "Level of rollback on errors" set to Transaction.
Note: for PostgreSQL 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.

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 PostgreSQL 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 PostgreSQL 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.

Only primary archives will be synchronized (not the statistical and evaluated ones).

The parameter is only allowed if the Arcsynchro - Archive Synchronization Tool#id parameter (data synchronization of one object with a particular identifier) is specified.
In that case, values of the object with the Arcsynchro - Archive Synchronization Tool#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).

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.

DSN of source Sybase depository database.
The parameter can be used just once. By default, it also enables the parameter /TAD (i.e. only values of objects, the definitions of which are in target archive database, are to be read from the depository database).

Note: If the parameter /ST is used, the parameter source (source archive DSN) will be ignored.

Name of source PostgreSQL depository database. Usually in appname_TREZOR_n format, e.g. Test_TREZOR_11.
The parameter can be used just once. By default, it also enables the parameter /TAD (i.e. only values of objects, the definitions of which are in target archive database, are to be read from the depository database).

Note: If the parameter /STPG is used, the parameter source (source archive DSN) will be used to connect to the PostgreSQL depository database (in order not to create a separate DSN for each PostgreSQL depository). Therefore source must point to the same PostgreSQL server where the depository database is located.

DSN of destination depository database.
The parameter may be repeated several times for destination depository database on Sybase (e.g. for synchronisation of the current and previous depository database: /TT app.curr_trezor /TT app.prev_trezor).

Note: If the first database cannot be opened, the arcsynchro will be stopped with an error. Error in opening  of the second or another database is to be ignored (to allow standard use with current and previous depository databases, while the previous one cannot be available at all).

For target depository database on Oracle, the parameter may be used in case that depository databases and the archive database are not stored in the same place (use the parameter /TTO otherwise). The parameter can be used only once. The user name used for connecting the database is specified by the parameter target_user, the user name may be defined by the parameter /TTP trezor_password.

For source depository database on Oracle: data from depository database trezor_id will be synchronised. Parameter can be used for Oracle depository databases stored along with the archive in the same database. Parameter enables filling of target database, or depository databases (Oracle, PostgreSQL, Sybase) from Oracle depository database.
Examples:

• /STO 16 - synchronisation from depository database 16

• /STO 16_S01 - synchronisation from depository database 16, depository database segment No.1

Note: Data can be read only from mounted depository databases (current, previous and older depository databases mounted by the Tell command MOUNT_TREZOR).

For destination depository database on Oracle: the parameter enables synchronization of depository databases. This parameter can be used for depository databases stored along with the archive in the same database. If the depository databases are stored in different database, there must be used the parameter /TT trezor_dsn.
Note: Data can be written only to depository databases mounted for writing (current, previous and older depository databases mounted by the Tell command MOUNT_TREZOR WRITE).

/PTO

Synchronization of depository databases (exclusive of the archive) in the destination database. The parameter target will be ignored if the parameter /TT trezor_dsn is used and the parameter /TAD is not used.

/TTP trezor_password

Password for connection to the destination depository database.

Arcsynchro uses the definitions of historical objects from the destination database. Although the definitions of historical values from the destination database are used by default, the parameter is required in case that the number of depository database segments in the destination Oracle archive is different from the number in the destination archive and data for depository databases are synchronized as well.
Without the parameter, the archive either stores data in the depository database segment 02 (if the number of segments in the source archive is less than the number of segments in destination archive) or cannot find any segment to store the data in (if the number of segments in the source archive is greater than the number of segments in destination archive).

For destination depository database on PostgreSQL: the parameter enables synchronization of depository databases.
If only a single depository database segment is configured (TrezorCountSegments=0), only the parameter /TTPG0 mask0 has to be specified. Parameter mask0 has to be equal to the value of parameter PG_TrezorName0.
If several depository database segments are configured (TrezorCountSegments>0), also the parameter /TTPGN maskN has to be specified. Parameter maskN has to be equal to the value of parameter PG_TrezorName.
Note: Data can be written only to depository databases mounted for writing (current, previous and older depository databases mounted by the Tell command MOUNT_TREZOR WRITE).

For PostgreSQL depository database on PostgreSQL from version 9.5: data is not entered into the depository databases via ODBC, but a file is created in the path directory where the data will be in the text form. After inserting the number of rows that corresponds to the startup parameter /CM (default 1000 but recommended to increase to 1000000 if /FM is used), a foreign table mapped to this file is created via PostgreSQL extensions 'file_fdw', and the data is merged into the depository database (upsert).

This procedure bypasses slowness of ODBC, which processes rows one at a time. It is necessary for the path directory to be readable for the PostgreSQL database (i.e., arcsynchro must run on the same computer as the database).

By using the / FM parameter, data transfer has been accelerated approximately 3 times (from 2400 to 7050 rows per second) in a specific case.

Copies the contents of the table LOG_DATA.
The copying is necessary when adding a new instance of D2000 Archiv to the existing application or during migration to a new database (e.g. when migrating from lower to higher version of Sybase, or from Sybase to Oracle platform and vice-versa). Table LOG_DATA contains information about archive's transition to monotonic time and about the start of on-change archiving. If older data are to be copied to archive database (from older archive database), it is necessary to copy also the contents of LOG_DATA table and only afterwards to start archiving. Otherwise old data may be misinterpreted and possibly damaged during recalculations.
Copying of the contents of the table LOG_DATA must be performed before D2000 Archiv starts writing data to the new database. Recommended procedure is following:

1. Create the new archive database (Sybase or MSSQL platforms) or archive tablespace (Oracle platform).

2. Run D2000 Archiv with parameter /RO (read only). The tables for archived data will be created, but no values will be inserted.

3. Stop D2000 Archiv as soon as tables are created.

4. Run:
   arcsynchro /CLD source target,
   source is DSN of the old archive database with historical data,
   target is DSN of the new archive database with empty tables.

5. At this point it is possible to run D2000 Archiv (start of normal archiving to a new archive database).

6. Copy the historical data from the old database into the new database
   arcsynchro source target time_start time_end,

Note: the row 'STOP' saving the time of the last stop of D2000 Archiv will not be copied to target database.

/DD

Detailed debug information.
After the parameter is enabled, detailed debug information will be shown on the screen as well as written into the arcsynchro.log log file.

/DC count

Setting the parameter to non-zero value count will cause letters 'I' or 'U' shown on the screen as well as written into the arcsynchro.log log file after inserting or updating count values.

Note: Letters are displayed continuously on the screen but only after processing of one object in log file.

Commits in archive database will be activated after count inserted/updated values. Default value of this parameter is 1000.

Supplementary condition for the ArchivDef table (a table with definitions of archive objects in the archive).
Example of use: when using arcsynchro to copy data from depository segments (e.g. from an Oracle database) to depository segments (e.g. PostgreSQL database) it is possible to specify /XADC "TRZ_SEG=2". Only objects that are in depository segment no. 2 will be synchronized. This can speed up data copying (the source depository segment is not queried for object data that is in other depository segments).

0

Successful completion of synchronisation.

1

Error in program parameters.

2

Error connecting to source database specified by parameter Arcsynchro - Archive Synchronization Tool#source.

3

Error connecting to source depository database specified by parameter /ST.

4

Error connecting to target database specified by parameter Arcsynchro - Archive Synchronization Tool#target.

5

Error connecting to separate target depository database on Oracle platform specified by parameter /TT trezor_dsn.

6

Error connecting to first target depository database on Sybase platform specified by first parameter /TT trezor_dsn.

7

The conversion to time slices in Arcsynchro - Archive Synchronization Tool#source database was started but not finished.

8

The conversion to time slices in Arcsynchro - Archive Synchronization Tool#target database was started but not finished.

9

Target database is not on Oracle platform and parameter /TTO was used.

10

Error reading list of depositories from Arcsynchro - Archive Synchronization Tool#target database on Oracle platform using the parameter /TTO.

11

Error reading list of depositories from separate depository database /TT trezor_dsn on Oracle platform using also the parameter /TTO.

12

Error reading parameters of source depository database specified by parameter /ST.

13

Error during data synchronisation (e.g. broken connection to database).