My Oracle Support Banner

Cross Schema Account Creation was Failing with CM Error "PIN_ERR_AUDIT_COMMIT_FAILED:98" And Dm_oracle "ORA-01031: insufficient privileges" (Doc ID 1545296.1)

Last updated on MAY 11, 2021

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.5.0]
Information in this document applies to any platform.
Checked for relevance on 30-Aug-2016.


This problem may happen with implementations using the Billing and Revenue Management (BRM) Multischema Architecture introduced from the product documentation Oracle® Communications Billing and Revenue Management - Concepts :

In multischema systems, the database layer of your BRM system consists of one primary schema and one or more secondary schemas in a single database. A primary DM is connected to the primary schema and secondary DMs are connected to the secondary schemas.

For instance:

  CM1 -- > DM1 (primary schema)
  CM2 -- > DM2 (secondary schema)

In such a situation, it may well be possible to create accounts from the primary Connection Manager 1 (CM1) through the primary schema, so using DM1, yet be impossible to create an account from the same primary CM1 through the secondary schema, for instance DM2.

In that case, the system may refuse the account creation and print:


This problem may occur following a new installation or an upgrade. The "Solution" below is a procedure that should always be applied when the multi schema feature is enabled.


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

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