SAP Knowledge Base Article - Preview

2903698 - LogMiner objects got compressed after upgrade database to 12.2.0.1

Symptom

You upgraded your Oracle database from 11.2 or 12.1 to 12.2.0.1. During the upgrade, the script "post_upgrade_tasks.sql" was executed and database parameter "_ADVANCED_INDEX_COMPRESSION_OPTIONS" was automatically set to 16. As a result of this parameter setting, all newly created indexes were compressed by default using "COMPRESS ADVANCED LOW" method.

For this compression method the Oracle license for the Advanced Compression Option (ACO) is needed. If you do not have this Oracle license for ACO, you must remove this parameter from SPFILE and rebuilt all indexes which have been compressed with "COMPRESS ADVANCED LOW" method.  You followed note 2500176 and decompressed/rebuilded the indexes in SAP schema. However, some LogMiner objects belong to SYSTEM still compressed.

For example:

OWNER  INDEX_NAME                   TABLE_NAME                     COMPRESSION
SYSTEM LOGMNR_I1SHARD_TS      LOGMNR_SHARD_TS         ADVANCED LOW
SYSTEM LOGMNRC_I1SHARD_TS    LOGMNRC_SHARD_TS       ADVANCED LOW
SYSTEM LOGMNRC_I1TS                LOGMNRC_TS                   ADVANCED LOW
SYSTEM LOGMNRC_I1TSPART         LOGMNRC_TSPART            ADVANCED LOW
SYSTEM LOGMNRC_TS_PK              LOGMNRC_TS                   ADVANCED LOW
SYSTEM LOGMNRC_TSPART_PK       LOGMNRC_TSPART            ADVANCED LOW
SYSTEM LOGMNRC_SHARD_TS_PK  LOGMNRC_SHARD_TS       ADVANCED LOW


Read more...

Environment

ORACLE

Keywords

_ADVANCED_INDEX_COMPRESSION_OPTIONS, Advanced Compression, LOGMNR_I1SHARD_TS, LOGMNRC_I1SHARD_TS, LOGMNRC_I1TS, LOGMNRC_I1TSPART, LOGMNRC_TS_PK, LOGMNRC_TSPART_PK, LOGMNRC_SHARD_TS_PK , KBA , BC-DB-ORA , Oracle , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.