Deployment Of Custom Data Model Modifications In Multi-Schema (Doc ID 1391961.1)

Last updated on SEPTEMBER 15, 2016

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

For multi-schema architecture: All custom objects are defined in a single podl file that is deployed by using pin_deploy with the replace option on each schema, using a CM that points to only one schema.

The problem is when there are modifications of already deployed custom objects, in particular for custom /config objects that are present only in the primary schema. If the procedure described above is used, pin_deploy fails with error PIN_ERR_STORAGE:43. The the DM pinlog contains "ALTER TABLE config_message_alerte_t ADD (message_flags int ) ". 

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