HDR: Using MtkTestService TestCustomMessageType Method CTB_MTK_XSD_MIF_ELMT_MISMATCH: Input SCHEMA and MIF files does not match (Doc ID 2126747.1)

Last updated on MAY 07, 2017

Applies to:

Oracle Healthcare Data Repository - Version 7.0.1 and later
Information in this document applies to any platform.

Goal

On HDR 7.0.1,  when attempting to upload customer messaging configuration using the MTK (Programmer's Guide for the MTK content) the following error is returned:

MESSAGE_PARAM = CTB_MTK_XSD_MIF_ELMT_MISMATCH: Input SCHEMA and MIF files does not match. Element code found in SCHEMA COMPLEX TYPE COCT_MT920000HT02.ObservationCriteria is missing in corrosponding MIF file.

Per the stack trace file:

Original Stacktrace:
oracle.apps.ctb.fwk.base.server.CTBValidationRuntimeException
CODE = CTB_MTK_XSD_MIF_ELMT_MISMATCH
MESSAGE = CTB_MTK_XSD_MIF_ELMT_MISMATCH: Input SCHEMA and MIF files does not match. Element code found in SCHEMA COMPLEX TYPE COCT_MT920000HT02.ObservationCriteria is missing in corrosponding MIF file.

at oracle.apps.ctb.message.mtk.xmlschemaloader.server.SchemaValidator.findComplexTypeAttributeForComplexElement(SchemaValidator.java:476)
at oracle.apps.ctb.message.mtk.xmlschemaloader.server.SchemaValidator.validateComplexType(SchemaValidator.java:194)
at oracle.apps.ctb.message.mtk.xmlschemaloader.server.SchemaValidator.validateSchema(SchemaValidator.java:93)
at oracle.apps.ctb.message.mtk.xmlschemaloader.server.SchemaLoader.uploadSchemas(SchemaLoader.java:388)
at oracle.apps.ctb.message.mtk.xmlschemaloader.server.SchemaLoader.uploadMessageType(SchemaLoader.java:219)
at oracle.apps.ctb.message.mtk.server.MtkTestServiceAMImpl.testCustomMessageType(MtkTestServiceAMImpl.java:239)
at oracle.apps.ctb.message.mtk.server.MtkTestServiceStatelessBMTBean.testCustomMessageType(MtkTestServiceStatelessBMTBean.java:144)
at oracle.apps.ctb.message.mtk.server.MtkTestServiceStatelessBMTBean_hc0tr0_MtkTestServiceRemoteBMTImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:34)
at oracle.apps.ctb.message.mtk.server.MtkTestServiceStatelessBMTBean_hc0tr0_MtkTestServiceRemoteBMTImpl.testCustomMessageType(Unknown Source)
at oracle.apps.ctb.message.mtk.server.MtkTestServiceStatelessBMTBean_hc0tr0_MtkTestServiceRemoteBMTImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:693)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:519)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:515)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)

at weblogic.utils.StackTraceDisabled.unknownMethod()
Caused by: oracle.apps.ctb.fwk.base.common.CTBValidationException
TYPE_PARAM = ERROR
CODE_PARAM = null
MESSAGE_PARAM = CTB_MTK_XSD_MIF_ELMT_MISMATCH: Input SCHEMA and MIF files does not match. Element code found in SCHEMA COMPLEX TYPE COCT_MT920000HT02.ObservationCriteria is missing in corrosponding MIF file.

... 1 more
Process exited with exit code 0.

 


The CMET COCT_MT920000HT02 is the Substance Administration Order CMET. It is not directly referenced in the uploaded payload XSD or MIF. It is also not referenced at all in the uploaded customer CMET XSD or MIF. The COCT_MT920000HT02.xsd and .mif files in the deployed HDR 7.0.1 application referenced the ObservationCriteria.

For the HTB 6.X Installation there was a concurrent job called "Healthcare Messaging Metadata Loader". Its purpose was to load the messaging artifact metadata from the MIF files for IMP, OMP, and MTK. in HDR 7.0.1, these tables are empty.  Unable to upload the custom changes to the Encounter Event message until this error is solved.

STEPS TO REPRODUCE
-----------------------
The issue can be reproduced at will with the following steps:

1. Call the TestIdData.getStatus() method on the failed test. It returns the following information:

 

Solution

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