Custom Medatadata - DB column not created on channel deployment with Oracle 19c DB (OCI)

[roggss]

Deploying a channel with Oracle 19c will not create the custom metadata column on the database side.
And if meta data was created manually on the DB side the column will still be deleted when channel got depolyed.

To Reproduce

1. Use Oracle19c database
2. Create a channel with custom metadata
3. Deploy the channel,

Expected behavior
Custom metada should be added to D_MCMxxx table

Actual behavior
D_MCM will only contains with two metada columns as below
metadata_id
message_id

Screenshots
Mirth

DB structure

Environment (please complete the following information):

• OS: Windows Server 2012R2 Stanadard
• Java Distribution/Version
• openjdk version "1.8.0_372"
• OpenJDK Runtime Environment Corretto-8.372.07.1 (build 1.8.0_372-b07)
• OpenJDK 64-Bit Server VM Corretto-8.372.07.1 (build 25.372-b07, mixed mode)
• Connect Version :3.9.0
• Oracle 19c (In Oracle Cloud Infrastructure or OCI Environment)

Workaround(s)
No workaround I can think, Please hellp

[pladesma]

Do you know if you can reproduce this in more recent versions of Mirth Connect? I tested in MC 4.4.0, and I'm not seeing the issue.

[roggss]

I tested it and does not exist in MC 4.4.0. The initialization of tables however, is not happening so I have to run the SQL statements manually plus the creation of D_CHANNELS (which is not on SQL file dbconf). refer to my post below about DB initialization issue that both exist in 3.9 and 4.4 for Oracle 19C database. #5886

Back to 3.9, is there a work around on this?

Thanks

PS: Oracle 19c (In Oracle Cloud Infrastructure or OCI Environment)

[roggss]

Furthermore, the custom metadata columns are not deleted if the channel was created under the new instance/db.

The metadata columns are only removed if the channel was migrated (coming from restore config).
And also, I noticed that if the metadata name changed, the channel will not be deplyed.., it just in keep in "deploying" status/

Looks like this issue is only for migrated channels. New created channels dont have this issue.

Please help

[pladesma]

Sorry, I don't have a good workaround at the moment. We'll need to do some research and get back to you.

[roggss]

Apparently, all the issues gone away after I changed my schema/user from any of these "mirth", " mirth1", "mirth2", "mirth3" to "MIRTHDB". Im not sure if the caps lock matter or its the schema name itself. I will definitely do a test if the uppercase matter. more to come :)