Queries About Schema and High-Availablity During Pipeline Database Installation (Doc ID 2463545.1)

Last updated on SEPTEMBER 08, 2023

Applies to:

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

Goal

Q1. During the Pipeline database installation, tables can be installed on existing Billing and Revenue Management (BRM) schema which uses PINX00 and PIN00 tablespaces, or customer can choose another database schema with different tablespaces. If the existing BRM schema is used for installation, will there be any impact on BRM functionality and performance?

Q2. Discounting Pipeline can be installed in high-availability mode: in case if one of the discounting pipeline is unavailable, Connection Manager (CM) can connect to the other. Will it be ok to use the following configuration in CMs pin.conf to achieve that?
- cm em_pointer discounting ip ${HOSTNAME1} 24000
- cm em_pointer discounting ip ${HOSTNAME2} 24000

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.

Queries About Schema and High-Availablity During Pipeline Database Installation (Doc ID 2463545.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!