Bug 118511 – cms upgrade from 6.0.0 to 6.0.1 : bug in sql script update-bundle-type-id.sql

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 118511 - cms upgrade from 6.0.0 to 6.0.1 : bug in sql script update-bundle-type-id.sql

Summary:	cms upgrade from 6.0.0 to 6.0.1 : bug in sql script update-bundle-type-id.sql

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Enterprise CMS
Classification:	Retired
Component:	other (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	ccm-bugs-list
QA Contact:	Jon Orris
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	108447
	Show dependency tree / graph

Reported:	2004-03-17 03:42 EST by durnez
Modified:	2007-04-18 13:04 EDT (History)
CC List:	0 users

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

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description durnez 2004-03-17 03:42:28 EST

Description of problem:

when running :
cms/sql/default/upgrade/6.0.0-6.0.1/update-bundle-type-id.sql

and with a database having a content item with several pending instances, 
the following error occurs :
ERROR at line 1:
ORA-01427: single-row subquery returns more than one row

The reason why this exception occurs is because the inner query
retrieves several values when the content item has several pending
instances.

The solution is to replace in file
cms/sql/default/upgrade/6.0.0-6.0.1/update-bundle-type-id.sql
 :
> set type_id = (select i.type_id
by
> set type_id = (select distinct i.type_id

Version-Release number of selected component (if applicable):
CMS 6.0.0 (for upgrade to 6.0.1)

How reproducible:
always

Comment 1 Dennis Gregorovic 2004-03-17 14:05:45 EST

Thanks for catching this.  The changes have been checked in.

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