E1: UPG: Problem With Table Constraints After Unicode Conversion
(Doc ID 1552993.1)
Last updated on NOVEMBER 22, 2019
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
Upgrade from XE to E9.1 TR 220.127.116.11
After running the Unicode Conversion during an Upgrade from XE to E9.1, the indexes on the tables are not in the same order as they were in their XE installation. The stored procedure OWTBLCONV seems to be causing this issue. The method for creating the table constraints has a code portion as follows:
sql_stmt2 := 'SELECT COLUMN_NAME FROM SYS.ALL_CONS_COLUMNS WHERE OWNER = :1 AND CONSTRAINT_NAME = :2';
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