My Oracle Support Banner

ORA-44001: invalid schema When Trying to Accept E2B Into Non-Default Enterprise (Doc ID 2453369.1)

Last updated on OCTOBER 07, 2018

Applies to:

Oracle Argus Safety - Version 8.1.1 and later
Information in this document applies to any platform.

Symptoms

Trying to accept E2B R2 file into a specific enterprise.

Get the following message on the Case Import Warning Messages pop-up screen:

Error in CFG_E2B.AE_USER_PROC for Profile ICH-ICSR V2.1 MESSAGE TEMPLATE - EMA, DTD Element MEDICINALPRODUCT ORA-44001: invalid schema

Error Stack has the following messages:

ORA-44001: invalid schemaORA-06512: at "SYS.DBMS_ASSERT", line 333
ORA-06512: at "ESM_OWNER.ESM_UTL", line 6368
ORA-06512: at "ESM_OWNER.ESM_UTL", line 6342
ORA-06512: at line 149
ORA-06512: at "SYS.DBMS_SQL", line 1707
ORA-06512: at "ESM_QUERY_USER.ESM_PKG", line 13277

PL/SQL Call Stack:
13294 ESM_PKG.F_EXECUTE_USER_PROC
374 ESM_IMP.P_IMP_DATA_TRANSLATE
417 ESM_IMP.P_IMP_DATA_TRANSLATE2
1 __anonymous_block

768 ESM_IMP_UTL.WRITE_ERROR_MSG
13294 ESM_PKG.F_EXECUTE_USER_PROC
374 ESM_IMP.P_IMP_DATA_TRANSLATE
417 ESM_IMP.P_IMP_DATA_TRANSLATE2
1 __anonymous_block

The sameE2B file loads in the Base Default Enterprise without any issues

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


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