My Oracle Support Banner

E1: UPG: INST: Information and Troubleshooting Known Issues For UBEs R9698711 And R9698713 (Doc ID 642925.1)

Last updated on MARCH 11, 2023

Applies to:

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


This knowledge document is designed to direct you through understanding the purpose and troubleshooting known issues on UBE R9698711 (Compare Tables and Indexes Against Central Objects or TAM Specifications) and UBE R9698713 (Index Recreation) mostly during a EnterpriseOne Application Release Software Upgrade. Note that these UBEs can be also run for EnterpriseOne Installations.

The knowledge provided is not meant to be as a substitute for the Install or Upgrade Guides, but as an aid for better understanding and troubleshooting UBEs R9698711 and R9698713 issues during an E1 Software Upgrade or during an E1 Installation.

The knowledge included in this document is meant for users that have a basic understanding of the Install / Upgrade process and have read the Upgrade Guides.
Refer to <Document 705521.1> JD Edwards EnterpriseOne Applications Release 9.0 Upgrade Guides, Update.
Refer to <Document 705463.1> JD Edwards EnterpriseOne Applications Release 9.0 Installation Guides, Update.

Refer to this link here for JD Edwards EnterpriseOne Applications Release 9.1.x Installation and Upgrade Documentation.

Refer to this link here for JD Edwards EnterpriseOne Applications Release 9.2.x Installation and Upgrade Documentation.

R9698711 (Compare Tables and Indexes Against Central Objects or TAM Specifications UBE)

You can run the R9698711 UBE program from Batch Versions after an install or upgrade. The report compares database tables and indexes against Release 9.0 Central Objects or TAM specifications. Use this report to verify the format of Application Release 9.0 tables in your database.
The "Understanding Table Format Verification" section of the upgrade guides provides some instruction for setting the Data Selection before you run the UBE.

R9698713 (Index Recreation UBE)

This report is for installation, upgrade and cumulative update customers.
The R9698713 program is run from Batch Versions after an install or upgrade. It compares database indexes versus Application Release 9.0 index specifications in F98712 and F98713. If you run the program in Update mode, it recreates incorrect indexes.

Troubleshooting Steps

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
Troubleshooting Steps
 Install Or Upgrade Information Which Include Info On UBEs R9698711 and/or R9698713 
 Troubleshooting Known Issues with UBE R9698711
 Scenario 1 - During An EnterpriseOne Software Upgrade, Getting Blank Processing Options for R9698711
 Scenario 2 - "List tables that differ from EnterpriseOne Specs" UBE R9698711 Reports Many Index Mismatches Between the Tables and the Specifications
 Scenario 3 - Running UBE R9698711 After Upgrade Showing 900+ "Spec Mismatch" Differences
 Scenario 4 - Post Upgrade Tables Differ From Specs - UBE R9698711
 Scenario 5 - Details On R9698711 UBE To Verify Table Formats After Upgrading to EnterpriseOneXe - Also Migration And Coexistence Customers
 Scenario 6 - R9698711 Unknown error in DESCRIBE for table
 Scenario 7 - R9698711 Failing with “Specifications for table not found in environment: PY910” 
 Troubleshooting Known Issues with UBE R9698713
 Scenario 1 - R9698713 Failed Creating Indexes - OS400QL017 "SQL0804 - SQLDA not valid" Errors - AS400 Platform
 Scenario 2 - OS400QL017 - SQL0904 - Resource Limit Exceeded Error On R9698713 UBE To Create Indexes - AS400 Platform
 Scenario 3 - R9698713 Failing - F9201, F9204, F9205 'Table not in Data Source' Errors
 Scenario 4 - R9698713 Failure -  "Create Single Index 1 failed".
 Scenario 5 - R9698713 prompts "Unable to connect to E1LOCAL" after upgrading to tools release 9.2.5.xand later
 Scenario 6 - R9698713 fails with error message "The primary key constraint 'F0150_PK' on table 'F0150' cannot be dropped because change tracking is enabled on the table. Change tracking requires a primary key constraint on the table. Disable change"
 Other Known Issues Involving UBEs R9698711 and/or R9698713

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