História stránky

...

• Kotva
  trezorpathora trezorpathora

  TrezorPath - path to the directory, where the data files of tablespaces are created. You must also enter the character "\" after the directory name. If the parameter is not given, data files are created in the database directory.
• TrezorCompressPath - path to the directory, where the data files of released tablespaces are being moved. You must also enter the character "\" after the directory name. Once the TrezorCompressPath parameter is defined, you must also define TrezorPath; otherwise, data files are not to be moved.

• Kotva
  trezorperiodora trezorperiodora

  TrezorPeriod - the period of the depository creation. It is specified in the 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 an 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 this command may perform various maintenance tasks that could otherwise block the archive.

• Kotva
  trezorcompresstimeora trezorcompresstimeora

  TrezorCompressTime - time for releasing the 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), and 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 data files in the tablespace, by default, is 1 (the parameter is of DWORD type !!!).

• Kotva
  trezorstartdatafilesize trezorstartdatafilesize

  TrezorStartDatafileSize - the size of the data file 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 data files damaged at a size of 4GB - must be tested before use!

• Kotva
  trezormaxdatafilesize trezormaxdatafilesize

  TrezorMaxDatafileSize - maximum size of data file (in Oracle syntax, e.g., 500K, 300M or UNLIMITED). If it is not defined, the size of the data file is specified at its creation (see the note for the previous parameter).

• Kotva
  trezordatafilesizestep trezordatafilesizestep

  TrezorDatafileSizeStep - the size of data file 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 the data file. The default value of this parameter is ORA.

• Kotva
  trezorprefix trezorprefix

  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 migrating the 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 the 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 the archive to read also from the depository segment 0 when reading from any other depository segment. Reading from depository databases will be slower, but it enables reconfiguring historical values from the 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 the Create Time of the 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 possibly moving data files of the released depository database. The program may be used e.g., to pack data files and copy them via the network.
  Note: before running the command, the environment variables D2000_DBUSER and D2000_DBPASS are set to the name and password that D2000 Archive uses to access the archive database. These variables can be used in a script to connect to the archive database.

• 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 the 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 data files of the depository database (i.e., the value of the parameter TrezorCountDatafiles).
  • #FILE1#, #FILE2#, etc. - is replaced by the name of the corresponding data file 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: The configuration of depository databases with one data file 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 the 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).

...