Bug 500432 - rhn-manage-channel-internal fails with oracle error
rhn-manage-channel-internal fails with oracle error
Status: CLOSED EOL
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Content Tools (Show other bugs)
RHN Stable
All Linux
low Severity medium
: ---
: ---
Assigned To: rhn-dev-list
Red Hat Network Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-05-12 12:53 EDT by Daniel Mach
Modified: 2017-07-05 11:15 EDT (History)
3 users (show)

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


Attachments (Terms of Use)

  None (edit)
Description Daniel Mach 2009-05-12 12:53:42 EDT
When we ran rhn-manage-channel-internal to create new channels, it failed several times.
When the command was ran for second time, it created couple more channels and failed again.

I believe there's a bug in the server code that prevents client scripts from working correctly.


Error Message:
    ORA-00001: unique constraint (RHN.RHN_DCM_UQ) violated
Error Class Code: 23
Error Class Info: Could not update database entry.

$ rhn-manage-channel-internal --username=rhel-admin --server=stage --create --csv=...

Channel rhel-i386-as-4.8.z already exists (use --update to update it)
Creating channel rhel-i386-as-4.8.z-cluster
  Channel rhel-i386-as-4.8.z-cluster created
Creating channel rhel-i386-as-4.8.z-extras
  Channel rhel-i386-as-4.8.z-extras created
Creating channel rhel-i386-as-4.8.z-gfs
  Channel rhel-i386-as-4.8.z-gfs created
Creating channel rhel-i386-es-4.8.z
  Channel rhel-i386-es-4.8.z created

Error Message:
    ORA-00001: unique constraint (RHN.RHN_DCM_UQ) violated
Error Class Code: 23
Error Class Info: Could not update database entry.

$ rhn-manage-channel-internal --username=rhel-admin --server=stage --create --csv=...
Red Hat Network password:
Channel rhel-i386-as-4.8.z already exists (use --update to update it)
Channel rhel-i386-as-4.8.z-cluster already exists (use --update to update it)
Channel rhel-i386-as-4.8.z-extras already exists (use --update to update it)
Channel rhel-i386-as-4.8.z-gfs already exists (use --update to update it)
Channel rhel-i386-es-4.8.z already exists (use --update to update it)
Creating channel rhel-i386-es-4.8.z-cluster
  Channel rhel-i386-es-4.8.z-cluster created
Creating channel rhel-i386-es-4.8.z-extras
  Channel rhel-i386-es-4.8.z-extras created
Creating channel rhel-i386-es-4.8.z-gfs
  Channel rhel-i386-es-4.8.z-gfs created
Creating channel rhel-ia64-as-4.8.z
  Channel rhel-ia64-as-4.8.z created

Error Message:
    ORA-00001: unique constraint (RHN.RHN_DCM_UQ) violated
Error Class Code: 23
Error Class Info: Could not update database entry.
Comment 2 Thomas "Shea" DeAntonio 2017-07-05 11:15:23 EDT
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).
Comment 3 Thomas "Shea" DeAntonio 2017-07-05 11:15:34 EDT
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).

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