História stránky

...

• 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 parameter TrezorCompressPath is defined, you must also define TrezorPath, otherwise datafiles not to be moved.

• Kotva
  trezorperiodora trezorperiodora

  TrezorPeriod - 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 compressed depository database will be put into offline mode. Value 0 means that 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 archiv.

• 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. Default value is 0 (only one segment 0 is being created), maximum value is 99 (segments 0 to 99 are being created). The parameter is of DWORD type !!!.

• Kotva
  trezorcountdatafiles trezorcountdatafiles

  TrezorCountDatafiles - number of datafiles in 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 before!

• Kotva
  trezormaxdatafilesize trezormaxdatafilesize

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

• Kotva
  trezordatafilesizestep trezordatafilesizestep

  TrezorDatafileSizeStep - size of datafile increment (in Oracle syntax, e.g. 200K, 1M) during 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. Default value of this parameter is ORA.

• Kotva
  trezorprefix trezorprefix

  TrezorPrefix - if this parameter is not set, prefix of trezor tablespaces and datafiles is APPLICATION_TS_TREZOR.
  Setting the value of TrezorPrefix changes this prefix. Parameter can be used together with parameter DbUsername when doing a migration of archive database from one application to another (or when renaming an application) and keeping the archive tablespace and existing trezors (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!". Default value is 120 seconds.

• Kotva
  trezorreadsegment0 trezorreadsegment0

  TrezorReadSegment0 - Parameter has a meaning only if depository segment 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 to reconfigure historical values from default depository segment 0 to a different segment while keeping access to data previously stored in depository segment 0.
  The parameter TrezorReadSegment0 can be changed by TELL command SET_OPTION .

• Kotva
  trezorpostcompresscmdora trezorpostcompresscmdora

  TrezorPostCompressCmd - name of a program to be run after releasing 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 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 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, there is run the program:
  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).

...