(2002) Object Translation

During the process of archiving, old data in DataProviders (DSO, ADSO, etc.) is moved to different storages. At the same time, each DataProvider can have several objects (e.g. queries) that are dependent on them. If dependent objects aren't adjusted, they would access only partial data.

The diagram below illustrates an example. We have the DSO object ZJG_DS2. A dependent object, in this example a query, reads data from this DSO. After archiving, significant part of data is archived into another storage. In this example into the Target storage table. The query reads after archiving only half of data, as the other half can not be read by the query.

In this section

To solve the problem, dependent objects like queries must be translated. It is necessary to perform this translation before the actual archiving process starts.

OutBoard DataTiering supports automatic translation of dependent objects. The translation process consists of two steps:

Step: Impact analysis - is executed on the system and searches for dependent objects (like queries and lookups)
Step: Object adjustment - once the dependent objects are found, they must be adjusted. The adjusted dependent objects are added into a transport and imported up the transport route (e.g to a production system).

These both steps are part of the DataProvider Wizard.

SNP

(2002) Object Translation

Analytics

In this section

Related content