Bug 1020477 - While upgrading Satellite server, schema upgrade fails at "drop index rhn_errataclone_teid_feid_idx" with error "ORA-02429: cannot drop index used for enforcement of unique/primary key"
While upgrading Satellite server, schema upgrade fails at "drop index rhn_err...
Status: NEW
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Upgrades (Show other bugs)
Unspecified Unspecified
medium Severity urgent
: ---
: ---
Assigned To: Tomáš Kašpárek
Red Hat Satellite QA List
Depends On:
Blocks: sat560-triage
  Show dependency treegraph
Reported: 2013-10-17 14:14 EDT by Xixi
Modified: 2016-05-12 11:03 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 228683 None None None Never

  None (edit)
Description Xixi 2013-10-17 14:14:27 EDT
Description of problem:

While upgrading satellite server schema from Satellite with external Oracle database to version 5.6, schema upgrade failed with:


drop index rhn_errataclone_teid_feid_idx
ERROR at line 1:
ORA-02429: cannot drop index used for enforcement of unique/primary key

Version-Release number of selected component (if applicable):
Satellite 5.6

How reproducible:
(uncertain, like with the other similar bugs (987183, 877299, or 875672) the error occurs with only some external Oracle instances, and not yet replicated in-house)

Steps to Reproduce:
1. Upgrade Satellite 5.3 with external Oracle database to Satellite 5.6

Actual results:
Fails with error above.

Expected results:

Additional info:
This is similar to the other known issues for similar indexes (rhn_eclonedtmp_teid_feid_idx, rhn_ug_id_name_org, rhn_sg_id_oid_name_idx), please refer to Knowledgebase solution for details and workaround https://access.redhat.com/site/solutions/228683

Please note that if customer is running into the same ORA-02429 error but with another object not listed on the above solution, file a new Bugzilla from the support case so it can be looked into, confirmed whether the same workaround applies, and addressed properly.

Note You need to log in before you can comment on or make changes to this bug.