E1: ESU: ESUs Do Not Appear In The Grid After Been Installed - "Copy/Init Data Error" In Software Updates Application (P96470)
(Doc ID 1377673.1)
Last updated on MAY 01, 2023
Applies to:
JD Edwards EnterpriseOne Tools - Version SP24 and laterInformation in this document applies to any platform.
Symptoms
Scenario 1: JDB9900428 'Failed to get new instance object or method ID' and 'Exception: failed to login to environment = JDEPLAN'
After installing the ESUs in the deployment server, the installed ESUs are not shown in the Software Updates application P96470. There is an error stating, "Copy/Init Data Error", in the P96470 application, bottom left hand corner. Additionally, the JDE logs showed the following error messages:
JdeJvm::CheckForExceptions() - Java Exception encountered : java.lang.Exception: failed to login to environment = JDEPLAN
4140/5080 WRK:Starting jdeCallObject Wed Nov 16 07:59:07.417001 JdeJvm.cpp2060
JdeJvm::CheckForExceptions() - Stack Trace for Exception : java.lang.Exception: failed to login to environment = JDEPLAN
at oracle.e1.database.copytablexml.E1CopyTableXML.login(Unknown Source)
at oracle.e1.database.copytablexml.E1CopyTableXML.getConnection(Unknown Source)
at oracle.e1.database.copytablexml.E1CopyTableXML.initColumnInfo(Unknown Source)
at oracle.e1.database.copytablexml.E1CopyTableXML.<init>(Unknown Source)
JDB9900428 - Failed to get new instance object or method ID
4140/5080 WRK:Starting jdeCallObject Wed Nov 16 07:59:07.423026 Jdb_rq1.c5758
JDB3700001 - Failed to validate Request handle
4140/5080 WRK:Starting jdeCallObject Wed Nov 16 07:59:07.424003 Jdb_rq1.c5758
JDB3700001 - Failed to validate Request handle
4140/5080 WRK:Starting jdeCallObject Wed Nov 16 07:59:07.426003 Jdb_rq1.c5758
JDB3700001 - Failed to validate Request handle
Scenario 2: ESUs do not appear in grid; 'Data directory for xxx missing from planner\data'
EnterpriseOne 9.0 / TR 8.98. Client has successfully installed many ESUs using the Electronic Software Updates application (P96470). They have downloaded about 50 ESUs and is attempting to install them, but the ESUs do not appear in the grid.
The status bar in the P96470 has a message stating: "Copy/Init Data error". The Event Viewer does not have any messages as to why the data copy is failing.
The jde.log has the following message:
Starting OneWorld
6108/5648 WRK:Starting jdeCallObject Fri Jul 10 11:43:26.648322 B96701.c1676
Data directory for JL11392 missing from planner\data
6108/5648 WRK:Starting jdeCallObject Fri Jul 10 11:43:26.664001 B96701.c1679
Remove registery entry for JL11392 from JDEdwards | OneWorldWindowsInstaller | Install.ini
On the Deployment Server, the folder mentioned in the jde.log Planner\data\JL11392 does not exist. Customer tried re-extracting patch ESU JL11392, however, the folder still does not get created in planner\data and none of the other extracted ESUs appear in the grid for installing.
Scenario 3: EnterpriseOne 8.9 application release issue; errors for missing DD specs table F9671 in TAM
This scenario applies ONLY to EnterpriseOne releases prior to aplication release 8.9, i.e. those E1 release levels using Access for the local database on the Deployment Server as EnterpriseOne Xe or ERP8.0.
Customer ran the executable file for the software update (e.g. JD123.exe), then logged into the JDEPLAN environment and opened the software updates application from menu GH9612. However, the update does not show up in the grid. At the bottom of the form on the left side of the application, there is a "Copy/Init Data Error" message. The jde.log shows errors regarding not being able to find Data Dictionary specs for the F9671 table in TAM. Customer can manually open the table in Access and see the data in the jdeb7.mdb file. But is unable to open table using UTB.
Scenario 4: 'Unable to find the configure file jdbj.ini'
When attempting to apply ESU using P96470 ESU application, the following error occurred in JDE.LOG:
JdeJvm::CheckForExceptions() - Stack Trace for Exception : java.lang.Exception: A JDBException occured. at oracle.e1.database.copytablexml.StandAloneCopyTableXML.initColumnInfo(Unknown Source) at oracle.e1.database.copytablexml.StandAloneCopyTableXML.<init>(Unknown Source)
Caused by: com.jdedwards.database.base.JDBException: [BOOTSTRAP_ERROR] An error occurred during bootstrap.
...
Caused by: java.io.IOException: Unable to find the configure file jdbj.ini
at com.jdedwards.base.util.IniFileLoader.getAbsoluteFileName(Unknown Source)
at com.jdedwards.base.util.IniFileLoader.load(Unknown Source)
... 8 more.
Scenario 5: Encounter "Database Connection failed for DataSource System Local" in JDE.log
After installing the ESU and using P96470 to apply the ESU, the new ESU did not appear in the grid. JDE.log states the following error:
3676/672 MAIN_THREAD Wed Jan 21 06:55:06.993000 Jdb_ctl.c4050
Starting OneWorld
3676/3548 WRK:Starting jdeCallObject Wed Jan 21 06:56:20.501000 JdeJvm.cpp2060
JdeJvm::CheckForExceptions() - Java Exception encountered : java.lang.Exception: A JDBException occured.
3676/3548 WRK:Starting jdeCallObject Wed Jan 21 06:56:20.501001 JdeJvm.cpp2060
JdeJvm::CheckForExceptions() - Stack Trace for Exception : java.lang.Exception: A JDBException occured. at oracle.e1.database.copytablexml.StandAloneCopyTableXML.initColumnInfo(Unknown Source) at oracle.e1.database.copytablexml.StandAloneCopyTableXML.<init>(Unknown Source)Caused by: com.jdedwards.database.base.JDBException: [DATABASE_CONNECT_FAILED] Database Connection failed for DataSource System Local. at com.jdedwards.database.impl.physical.JDBConnectionManager.createNewConnection(Unknown Source) at com.jdedwards.database.impl.physical.JDBConnectionManager.getPhysicalConnection(Unknown Source) at com.jdedwards.database.impl.physical.JDBRetryableConnection.attempt(Unknown Source) at com.jdedwards.base.util.Retryer.retry(Unknown Source) at com.jdedwards.database.impl.physical.JDBConnectionManager.getConnection(Unknown Source) at com.jdedwards.database.jdb.JDBStandaloneConnectionFactory.newPhysicalAccess(Unknown Source) at com.jdedwards.database.jdb.JDBStandaloneConnectionFactory.newPhysicalAccess(Unknown Source) at com.jdedwards.database.impl.logical.JDBLogicalConnection.resolvePhysicalConnection(Unknown Source) at com.jdedwards.database.impl.logical.JDBLogicalConnection.select(Unknown Source) at com.jdedwards.database.impl.condensed.JDBCondensedAccessDelegate.select(Unknown Source) at com.jdedwards.database.impl.usage.JDBUsageTrackingAccess.select(Unknown Source) at com.jdedwards.database.impl.condensed.JDBCondensedAccessExpander.select(Unknown Source) ... 2 moreCaused by: java.sql.SQLException: The Network Adapter could not establish the connection at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:412) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:531) at oracle.jdbc.driver.T4CConnection.
Scenario 6: Encounter "An SQL exception occurred: ORA-01536: space quota exceeded for tablespace 'JDEVL910'"
After running the esuname.exe, log into JDEPLAN and go into P96470, and get an error on screen regarding the ESU and the following in the jde.log:
Changes
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 |
| Scenario 1: JDB9900428 'Failed to get new instance object or method ID' and 'Exception: failed to login to environment = JDEPLAN' |
| Scenario 2: ESUs do not appear in grid; 'Data directory for xxx missing from planner\data' |
| Scenario 3: EnterpriseOne 8.9 application release issue; errors for missing DD specs table F9671 in TAM |
| Scenario 4: 'Unable to find the configure file jdbj.ini' |
| Scenario 5: Encounter "Database Connection failed for DataSource System Local" in JDE.log |
| Scenario 6: Encounter "An SQL exception occurred: ORA-01536: space quota exceeded for tablespace 'JDEVL910'" |
| Scenario 7: "No suitable driver found for jdbc" |
| Scenario 8: "SQL Server Browser Services not started" |
| Changes |
| Cause |
| Scenario 1: JDB9900428 'Failed to get new instance object or method ID' and 'Exception: failed to login to environment = JDEPLAN' |
| Scenario 2: ESUs do not appear in grid; 'Data directory for xxx missing from planner\data' |
| Scenario 3: 8.9 application release issue; errors for missing DD specs table F9671 in TAM |
| Scenario 4: 'Unable to find the configure file jdbj.ini' |
| Scenario 5: Encounter "Database Connection failed for DataSource System Local" in JDE.log |
| Scenario 6: Encounter "An SQL exception occurred: ORA-01536: space quota exceeded for tablespace 'JDEVL910'" |
| Scenario 7: "No suitable driver found for jdbc" |
| Scenario 8: "SQL Server Browser Services not started" |
| Solution |
| Scenario 1: JDB9900428 'Failed to get new instance object or method ID' and 'Exception: failed to login to environment = JDEPLAN' |
| Scenario 2: ESUs do not appear in grid; 'Data directory for xxx missing from planner\data' |
| Scenario 3: 8.9 application release issue; errors for missing DD specs table F9671 in TAM |
| Scenario 4: 'Unable to find the configure file jdbj.ini' |
| Scenario 5: Encounter "Database Connection failed for DataSource System Local" in JDE.log |
| Scenario 6: Encounter "An SQL exception occurred: ORA-01536: space quota exceeded for tablespace 'JDEVL910'" |
| Scenario 7: "No suitable driver found for jdbc" |
| Scenario 8: "SQL Server Browser Services not started" |
| References |