(SP35) Settings parameters

AUTHORIZATION 

This parameter determines if OutBoard Authorization is switched ON (value X) / OFF (value ' ').

BG_JOB_DIRECT_START

This parameter determines if Background jobs in OutBoard are started "With converting to Time – Based Jobs" (value 'X')/ "Without converting to Time – Based Jobs" (no value). When a job is started "Without converting to time-based jobs", this job is scheduled and started normally when any background job is free. When selecting "With converting to Time – Based Jobs", the job will be started immediately if any background job is free. If there are no free background jobs it will try to execute the job every ten seconds for 30 minutes.

CHECK_PACKAGE_SIZE 

This parameter checks the maximum size of each data package during archiving to avoid possible problems with the future reload of archived data, a load of archived data to other InfoProviders, or performance problems during reporting on archived data in SP19. This parameter can negatively impact the archiving performance in the copy phase when there are many characteristics used as semantic groups in the Data archiving process. To disable this check, change the value of this parameter to an empty value.

CREATE_PARTITIONING

DISPLAY_COMP_RATIO_TYPE

This parameter determines the way of computing the saved storage by archiving. Two possible settings are possible:LOCAL_ONLY: when the saved storage is calculated, the ratio for calculating the saved storage in external storages is set to 100%. For data archived in the online database, the compression ratio was determined during archiving. When the saved storage is calculated, the compression ratio used for calculation is taken and is determined during archiving. In case the parameter is changed, the statistics need to be recalculated with the report /dvd/nls_upd_clu_ratio_size.

DUMMY_VARIANT_DATE

Bottom range date limit used for generated data archiving process variants. Possible values: date >= 19010101 (YYYYMMDD) Note: If a fiscal variant is year-dependent, the value of this setting has to be inside the defined range of years for that variant, otherwise the date will not be translated.

FILTERING_TYPE 

Determines the way, how is the archived data filtered when accessed. Can be based on RANGE or SETS. Possible values: RANGE, SETS.

HNA_UNLOAD_PRIO 

Determines the Unload Priority of Outboard tables for SAP BW running on SAP HANA. It can be 0 ~ 9, where 0 means not-unloadable and 9 means the earliest unload.

LOAD_MAX_GRAN 

Determines the maximum number of packages that can be processed at once in the loading via a Data Transfer Process (DTP). Possible values:  integer > 0 e.g. 10, 20, 50.

LOAD_USE_ADD_SORTING

When enabled, data loaded from archived WODS is sorted in the same order in which it was loaded. This applies when the setting has the value ‘X’, L mode is used, source WODS is archived. Setting may be switched ON (value X) / OFF (value ‘ ’).

LOAD_PAR_RET 

Maximum number of finished processes during parallel DTP load. Possible values:  integer > 0 e.g. 10, 20, 50.

LOAD_PAR_WP

Determines how many parallel jobs will be used for reading from the archive when loading from the archive via DTP.  Possible values:  integer >= 0 e.g. 0, 4, 15.

NAV_ATTR_BUFFER 

Size of the buffering table when the Navigation attribute support is switched on. Possible values:  integer > 0 e.g. 10, 20, 50.

0

Defines the filtering order/ priority when the Navigation attribute support is switched on. Value 0 means that filtering on the Navigation attribute is done at first then the filtering on other attributes is done. Value 1 represents the opposite scenario.

NAV_ATTR_SELECTION 

This parameter is for turning the navigation attribute support functionality: on (1) or off (" "). This setting can be edited on the InfoProvider level. It is recommended to turn this parameter off for SybaseIQ archiving storage. This is due to the fact that needed filtering is done on the database level and there is no need to use the standard Outboard navigational functionality in this case.

NLS_STATISTICS 

This parameter determines if OutBoard Statistics is switched ON (value X) / OFF (value ' ').

REBUILD_AGGREGATE

REP_PAR_WP 

This value determines how many work processes are used for reading when data from OutBoard is requested for reporting. Possible values:  integer > 0 e.g. 10, 20, 50
Note: For an IQ transparent storage, the parameter for REP_PAR_WP cannot be set to higher than 1.

SIZE_DIFF_THRESHOLD 

If using a size-dependent OutBoard license, after reaching this value of free space, the user will get a warning message from each archiving process or creation of DAP.

SIZE_TO_MONEY_COEFF 

SIZE_UNIT 

STORAGE_UPDATE_PACK_LOG_SECS 

UPDATE_SIZE_STATISTICS

This parameter determines if the object size statistics are updated while archiving or reloading data. In the case of substantial archiving requests, recalculation has a noticeable performance impact. This setting may be switched ON (value X) / OFF (value ‘ ’).

USE_DATA_CLASS_BADI

Determines if BAdI will be used to define DATA_CLASS. If the value is 'X', the parameter DATA_CLASS cannot be edited in Settings for a given InfoProvider. (The default value can still be changed.) If the BAdI is used, the implementation for BAdI /DVD/NLS_DETERMINE_DATACLASS has to be created. Parameters of BAdI: iv_dapname – Technical Name of InfoProvider ev_data_class – Data class in technical settings. The output format of the BAdI implementing class method GET_DATA_CLASS should be of type TABART.

USE_PART_KEY_BADI 

USE_DV1_NAMESPACE 

VP_SUPP_NAV_ATTR_IN_LOC_FILT

In case the local filters are defined on navigational attributes, some tuning can be done by setting the parameter to a specific value:
      S (recommended): support filtering on navigational attributes in the local filters
      N: local filters will be removed/cleared from the filtering completely
      R: only local filters parts connected to navigational attributes will be removed

This setting initializes secondary indexes on all key fields of an ADSO during a DAP creation. This setting is supported only for Writer, for ADSO delta calculation type ("DSO like").

WRITER_AUTO_RELOAD_EMPTY_REQ

Enables the automatic reload functionality. At the beginning of a DTP load to cube / DSO activation, empty archiving requests are reloaded. Data, therefore, stays in the active table, in the post-processing, new archiving requests are created with the same archiving condition. Possible values: ON (value X) / OFF (value ' ') .

FILTERING_EXCLUDE_NAV_ATTR

At query runtime split filter ranges into those with navigation attributes and without nav. attrs. And filters on database only with filters without nav. attrs. (additional filtering on navigation attributes  on the app. server) .

FILTERING_HUGE_SEL

Max value of the number of conditions. When exceeded filtering on the application server is used (internal table instead where condition on storage).

HUGE_SEL_FAE_FOR_SEL_OPT

Max value for all entry lines. When exceeded filtering on the application server is used (unfiltered data are selected into an internal table, additional filtering on application server instead of the complex one where the condition sent into database needs to be processed).

INDEX_PAR_BUILD

INDEX_SEC_BUILD

Determines, if OutBoard secondary indexes will be built during archiving of new data values: 'X' - Build , ' ' - Do not build , 'P' - Build partially.

INDEX_SEC_DEFAULT_STORAGE

Identifies, which SM storage should be used as a default for OutBoard SI creation. (SPACE = primary database).

INDEX_SEC_FILTERING_ON_POS

Determines, if OutBoard Secondary Indexes will be used for filtering based on the position of entries in the NLS archive on row level. Values 'X' - use , ' ' - do not.

INDEX_SEC_HINT_BLOCK_FACTOR

Determines, which value is used for "ORACLE" hint factors (for parameters visible in TA rz11 rsdb/max_in_blocking_factor and rsdb/max_blocking_factor) (values: empty/integer).

INDEX_SEC_READ_PACKAGE_SIZE

Determines, how often the /SEC/ table will be accessed during Secondary Indexes creation, the higher package size, the less often the /sec/table is accessed.

INDEX_SEC_SEARCH_MAPPING_TAB

Determines, if the extended logic for OutBoard Secondary Indexes usage will be used in archiving verify phase. 

INDEX_SEC_SEARCH_REGEX

Identifiers the string to be used for the extended OutBoard Secondary Indexes usage logic (values: custom string/empty).

INDEX_SEC_USE_FOR_FILTERING

Determines, if Secondary Indexes will be used for filtering based on the position of entries in the NLS archive on the package level. X = on / ' ' = OFF

LOOKUP_FAE_FILTER

LOOKUP_FAE_FILTER_REC

Maximum number of records with EQ sign in For All Entries table, if there are more, interval (Between) is used. Possible values - integer number

LOOKUP_FAE_OPTIMIZATION

Use hashed For all entries table to filter the data - faster performance, the recommendation is to have it turned on. Possible values -  X/' '.

MASS_ARCH_VAR_PREV_STAT_CHECK

Mass archiving special functionality should be executed for not partitioned objects Possible values - X/' '.

MASS_ARCH_VAR_SPECIAL_EXEC

Mass archiving parallelism functionality starts the variants sequentially. The next variant is started if the previous one has an NL request created (partition is added), then it's running in parallel. And also it's setting up priority to a variant that is creating NL request (adding partition). It means all other running variants which are inserted into the table will wait while the variant creates an NL request. Possible values - X/' '.

MASS_ARCH_WAIT_TIME_PAR

Mass archiving for the first set of variants in parallel. The value is time in seconds, which variant of the first set will wait to run another one. It works only for parallel mass archiving. DO NOT set it up when parameter MASS_ARCH_VAR_SPECIAL_EXEC is set because it will uselessly decrease the performance of mass archiving. This is caused due to the fact the variant will wait twice. It is used for a deadlock situation when starting the initial run.

MAX_INSERT_PACKAGE_SIZE

NAV_ATTR_CHAR_VALUES_COUNT

Maximum number of records in Navigation attributes selection, for which navigation attributes selection is translated to basic IOBJ selection. Possible values - integer

NLS_LOOKUP_TRANSLATION

If Lookup translation code execution is turned on/off. Possible values - X/' '.

NLS_LOOKUP_TRANSLATION_KATE

If Lookup translation KATE testing is turned on. Only valid, if KATE is installed on the system. Possible values - X/' '.

SET_DEFAULT_SM_STORID_FOR_AGG

Identifies in which storage of storage management is the aggregate created.

WRITER_BACKUP_PACKAGE

WRITER_CHECK_FULL_LOAD

Parameter WRITER_CHECK_FULL_LOAD is used for InfoCube load and DSO Request activation. If this parameter has 'X', then all full loads are processed, i.e. Writer functionality is off. However, there is an exception table '/DVD/NLS_W2_LOAD'. In the field 'DATA_LOAD' can be stored the technical names of DTPs or InfoPackages, which will be processed by Writer.

WRITER_ENABLED_FOR_CUBE

Specifies whether the NLS Writer processing should take action when CUBE load processing interferes with archive selections. If turned off, SAP functionality works as standard.

WRITER_ENABLED_FOR_ODSO

Specifies whether the NLS Writer processing should take action when DSO load processing interferes with archive selections. If turned off, SAP functionality works as standard.

WRITER_INDEX_SEC_BUILD

Determines, if OutBoard Secondary Indexes will be rebuilt during NLS Writer adjustments values: 'X' - Rebuild , ' ' - Do not rebuild , 'P' - Rebuild partial.

WRITER_MAX_BUFFERED_PACKAGES

Parameter is relevant only for the DSO activation process. This parameter regulates the maximum number of buffered packages in memory. If the number is set to a “very high” figure, depending on hardware performance, this may cause a “MEMORY_LOW” short dump. Packages are kept in memory because of performance reasons. It is recommended that one package should be approx. 100MB, i.e. 10 packages will use 1GB of memory.

WRITER_ODSO_MAX_PACK_ROWS

Parameter is used for DSO Request activation. This parameter sets the maximum number of rows, which can be inserted into an archiving package. This setting is taken into account only when new data should be inserted into the archive.

Parameter is used for DSO Request activation. This parameter sets the maximum number of locked records, which will be processed by using the Writer. For cases where more records should be processed, Writer processing will be skipped and a warning will appear. If this happens, the user should increase the maximum number of records but this may affect the performance of the system.

WRITER_ODSO_MAX_REP_JOBS

Parameter is connected with the report '/DVD/NLS_W2_CHECK_DSO'. This parameter sets the maximum number of background jobs that will be used for moving locked data from an active table to an archive. Note: The minimum number of jobs is 2.

WRITER_REBUILD_AGGREGATES

Parameter is used for InfoCube load and ODS Request activation. If the parameter is set to 'X', then the Writer rebuilds all OutBoard Aggregates connected to the affected InfoProvider.

WRITER_TRS_MASS_DELETE

This parameter sets the value of how many records will be deleted from the database at once, saving time for logging operations on the database. For most systems, it is not recommended to set this parameter's value beyond 500.

WRITER_TRS_MASS_INSERT

This parameter sets the value of how many records will be inserted in bulk in one insert statement at once. Due to SQL command size limitations, it is not recommended to set this parameter's value beyond 5000.

RELOAD_DUPLICATES

Parameter is set during /dvd/nls_set_reload_duplicates. It determines which FM for getting locked records is used. (SPACE = /DVD/NLS_W2_IS_REQUEST_LOCKED / X =  /DVD/NLS_W2_GET_DUPLICATE_RECS).  Connected in Writer preprocessing with parameter WRITER_ODSO_MAX_RECORDS (max value of locked records in a DTP load, if there are many records in a locked area, they will be written into the error stack and writer processing will skip them).

NAV_ATTR_CURSOR_SIZE

Size of a cursor to read and replicate navigational attribute master data.

NAV_ATTR_GEN_WHERE_TAB

NAV_ATTR_ON_FLY_REPLICATION

LOG_TECH

Turns on/off writing technical logs into application logs. Use for debugging (at reading data from archive) Log obj.: /DVD/NLS_TECH. It can create a lot of "garbage" logs. 

INDEX_SEC_REBUILD_PAR_WP

Count of parallel work processes for sec index rebuild.

INDEX_PAR_WAIT_FINISH

Time period to check if all parallel processes (building a secondary index) have finished.

SET_EXCLUDE_INACTIVE_REQUEST

Effective only for transparent storages. Value X = in fetch next package add into where condition only active requests. This can cause performance problems because of too many requests. (200+) HADOOP - reporting on partitions is more effective.

USE_PIT_HANA

Point-in-Time recovery for HANA/primary database. Used to be able to recover from the state, where the archive is restored to a point in time when it doesn't correspond with the primary database.

USE_PIT_ARCHIVE

Point-in-Time recovery for an archive. Used to be able to recover from the state, where the primary database is restored to a point in time when it doesn't correspond with the archive.

PIT_BIN_STORAGE

Name of the binary storage from Storage Management used to store data for Point-in-Time recovery for HANA.

WRITER_SYB_UPDATE_DIRECTLY

WRITER_SYB_FOR_ALL_ENTRIES

Parameter is used for DSO Request activation. If the parameter is set to 'X', then for any transparent storage, Writer will select data from the NLS archive directly from the transparent storage table with an open SQL statement SELECT… FOR ALL ENTRIES.

WRITER_ODSO_PREPROC_OPTIM_READ

Turn on optimization via open cursor for all entries for lookup.

WRITER_VERIFICATION

Determine if verification phase during W2 processing should be executed. (value : SPACE = SKIP / C = count packages)

WRITER_CLEANUP_MAX_WHERE

Max number of rows in where condition during W2 cleanup phase. When exceeded processing dumps.