Queries on dm_init_be_timeout Value (Doc ID 3021309.1)

Last updated on MAY 09, 2024

Applies to:

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

Goal

After migrating the database to OCI/EXACS we had to increase the value of the flag dm_init_be_timeout from the standard value 1 to the value 9999 in order to be able to run the DM Oracle POD and avoid the timeout error.

The following queries needs to be addressed
1) What is the proper value for this flag?
2) What is the impact of this value modification?
3) The impact of the flag value modification impacts only the BRM initialization?

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 on dm_init_be_timeout Value (Doc ID 3021309.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!