Inconsistent Behavior In Single BI Context Transaction If Changes Done Along With Condition Delete. (Doc ID 1443112.1)

Last updated on JULY 12, 2017

Applies to:

Oracle Communications Unified Inventory Management - Version 7.1.2 to 7.1.2 [Release 7.1.0]
Information in this document applies to any platform.

Symptoms

Inconsistent behavior is observed with in single BI context transaction if changes done along with Condition delete.

Within single transaction the following 2 scenarios were performed:

Scenario I:
1. name, description, characteristic of PD get updated
2. previously put condition get deleted
3. new condition is created
4. transaction committed
Outcome:
Search performed on this stage shows that condition is created, but update done in (1) is not there. To be exact name and description is not updated, only characteristic gets updated.

Scenario II:
1. delete previous condition
2. update name, description, characteristic
3. create new condition
4. commit transaction
Outcome:
Search shows that newly created condition as well as all updates are done at point 2.

As those things are done in single transaction, it will not be possible to reproduce this in GUI.

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