(SP21) Maintenance, Contact details and FAQ

Backup

Since OutBoard is completely stored in the online database, no additional backup strategy has to be developed. With every regular system backup, OutBoard is automatically included.  OutBoard can however help to shrink the backup runtime as it shrinks the total volume of the database.

Change of structure

The change of structure (e.g. new InfoObject added) of the source InfoProvider is supported by OutBoard. Each request knows its source structure and in the process of decompression copies the data in the most current structure with "move corresponding" ABAP statement. Therefore the change of structure has a minor runtime impact on the reading from older requests.

Storage maintenance

For each InfoProvider, separate storage area table is generated. As of October 2014 it follows the naming convention /DV1/CN for the cluster table and /DV1/IN for the index table. The previously used namespace /BIC/* is now obsolete, so it is recommended to automatically move the archived data from /BIC/* tables to /DV1/ tables. If not, there may be issues in the future when trying to overwrite the archived data via some standard SAP objects (using namespace /BIC/)To move the data from obsolete /BIC/* tables to new /DV1/* tables use the report /DVD/NLS_COPY_BIC_TO_DV1 or start this report from NLS Menu. After the /BIC/ data is succesfully moved to the /DV1/ tables (in the verification phase no problem was found), the obsolete /BIC/ tables are not accessed anymore when reading the data. For safety reasons, the mentioned report can be run in a mode, where the /BIC/ tables are not deleted – in this case it is recommended to delete them afterwards, once successfully copying to /DV1/ tables is confirmed.For certain scenarios, it can be beneficial to put these storage tables into same tablespace. It is recommended to do so after creation of each DAP, because at that time the table is empty and possible change of table space will be easy.