E1: ESU: Information And Troubleshooting Known Errors And Issues With UBE R98407 - "Table and Index Creation" When Installing A Software Update Patch (ESU or ASU)
(Doc ID 1502692.1)
Last updated on JANUARY 30, 2018
Applies to:JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.
This document is part of an Information Center - to see other documents related to Software Updates, please use the links provided below:
Information Center: Software Updates(ESUs, ASUs), Product Packaging, Change Assistant, Configuration Assistant and OBA in the JD Edwards EnterpriseOne Tools and Technology Product > Information Center: Troubleshooting Software Updates(ESUs and ASUs) in the JD Edwards EnterpriseOne Tools and Technology Product > Software Updates - "Application Table Merges" section
This document was created to provide vital information on UBE R98407 and assist customers on troubleshooting the different scenarios, causes and resolutions for issues involving Software Update (ESU or ASU) patch install errors when there are errors occurring on running UBE report
Overview of UBE R98407 and Examples of R98407 XJDE0001 PDF Results
The process of adding new tables for any software updates (ESU or ASU) may utilize the UBE R98407 - Table and Index Creation" during the software update patch application process to generate the table(s). The R98407 runs with ESUs that provide new tables and indexes that will automatically generate the table/indexes in the target datasource, but only in the target datasource. By design, if the ESU is not installed directly to the environment, then the table/index doesn't get generated in that datasource.
From EnterpriseOne 8.11 SP1 onwards, there is a change to the ESU installation process that will automatically generate new tables and new indexes when an ESU is installed. There is a process for identifying new tables and indexes at ESU creation time (i.e. when they are built into the ESU). ESU installation uses the information to create the new tables and indexes if they do not exist in the Business Data datasource for the target environment. Refer to <Document 957182.1> for more details.
UBE R98407 "Table and Index Creation" XJDE0001 version creates or regenerates all tables that are specified in the table change table (F9698710, F9698712). Page one of the report includes source, target, and environment information. Page two includes the overall status of the table creation in green or red text. Subsequent pages list the status of each table and index to be created or regenerated.
Note that this UBE will also run when you are upgrading your EnterpriseOne system to a higher application release level. The R98407 runs during the upgrade plan to generate new tables into the upgraded environment's datasources for those that are new to the new release (per the F9698710).
Note that when looking in the custom installation plan application, or in the workbench, this job can be referred to with or show as F0101.
Example of UBE R98407 XJDE0001 Page 1 details. In this case, user is installing EnterpriseOne 9.0 ASU Update 2 (UL2) patch :
Examples of UBE R98407 XJDE0001 Page 2 details containing UBE status. In the first case, R98407 completed successfully, no errors; in the second example, user is installing EnterpriseOne XE Update 8 (XU8) and the process completed successfully however there were some errors found for some tables or indexes:
Examples of UBE R98407 XJDE0001 Page 3 details containing tables and indexes details and status. In the first case, for the user installing E1 9.0 UL2 there are no errors and tables/indexes status are normal; in the second case, for the user installing E1 Xe XU8, as errors can be observed, for more error's details, start by cross reference these errors found with any possible error message in the jde.log and debug (if available) from your deployment server.
Table and Index Generation UBE R98407: Table Mappings and Generation for Software Updates
The Table and Index Creation UBE R98407 previously would create tables into the default datasource, Business Data, which could require some clean-up if the table is not intended to be in the Business Data datasource.
Solution: The process of adding new tables for any software updates (ESU or ASU) may utilize the R98407 process during the software update application process to generate the table(s). In some cases, the generation of the table will not be the correct location due to OCM mappings not being available for that table at the time of the R98407 process.
The default data source for your environment (usually Business Data - xxx) will then contain tables generated that are not used or required in the Business Data data source. Tables shipped with software updates that require a non default data source such as the System or Control Table data source will have manual special instructions to create a proper OCM mappings and generate the table in the correct location.
This will leave orphaned or unused tables in the Business Data data source that will need to be removed manually if desired. Please note that a majority of ESUs are application based and therefore the Business Data data source will be the correct location. This issue will normally only effect a certain type of table which is system related instead of application based.
Example -- A good example of this occurrence is with EnterpriseOne Xe ASU Update 8 (XU8) and the F98305V which attempts to generate into the Business Data data source during the R98407 process. In the special instructions however, the client is prompted to create an OCM mapping pointing to the Versions data source to regenerate the table in the correct location. In this case, you will still have an empty and unused F98305V in your Business Data data source.
The automation of OCM mapping creation at the time of new table generation is NOT resolved in EnterpriseOne Xe or ERP8.0 releases. This issue will be resolve in future releases.
NOTE : In the example above the AS400 DB2 databases are an exception in this case do to Translation settings on the Business Data data source which causes the F98305V to fail to generate in the Business Data data source -- therefore there would be no orphaned table to remove.
NOTE: The database data source that table(s) are to be created in, needs to point to the correct object owner/library/etc.
How to Reset the Status of the Table and Index Creation (R98407) to Success to Continue On With Software Update Installation
In this example, customer is applying an ASU patch, but the Table and Index Creation UBE (R98407) process fails on several new tables and changed indexes. Customer would like to set this to success (60) to continue on with the ASU install and then generate the tables and indexes manually later.
Solution: To correct this issue, follow these steps:
- On the Deployment Server, log into the JDEPLAN environment.
- Go to (GH9612) into the Software Updates application (Electronic for an ESU or Application for an ASU).
- Highlight and Select the ESU or ASU you are attempting to apply. Click Next.
- Highlight the desired environment. UNCHECK the Unattended Workbench checkbox (to place install in "Attended" Mode and allow the ESU install process to stop through the workbenches scheduled to run) and UNCHECK the Backup checkbox and the Create OMW Project checkbox. Click Next.
- Once the application stops (should be at the Table Conversion screen with the failed R98407), leave the screen up and return to the main menu screen.
- Go to menu GH961 and launch the Custom Installation Plan application.
- In the Custom Installation Plan -[Work with Installation Plans] (P98240/W98240B) form click Find.
- Expand the ESU or ASU's latest plan. Each time the ESU/ASU is run, a new project is created with a unique name by appending the project with the next sequential number, e.g. JL123-4. The highest number should match the project you are currently working with in the other window.
- Expand Base Location, the Location, Environments, and then the given environment, e.g. DV900. Set focus on Table Conversion and click Select.
- In the grid row for the environment, it should have a row where Table Name is F0101 and the Program Name as R98407. Focus in the Dtl Sts box on that grid row and use the Visual Assist to choose 60 (Installed). Click Save and return to the ESU/ASU application.
- Return to the active window for the Software Updates application and click the Back button until you get to the screen before the R98407.
- Click Next. If there is another process on the Table Conversions, it will stop there so you can complete any unprocessed conversions. If the R98407 was the only unsuccessfully processed job, the Software Updates application should move past it to the next workbench in the installation.
NOTE: Please note that in some cases, the customer issue got resolved after rerunning R98407.
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
|Overview of UBE R98407 and Examples of R98407 XJDE0001 PDF Results|
|Table and Index Generation UBE R98407: Table Mappings and Generation for Software Updates|
|How to Reset the Status of the Table and Index Creation (R98407) to Success to Continue On With Software Update Installation|
|Scenario 1 - F98611 Fetch Failed Error On R98407 (Table And Index Creation) When Applying ESU|
|Scenario 2 - EnterpriseOne 8.12 ASU UK3 Install, UBE R98407 Fails on UDB/DB2 Databases|
|Scenario 3 - During ESU Installation UBE R98407 Index Table Creation Fails Due to Incorrect CCSID - AS400 iSeries Platform Only|
|Scenario 4 - Applying Cumulative Update (ASU) - R98407 UBE Errors - JDB9900299 - Failed to Create Global Table Specs / JDB9900307 / JDB9900318 Errors|
|Scenario 5 - ASU Patch Install to an Environment Fails on Table and Index Creation UBE R98407 - JDB and Fatal System Error - JDB3300020 / JDB9900913 / JDB9900307 Errors|
|Scenario 6 - Errors Applying EnterpriseOne Xe ASU Update 8 (XU8) with AS/400 - R98407 and R98700 Errors|
|Issue 1: R98407 Errors Generating F9070* Tables|
|Issue 2: R98700 Errors on D8300003|
|Solution 1: R98407 Errors Generating F9070* Tables|
|Solution 2: R98700 Errors on D8300003|