Error 'Seed data table must have a unique index' in section 32 GSCC reports
(Doc ID 2774084.1)
Last updated on JUNE 12, 2023
Applies to:
EMEA Add-on Localizations - Version 12.2 and laterInformation in this document applies to any platform.
Symptoms
Reported Issue
--------------------
On upgrading to R12.2.X environment from R12.2.X and running the Global Standard Compliance Checker (GSCC) report an error
is observed under section - 32.
Error message in section - 32
--------------------------------------
DOC> **********************************************************************
DOC> SECTION-32 [full]
DOC> **********************************************************************
DOC> "Seed Data Table must have a unique index."
DOC>
DOC> - P2: Run Edition updates to these tables will not be synchronized to the
DOC> Patch Edition if these tables are loaded during online patching.
DOC> - This violation can be ignored if the table is "Read-Only" for the runtime
DOC> application. To remove read-only tables from this report, please log a
DOC> bug with AD (166/OP).
DOC> Note: This check only works after Online Patching Enablement.
DOC>#
OWNER TABLE_NAME
---------------- ------------------------------
CLE CLE_FA_METHODS_EXT
CLE CLE_PF_COL_NAMES
OWNER TABLE_NAME
---------------- ------------------------------
CLE CLE_FA_METHODS_EXT
CLE CLE_PF_COL_NAMES
Steps for replication
--------------------------
The issue can be reproduced at will with the following steps:
1. Run GSCC report on the upgraded instance .
2. An error is observed under section -32.
Expected behavior
-----------------------
As this reports is about compliance wanted clarification over the next steps
wherein to address this error further.
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 |