Last updated on SEPTEMBER 15, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 126.96.36.199.0
Information in this document applies to any platform.
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 ) ".
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