My Oracle Support Banner

E1: ESU: Software Updates Fail to Apply When Backup/OMW Options Are Selected - JDB2700003, JDB9900245, "Failed to create OMWProjectObject" Errors (Doc ID 966224.1)

Last updated on APRIL 18, 2025

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.

Symptoms

JDE EnterpriseOne 9.0 application release level . Issue when applying any ESU patch where the backup process/OMW creation fails if selected. ESUs apply with no problems if the backup/OMW boxes are unchecked.

The jde.log may show the following when attempting to apply ESUs with the backup/OMW project option checked on when DEP9 or other invalid mappings were found active in the local database :

5676/5680 MAIN_THREAD Wed Sep 09 12:52:16.538000 Jdb_ctl.c3940 Starting OneWorld
5676/6020 WRK:Starting jdeCallObject Wed Sep 09 12:52:55.850000 B9600490.c1916 Verify Deployment Package (F98403): JL12089 Environment: DV900
5676/6020 WRK:Starting jdeCallObject Wed Sep 09 12:52:55.866000 B9600490.c1916 Dependent Objects Verified
5676/6020 WRK:Starting jdeCallObject Wed Sep 09 12:52:57.475000 Jtp_tm.c1183 JDB9909101 - GetDSRecord failed: data source
5676/6020 WRK:Starting jdeCallObject Wed Sep 09 12:52:57.475001 Jdb_rq1.c3021 JDB2700003 - Failed to connect to the DataSource OneWorld Local failed
5676/6020 WRK:Starting jdeCallObject Wed Sep 09 12:52:57.475002 Jdb_omp1.c598 JDB9900245 - Failed to find F98611 OneWorld Local in cache 5676/6020 WRK:Starting jdeCallObject Wed Sep 09 12:52:57.475003 Jdb_rq1.c1959 JDB3100011 - Failed to get location of table F983051 for environment JDEPLAN
5676/6020 WRK:Starting jdeCallObject Wed Sep 09 12:52:57.475004 Jdb_exet.c10314 JDB9900224 - Failed to validate request handle
5676/6020 WRK:Starting jdeCallObject Wed Sep 09 12:52:57.475005 OMWEntry.cpp852 OMWMethod : eCREATEPROJECT -- OMWExceptionError caught. Error : Memory Error: Failed to create OMWProjectObject. 5676/6020 FOREIGN_THREAD Wed Sep 09 12:53:45.538000 Jdb_ctl.c6660 JDB4200003 - OPEN TABLE NOT CLOSED = F98220
5676/5680 MAIN_THREAD Wed Sep 09 12:53:50.616000 Jdb_ctl.c6660 JDB4200003 - OPEN TABLE NOT CLOSED = F98220 5676/5680 MAIN_THREAD Wed Sep 09 12:53:50.616001 Jdb_ctl.c6660 JDB4200003 - OPEN TABLE NOT CLOSED = F98222


The jdedebug.log clearly showed how it used the first environment attached to the Planner pathcode (ASTARTUP) instead of the actual environment either requested or logged into at the time :

Sep 22 13:24:02.094350 - 2096/3424 WRK:Starting jdeCallObject Exiting JDB_OpenTable(Table = F00941) with Success
Sep 22 13:24:02.094351 - 2096/3424 WRK:Starting jdeCallObject Entering JDB_OpenTable(Table = F986101)
Sep 22 13:24:02.094352 - 2096/3424 WRK:Starting jdeCallObject ODBC:X DBInitConnection shr(54) con=03970DD8 env=03D434D8 dbc=03D43580 spid=51 cur=0,3,6 sep=. (local) A (JDE@EnterpriseOne SSELocal)
Sep 22 13:24:02.094353 - 2096/3424 WRK:Starting jdeCallObject Exiting JDB_OpenTable(Table = F986101) with Success
Sep 22 13:24:02.094354 - 2096/3424 WRK:Starting jdeCallObject Entering JDB_SetSelection
Sep 22 13:24:02.094355 - 2096/3424 WRK:Starting jdeCallObject Exiting JDB_SetSelection With Success
Sep 22 13:24:02.110000 - 2096/3424 WRK:Starting jdeCallObject Entering JDB_SelectKeyedPosition
Sep 22 13:24:02.110001 - 2096/3424 WRK:Starting jdeCallObject ODBC:X DBInitRequest(new) req=2777EBC0 con=03970DD8 env=03D434D8 dbc=03D43580 spid=51 (local) A (JDE@EnterpriseOne SSELocal)
Sep 22 13:24:02.110002 - 2096/3424 WRK:Starting jdeCallObject SELECT LMLL FROM JDEPlan900.DBO.F00941 WHERE ( LMPATHCD = 'PLANNER' ) ORDER BY LMLL ASC
Sep 22 13:24:02.110003 - 2096/3424 WRK:Starting jdeCallObject Entering DBPerformRequest
Sep 22 13:24:02.110004 - 2096/3424 WRK:Starting jdeCallObject ODBC:X DBPerformRequest req=2777EBC0 con=03970DD8 env=03D434D8 dbc=03D43580 spid=51 (local) A (JDE@EnterpriseOne SSELocal)
Sep 22 13:24:02.110005 - 2096/3424 WRK:Starting jdeCallObject Exiting DBPerformRequest
Sep 22 13:24:02.110006 - 2096/3424 WRK:Starting jdeCallObject Exiting JDB_SelectKeyedPosition with Success
Sep 22 13:24:02.110007 - 2096/3424 WRK:Starting jdeCallObject Fetched the record
Sep 22 13:24:02.110008 - 2096/3424 WRK:Starting jdeCallObject Entering JDB_SelectKeyed
Sep 22 13:24:02.110009 - 2096/3424 WRK:Starting jdeCallObject ODBC:X DBInitRequest(new) req=0ABF0980 con=03970DD8 env=03D434D8 dbc=03D43580 spid=51 (local) A (JDE@EnterpriseOne SSELocal)
Sep 22 13:24:02.110010 - 2096/3424 WRK:Starting jdeCallObject SELECT OMDATP, OMSTSO FROM JDEPlan900.DBO.F986101 WHERE ( OMENHV = 'ASTARTUP ' AND OMOBNM = 'F983051' AND OMUGRP = '*PUBLIC' ) ORDER BY OMENHV ASC,OMOBNM ASC,OMUGRP ASC,OMDATP ASC
Sep 22 13:24:02.110011 - 2096/3424 WRK:Starting jdeCallObject Entering DBPerformRequest
Sep 22 13:24:02.110012 - 2096/3424 WRK:Starting jdeCallObject ODBC:X DBPerformRequest req=0ABF0980 con=03970DD8 env=03D434D8 dbc=03D43580 spid=51 (local) A (JDE@EnterpriseOne SSELocal)
Sep 22 13:24:02.110013 - 2096/3424 WRK:Starting jdeCallObject Exiting DBPerformRequest
Sep 22 13:24:02.110014 - 2096/3424 WRK:Starting jdeCallObject Exiting JDB_SelectKeyed with Success
Sep 22 13:24:02.110015 - 2096/3424 WRK:Starting jdeCallObject No More Data found
Sep 22 13:24:02.110016 - 2096/3424 WRK:Starting jdeCallObject Fetched the record
Sep 22 13:24:02.110017 - 2096/3424 WRK:Starting jdeCallObject Entering JDB_SelectKeyed
Sep 22 13:24:02.110018 - 2096/3424 WRK:Starting jdeCallObject ODBC:X DBResetRequest req=0ABF0980 con=03970DD8 env=03D434D8 dbc=03D43580 spid=51 (local) A (JDE@EnterpriseOne SSELocal)
Sep 22 13:24:02.110019 - 2096/3424 WRK:Starting jdeCallObject *SELECT OMDATP, OMSTSO FROM JDEPlan900.DBO.F986101 WHERE ( OMENHV = 'DEP9 ' AND OMOBNM = 'F983051' AND OMUGRP = '*PUBLIC' ) ORDER BY OMENHV ASC,OMOBNM ASC,OMUGRP ASC,OMDATP ASC*
Sep 22 13:24:02.110020 - 2096/3424 WRK:Starting jdeCallObject Entering DBPerformRequest
Sep 22 13:24:02.110021 - 2096/3424 WRK:Starting jdeCallObject ODBC:X DBPerformRequest req=0ABF0980 con=03970DD8 env=03D434D8 dbc=03D43580 spid=51 (local) A (JDE@EnterpriseOne SSELocal)

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
References


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