Negative Impact Because of Database Compression (Doc ID 1642814.1)

Last updated on FEBRUARY 06, 2024

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and later
Information in this document applies to any platform.

Goal

To understand if Billing and Revenue Management (BRM) has any negative impact because of database compression.

Performance was improved for billing if BRM tables are compressed at Database level.

As an example:
- created tables in Oracle database with compressed option, e.g. use "COMPRESS FOR OLTP LOGGING" for all the tables.
- did not compress any index.

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Negative Impact Because of Database Compression (Doc ID 1642814.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!