After Service Transfer ECE Cache Referring Old Account Instance After Incremental Loading (Doc ID 2961543.1)

Last updated on JULY 18, 2023

Applies to:

Symptoms

Steps to Reproduce:
---------------------------
1. Create source and target account
2. Add mobile service on source account
3. Perform some data usage
4. Perform service transfer
5. Capture source and target service account customer cache details
6. Perform data usage
7. Sync source account from BRM to ECE(with the help of incremental loading)
8. Perform data usage

Note: Capture PublicUserIdentity details before and after service transfer and also after syncing the source account

Actual result:
After Service Transfer, Service is still active under source account's audit (au_service_t) table and also under the target account's audit (au_service_t) table.

Expected:
After incremental loading of the source account ECE PublicUserIdentity cache should have been updated with target poid and in au_service_t the status for the source account should have been inactive.

Changes

Cause

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