Upgrade To Multi-Schema, The Effective_t Populate In Uniqueness Tables Is Wrong. (Doc ID 1352054.1)

Last updated on DECEMBER 30, 2011

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.4.0.0.0 and later   [Release: 7.4.0 and later ]
Information in this document applies to any platform.

Symptoms

When initializing multi-schema using pin_multidb.pl, one of the step populates all the login data into uniqueness_t. Effective_t populated in uniqueness_t table is the current time when running the pin_multidb. Any late CDRs/Suspense recycle CDRs that are routed through the router pipeline with start_time before running pin_multidb are rejected with ERR_CUSTOMER_LOGIN_NOT_VALID_FOR_TIME error.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms