...
Depository database is implemented as an independent tablespace named APPLICATION_TS_TREZORID, where ID=1,2.. etc (e.g. TEST_TS_TREZOR5). The tablespace contains datafiles - their number is defined by the parameter TrezorCountDatafiles (1, by default). Datafiles are generated in the TrezorPath directory.
If TrezorCountDatafiles=1, the datafile name is APPLICATION_TS_TREZORxxID_YYYYMMDD.ORA.
If TrezorCountDatafiles>1, the datafile names are APPLICATION_TS_TREZORxxID_01_YYYYMMDD.ORA, APPLICATION_TS_TREZORxxID_02_YYYYMMDD.ORA etc, where xxID is ID enhanced from the left with a zero to the length of 4 characters and YYYYMMDD is the depository database creation date, e.g. TEST_TS_TREZOR0005_03_20060930.ORA. Datafile size is specified by the parameter TrezorStartDatafileSize, the parameter TrezorMaxDatafileSize allows specifying the maximum datafile size.
...
Note 3: Oracle database can contain as many datafiles as defined by the parameter DB_FILES in the initialisation initialization file of the database. Therefore, set up the value of the parameter to sufficient value before creating depository databases is enabled.
...
Since the 7.01.10 version, the process D2000 Archiv supports the concept of depository database segments on the Oracle platform. Depository database segments is a depository database tablespace, several of which can be created and filled in parallel. Each historical value is stored in one segment, the number of which is specified by the parameter Depository segment in the historical value configuration.
...
The main purpose of depository database segments is the creation of several smaller depository databases so that reading of one historical value for a long time interval requires less disk space (because only specific segments containing that historical value need to be mounted) - compared to mounting all non-segmented depository databases for a required time interval.
Having depository database segments enabled, the name of zero segment tablespace is APPLICATION_TS_TREZORID (identical with the name of the depository database tablespace if segments are disabled) and the names of all another other segments are APPLICATION_TS_TREZORID_seg, where seg is a double-digit number of segment (between 01 and TrezorCountSegments).
If TrezorCountDatafiles=1, the names of datafiles are APPLICATION_TS_TREZORxxID_Syy_YYYYMMDD.ORA
If TrezorCountDatafiles>1, the names of datafiles are APPLICATION_TS_TREZORxxID_Syy_zz_YYYYMMDD.ORA, where xxID is ID enhanced from the left with zero to the length of 4 characters, yy is the segment number enhanced from the left with a zero to the length of 2 characters, z is the datafile number enhanced from the left with a zero to the length of 2 characters and YYYYMMDD is the depository database creation time. Example: TEST_TS_TREZOR0005_S02_01_20060930.ORA
...
All the configuration parameters in the Windows Registry are of String type, beside besides the parameters TrezorCountDatafiles, TrezorCountSegments, TrezorCountDatafiles, and TrezorNoLogging of DWORD type.
| Kotva |
|---|
| trezorpathora |
|---|
| trezorpathora |
|---|
|
TrezorPath - path to the directory, the datafiles of tablespaces are created in. You must also enter the character "\" after the directory name. If the parameter is not given, datafiles are created in the database directory.- TrezorCompressPath - path to the directory, the datafiles of tablespaces released are being moved to. You must also enter the character "\" after the directory name. Once the TrezorCompressPath parameter is defined, you must also define TrezorPath, otherwise datafiles not to be moved.
| Kotva |
|---|
| trezorperiodora |
|---|
| trezorperiodora |
|---|
|
TrezorPeriod - the period of the depository creation. It is specified in format NX, where N is an integer number and X defines a time unit.
Permitted time units are:- H - hour
- D - day
- W - week
- M - month.
Note: Setting the parameter either to empty value or to 0H disables the functionality of depository databases.
| Kotva |
|---|
| trezorcompressofflineora |
|---|
| trezorcompressofflineora |
|---|
|
TrezorCompressOffline - value 1 (default) means that the compressed depository database will be put into offline mode. Value 0 means that the depository database remains in read-only mode and data will be available for reading. Value 2 means that D2000 Archiv will not access the depository database while TrezorPostCompressCmd is running, so that this command may perform various maintenance tasks which could otherwise block the archive.| Kotva |
|---|
| trezorcompresstimeora |
|---|
| trezorcompresstimeora |
|---|
|
TrezorCompressTime - time for releasing depository tablespace. The tablespace is available for writing delayed data during this period. TrezorCompressTime must be less than TrezorPeriod.| Kotva |
|---|
| trezorcountsegments |
|---|
| trezorcountsegments |
|---|
|
TrezorCountSegments - number of depository database segments (depository database tablespaces), that are being created in parallel. The default value is 0 (only one segment 0 is being created), the maximum value is 99 (segments 0 to 99 are being created). The parameter is of DWORD type !!!.| Kotva |
|---|
| trezorcountdatafiles |
|---|
| trezorcountdatafiles |
|---|
|
TrezorCountDatafiles - the number of datafiles in the tablespace, by default, is 1 (the parameter is of DWORD type !!!).| Kotva |
|---|
| trezorstartdatafilesize |
|---|
| trezorstartdatafilesize |
|---|
|
TrezorStartDatafileSize - size of datafile that is to be created (in Oracle syntax, e.g. 500K, 300M). The parameter must be specified.
Note: For OpenVMS+Oracle 9.2.0.x platform, there is a problem with datafiles damaged at the size of 4GB - must be tested prior to using!| Kotva |
|---|
| trezormaxdatafilesize |
|---|
| trezormaxdatafilesize |
|---|
|
TrezorMaxDatafileSize - maximum size of datafile (in Oracle syntax, e.g. 500K, 300M or UNLIMITED). If it is not defined, the size of datafile is specified at its creation (see the note for the previous parameter).| Kotva |
|---|
| trezordatafilesizestep |
|---|
| trezordatafilesizestep |
|---|
|
TrezorDatafileSizeStep - the size of datafile increment (in Oracle syntax, e.g. 200K, 1M) during the growth of the datafile (ON NEXT clause of the CREATE TABLESPACE command). If the parameter is not defined, the ON NEXT clause is not used and the increment is the database default value (8K, by default).| Kotva |
|---|
| trezordatafilesuffix |
|---|
| trezordatafilesuffix |
|---|
|
TrezorDatafileSuffix - suffix of datafile. The default value of this parameter is ORA.- TrezorPrefix - if this parameter is not set, the prefix of depository tablespaces and datafiles is APPLICATION_TS_TREZOR.
Setting the value of TrezorPrefix changes this prefix. The parameter can be used together with the DbUsername parameter when doing a migration of archive database from one application to another (or when renaming an application) and keeping the archive tablespace and existing depositories (i.e. setting the value of TrezorPrefix to OldApp_TS_TREZOR). - TrezorReadOnlyTimeout - specifies the timeout (in seconds) for switching depository database into READ ONLY mode. After expiration, the archive generates the system alarm "Changing trezor tablespace read-only takes more than 120 sec, possible Oracle lock!". The default value is 120 seconds.
| Kotva |
|---|
| trezorreadsegment0 |
|---|
| trezorreadsegment0 |
|---|
|
TrezorReadSegment0 - Parameter has a meaning only if depository segments are configured (non-zero value of TrezorCountSegments parameter). Activation of a parameter (value 1) instructs archive to read also from depository segment 0 when reading from any other depository segment. Reading from depository databases will be slower, but it enables reconfiguring historical values from default depository segment 0 to a different segment while keeping access to data previously stored in depository segment 0.
The TrezorReadSegment0 parameter can be changed by the SET_OPTION TELL command.| Kotva |
|---|
| trezorreadsincecreate |
|---|
| trezorreadsincecreate |
|---|
|
TrezorReadSinceCreate - value 1 means that depositories that are older than Create Time of historical value will not be read. The TrezorReadSinceCreate parameter can be changed by the SET_OPTION TELL command.| Kotva |
|---|
| trezorpostcompresscmdora |
|---|
| trezorpostcompresscmdora |
|---|
|
TrezorPostCompressCmd - the name of a program to be run after releasing the depository database and possible moving of datafiles of the depository database released. The program may be used e.g. to pack datafiles and copy them within the network.| Kotva |
|---|
| trezorpostcompressparora |
|---|
| trezorpostcompressparora |
|---|
|
TrezorPostCompressPar - optional parameter, used for the program specified by the parameter TrezorPostCompressCmd. It can contain optional text and predefined macros to be replaced before running the program:- #ID# - is replaced by depository database Id (e.g. 15).
- #TREZOR# - is replaced by the depository tablespace name (e.g. TEST_TS_TREZOR5).
- #SEGMENTS# - is replaced by the number of depository database segments (i.e. the value of the parameter TrezorCountSegments).
- #FILES# - is replaced by the number of datafiles of depository database (i.e. value of the parameter TrezorCountDatafiles).
- #FILE1#, #FILE2#, etc. - is replaced by the name of the corresponding datafile along with the path, if the path is defined by the parameter TrezorPath (e.g. C:\ora920\oradata\D2000\TEST_TS_TREZOR5_1.ORA).
Example 1: There is enabled the creating of depository databases with one datafile to be packed into the file TrezorID.zip (ID=1,2 etc.) and moved to the directory D:\backup
TrezorCountDatafiles 1
TrezorPostCompressCmd C:\utils\zip.exe
TrezorPostCompressPar -m D:\backup\Trezor#ID#.zip #FILE1#
After releasing for example the depository database nr. 5, a program can be run:
C:\utils\zip.exe -m D:\backup\Trezor5.zip C:\ora920\oradata\D2000\TEST_TS_TREZOR5_1.ORA
Example 2: Configuration, which will remount (using TELL command) the depository tablespace immediately after it is released by:
TrezorPostCompressCmd c:\D2000\D2000.E70\bin\tell.exe
TrezorPostCompressPar dst=SELF.ARC cmd="MOUNT_TREZOR #ID#" uid=myuser pwd=mypassword- TrezorNoLogging - the parameter of DWORD type, its non-zero value causes the depository tablespace to be created in the NOLOGGING mode. If its value is zero or doesn't exist, the depository tablespace is to be created in the LOGGING mode (it generates REDO logs and is restorable).
...
| Kotva |
|---|
| trezor_outside |
|---|
| trezor_outside |
|---|
|
Oracle-based archives support creating the depository databases in a different database than the archive is in.
The TNS of the depository database is defined by the configuration parameter
| Kotva |
|---|
| tns_service_name_trezor |
|---|
| tns_service_name_trezor |
|---|
|
TNS_Service_Name_Trezor. The user name and password are the same as in the archive database.
Parameter
TNS_Service_Name_Trezor is located in the registry in a branch belonging to the application and archive, e.g. HKEY_LOCAL_MACHINE\Software\Ipesoft\D2000V70\cfg_test\SELF.ARC
Database, in which the depository will be created, must contain the archive tablespace (created in the same way as if
the archive was supposed to be located in this database) and appropriate archive user
application_name_archiv, e.g. test_archiv.
...
Oracle-based archives support the configuration where two or more shadow archives work with a common depository database. Only an active instance of archive uses the depository database. The common depository database is defined by the setting of configuration parameter
| Kotva |
|---|
| trezor_active_only |
|---|
| trezor_active_only |
|---|
|
Trezor_Active_Only (of REG_DWORD type) to a non-zero value. This parameter is located in the registry in a branch belonging to the application and archive. As the archives are shadow archives,
the branch of the archive contains also instance number, generally HKEY_LOCAL_MACHINE\Software\Ipesoft\D2000V70\cfg_
APPLICATION_NAME\
ARCHIVE_NAME.ARC_
INSTANCE_NUMBER, e.g. HKEY_LOCAL_MACHINE\Software\Ipesoft\D2000V70\cfg_test\SELF.ARC_2\)
...
| Kotva |
|---|
| trezory_pre_pgsql |
|---|
| trezory_pre_pgsql |
|---|
|
Depository databases on the PostgreSQL platform
...
Depository A depository database is implemented as an independent database. Names of depository databases are defined by configuration parameter PG_TrezorName0.
Similarly to Sybase, the configuration of the process D2000 Archiv contains a configured time period TrezorPeriod, during which the process writes data to one depository database. When this period elapses, the database is released and the process starts storing values into a new database. The released database is available for storing delayed data for a given time (configuration parameter TrezorCompressTime). After expiration of this time, a default read-only access is configured for the database (ALTER DATABASE APLIKACIA_TREZOR_#ID# SET default_transaction_read_only = true) and then if value of parameter TrezorCompressOffline=1, access to depository database is forbidden (update pg_database set datallowconn = false where datname = 'APLIKACIA_TREZOR_#ID#'). After disconnecting a depository database, it is possible to run an external program - its name and path to it is defined by the parameter TrezorPostCompressCmd and its parameters are defined by the parameter TrezorPostCompressPar.
This program can for example move and compress a disconnected depository database or create a dump of read-only depository database via PostgreSQL utility pg_dump.
Note 1: In order for a database user dba (used by D2000 Archiv to connect to PostgreSQL server), to create and disconnect the databases, it is recommended to grant the dba user a superuser privilege ( ALTER ROLE dba WITH SUPERUSER; ).
Note 2: As every depository database (resp. every depository database segment) is a separate database, which is accessed by D2000 Archiv via a separate database connection, it is necessary to configure the PostgreSQL server to permit a sufficient number of connections (parameter max_connections), for D2000 Archiv to open a connection to all mounted depository databases.
| Kotva |
|---|
| trezorovy_segmentpg |
|---|
| trezorovy_segmentpg |
|---|
|
Depository database segments
Depository database on the PostgreSQL platform supports also depository database segments (similarly to Oracle platform). Depository The depository database segment is a separate depository database, several of which can be created and filled in parallel. Each historical value is stored in one segment, the number of which is specified by the parameter Depository segment in the historical value configuration.
...
The number of segments created by the process D2000 Archiv is specified by the parameter TrezorCountSegments in the Windows registry. Historical values with the parameter depository segment higher than the value of the parameter TrezorCountSegments are to be stored in zero depository segment (it is the segment that is also created when depository database segments are disabled).
Name of the database representing depository segment 0 is specified by configuration parameter PG_TrezorName0, names of databases representing depository segments 1..N are specified by configuration parameter PG_TrezorName.
...
| Kotva |
|---|
| pg_createtrezor |
|---|
| pg_createtrezor |
|---|
|
PG_CreateTrezor - SQL command for creating a depository database. Default value is
CREATE DATABASE "#TREZOR#" WITH ENCODING='UTF8' OWNER=dba TABLESPACE="D2000" TEMPLATE=template0
where #TREZOR# is a name of depository database (defined by configuration parameter PG_TrezorName0 resp. for depository database segments 1..N by parameter PG_TrezorName). By default existence of tablespace named D2000 and template database template0 is required in PostgreSQL database server.| Kotva |
|---|
| pg_trezorfilemulti |
|---|
| pg_trezorfilemulti |
|---|
|
PG_TrezorFileMulti - parameter is active if also the PG_TrezorFilePath parameter is specified. The parameter defines a multiplicator for the CommitCount parameter. The default value of this parameter is 10.| Kotva |
|---|
| pg_trezorfilepath |
|---|
| pg_trezorfilepath |
|---|
|
PG_TrezorFilePath - parameter can be used for PostgreSQL 9.5 and above. It activates writing to depository databases via files, which is 2 to 3-times faster than the standard batch insert via the ODBC interface. After PG_TrezorFileMulti * CommitCount values are accumulated, they are stored into a file named archiv_<TrezorId>_<SegmentId>.txt (e.g. archiv_4_1.txt) in directory PG_TrezorFilePath and an UPSERT into a depository database is performed, using a foreign table mapped onto this file (using PostgreSQL extension file_fdw) as a source of data.
The directory PG_TrezorFilePath must be available both for reading and writing to archive as well as to the PostgreSQL database, therefore this parameter can be used if both archive and database are on the same computer.
| Kotva |
|---|
| pg_trezorname0 |
|---|
| pg_trezorname0 |
|---|
|
PG_TrezorName0 - mask for the name of created depository databases. If depository database segments are enabled, this mask will be used for segment 0. The default value is appname_TREZOR_#ID#, where appname is the application's name and #ID# is replaced by the depository database number.
E.g. for the application named Test, depository databases Test_TREZOR_1, Test_TREZOR_2, Test_TREZOR_3, etc will be created.
Specified The specified mask must contain text #ID#.
Note: If the default value is not acceptable, the custom desired value must be configured before enabling depository databases. Should the value of this parameter be changed after some depository databases have been created, it is necessary to rename all existing depository databases according to the newly specified mask.| Kotva |
|---|
| pg_trezorname |
|---|
| pg_trezorname |
|---|
|
PG_TrezorName - mask for the name of created databases - depository database segments 1..N.
Parameter is used only when TrezorCountSegments > 0. The default value is je appname_TREZOR_#ID#_#SEG#, where appname is the application's name, #ID# is replaced by the depository database number and #SEG# is replaced by the segment number.
E.g. for an application named Test with a number of segments equal to 1, databases Test_TREZOR_1, Test_TREZOR_1_1, Test_TREZOR_2, Test_TREZOR_2_2, Test_TREZOR_3, Test_TREZOR_3_1, etc will be created.
The specified mask must contain text #ID# and #SEG#.
Note: If the default value is not acceptable, the custom desired value must be configured before enabling depository databases. Should the value of this parameter be changed after some depository databases have been created, it is necessary to rename all existing depository databases according to the newly specified mask.| Kotva |
|---|
| trezorperiodpg |
|---|
| trezorperiodpg |
|---|
|
TrezorPeriod - the period of the depository creation. It is specified in format NX, where N is an integer number and X defines a time unit.
Permitted time units are:- H - hour
- D - day
- W - week
- M - month.
Note: Setting the parameter either to empty value or to 0H disables the functionality of depository databases.
...