Kontakt

Ansicht
Dokumentation

RILM_STOR_TABLE_DISTRIBUTE_IQ - Program RILM_STOR_TABLE_DISTRIBUTION

RILM_STOR_TABLE_DISTRIBUTE_IQ - Program RILM_STOR_TABLE_DISTRIBUTION

BAL Application Log Documentation   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You need to execute the report before you implement the ILM Database Store as soon as a database other than that of the application server is to be used as the store. With the help of this report, you can distribute the tables required for the ILM Database Store to the various database system, and, if necessary, generate them in the target systems.

Note: The ILM Database Store supports Sybase IQ Version 15.4.

The following tables are considered:

  • TILM_STOR: Root Table / Mapping URI-HANDLE
  • TILM_STOR_AUDIT: Table with Processing Information
  • TILM_STOR_BLOB: Table of Resources
  • TILM_STOR_CERT: Table of Certificates
  • TILM_STOR_COL: Table of Collections
  • TILM_STOR_POOL: Management of Pool Tables
  • TILM_STOR_PROP: Archive Properties
  • TILM_STOR_RTI: Runtime Properties Table
  • TILM_STOR_RTM: Runtime Management Table

The tables can either be created on the database of the application server or on one or more secondary databases. In the first case, enter DEFAULT as the DB connection for the relevant tables. This setting is then persisted.

If you want to create a table on a secondary DB, select the valid DB connection. Make sure you have already defined the connection using transaction DBCO. Doing so persists the setting and the table is physically generated on the target DB. When executing the report, only the connection is persisted for table TILM_STOR_BLOB; the table is generated later when the actual data is stored on the target DB.

The following table distribution is recommended:

  • Use of the application server's DB for the main administration tables:
  • TILM_STOR

  • TILM_STOR_POOL

  • TILM_STOR_PROP (for performance reasons; should actually be on the secondary DB)

  • TILM_STOR_RTI

  • TILM_STOR_RTM

  • We recommend storing the following tables on a secondary DB:
  • TILM_STOR_BLOB

  • TILM_STOR_CERT

  • TILM_STOR_COL

You can make changes to the table distribution as long as the tables do not contain any data. As soon as data is found in a table, it is no longer possible to move the affected table. This prevents data inconsistencies and loss of data. In cases such as these, you need to use a separate report to move the data.

Integration

Prerequisites

Features

Selection

Standard Variants

Output

Activities

Example






rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3472 Date: 20240531 Time: 091115     sap01-206 ( 53 ms )