Messaging Metadata Concurrent Request Results in Incomplete Metadata in HDR Config Tables (Doc ID 2898223.1)

Last updated on FEBRUARY 02, 2024

Applies to:

Symptoms

Oracle Healthcare Data Repository - Version 8.1.2 and later

ACTUAL BEHAVIOR
---------------
After a fresh install of HDR 8.1.2 with the latest patches, executing the messaging metadata concurrent request results in incomplete metadata in HDR's config tables.
Reviewing OHF_HDR_MS_CMPLX_TYP_ATTRBTS shows missing entries and breaking inbound messaging.

- One example that is missing: personalRelationship COCT_MT030000HT01.Person
- Without this, customer cannot process messages that have a personalRelationship. This particular parent complex type is missing eight entries - and it's just one type.
- This also appears to affect inbound messaging, even if you import metadata from a previous HTB instance, with messaging failing upon subsequent runs.

EXPECTED BEHAVIOR
-----------------------
Expected to see a complete metadata in HDR's config tables after executing the messaging metadata.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Install a fresh HDR 8.1.2 with the latest patches
2. Executing the messaging metadata
3. Observe incomplete metadata in HDR's config tables

Cause

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