Ansicht
Dokumentation

V_ARC_USR - Object-Dependent Settings

Data is pulled from archiving object-specific Customizing for controlling the sessions.

In many cases, the default values can be used; make sure you check this.

• Size of the archive file
  Make sure the size of the file is set to be able to control the number of archive files generated (together with the maximum number of objects per archive file). Choose a size that ensures good read performance, but is not too big thus increasing administration requirements. The size should usually be between 20 and 100 MB.

• Commit counter for the delete program
  A very small value (such as 1) usually makes sense in most cases. A value greater than 10, on the other hand, does not.
  The commit counter is the number of data objects deleted in one LUW, not the number of table entries. One data object almost always contains more than one table entry.

• Indicator for automatically starting delete programs
  This indicator is of interest when you want to back up the archive files before the delete program runs. For security reasons, it makes sense to have two copies of the archive files before the data is deleted from the database.
  However, this increases the interval between the writing of the archive and the deletion of data from the database. This increases the chance that the data might be changed before it is deleted. This means the data in the archive may not be the latest version from the database. Changes to the data between the write and delete sessions should be prevented by organizational measures.

• Variants for the delete program
  On the scheduling screen of archive management you can choose the option "Test session". You must specify two variants; one for the test session and one for the actual session. These are used by transaction SARA to select the correct session when scheduling the jobs.
  Make sure the set variants actually exist. If the production session variant does not exist, data will most likely not be deleted from the database when the production delete session is started.

For more information, see Application help.