Bug 154447 - Satellite schema upgrade 3.6-215->3.7 results in errors.
Satellite schema upgrade 3.6-215->3.7 results in errors.
Status: CLOSED NOTABUG
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Other (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: James Slagle
Red Hat Satellite QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-11 15:22 EDT by Steve Conklin
Modified: 2007-10-23 22:17 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-04-11 22:11:00 EDT
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 Steve Conklin 2005-04-11 15:22:50 EDT
Description of problem:
Errors during upgrade of 3.6 satellite to 3.7

During an upgrade from schema version 3.6-199 to 3.7, the first two schema
upgrade scripts ran without errors, bring the schema version to 3.6-215.

While running the last sql script, the following errors were seen:

				Table altered.


				Warning: Package Body created with
compilation errors.

				Errors for PACKAGE BODY RHN_BEL:

				LINE/COL ERROR
				--------
-----------------------------------------------------------------
				3/11     PLS-00323: subprogram or cursor
'FIND_STATE_OF_ORG' is declared
				         in a package specification and
must be defined in the package
				         body

				6/11     PLS-00323: subprogram or cursor
'IS_STATE_LEGACY_UNCLASSIFIED' is
				         declared in a package
specification and must be defined in the
				         package body

				15/11    PLS-00323: subprogram or cursor
'LOOKUP_ORG_STATE' is declared in
				         a package specification and
must be defined in the package body


				LINE/COL ERROR
				--------
-----------------------------------------------------------------
				18/12    PLS-00323: subprogram or cursor
'VALIDATE_ORG_STATE_CHANGE' is
				         declared in a package
specification and must be defined in the
				         package body

				22/12    PLS-00323: subprogram or cursor
'JOIN_RHN' is declared in a
				         package specification and must
be defined in the package body

				25/12    PLS-00323: subprogram or cursor
'SET_ORG_PAID' is declared in a
				         package specification and must
be defined in the package body

				28/12    PLS-00323: subprogram or cursor
'SET_ORG_UNPAID' is declared in a

				LINE/COL ERROR
				--------
-----------------------------------------------------------------
				         package specification and must
be defined in the package body


				Package body created.

				No errors.

				Warning: Package Body created with
compilation errors.

				Errors for PACKAGE BODY RHN_CONFIG:

				LINE/COL ERROR
				--------
-----------------------------------------------------------------
				8/11     PLS-00323: subprogram or cursor
'INSERT_REVISION' is declared in
				         a package specification and
must be defined in the package body


				View created.


				Table altered.


				Procedure created.

				No errors.

				Table altered.
Comment 1 Steve Conklin 2005-04-11 15:24:15 EDT
The customer says that during their upgrade to sat3.6, they also had errors and
had to run some custom sql. I will try to determine from them why they have
customizations, and whether they can be removed.
Comment 2 Steve Conklin 2005-04-11 15:32:52 EDT
The customer says that they aren't using any db customizations that they are
aware of. They have been running monitoring for about a week.
Comment 4 Steve Conklin 2005-04-11 22:09:52 EDT
According to information from RHN engineering, these aren't fatal and can be
ignored as long as the script completed.

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