MySQL Bugs: #19376: Missing RPMs

Bug #19376	Missing RPMs
Submitted:	26 Apr 2006 15:20	Modified:	3 Aug 2006 12:04
Reporter:	Clinton Watson	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MaxDB	Severity:	S3 (Non-critical)
Version:	7.6.00.16	OS:	Linux (RedHat ES4)
Assigned to:		CPU Architecture:	Any

Description:
We have recently installed a RHEL 4 box with MaxDB 7.6.00.16 to replace a Fedora Core box using MaxDB 7.5.00.24.

Upon installation we discovered that the package SDBKRN.TGZ was missing files that we required, that have apparently been moved to client packages for Perl and Python. This wouldn't have been a large issue, however the RedHat server was installed using RPMs, and the files are missing from the RPM builds and there does not appear to be any client RPMs available to install the Perl, Python or DevTools packages.

Was this intentional? I.E., this will be the case from now on? Or was it an oversite? If this is to be the case in the future, will there be RPM releases for the client packages?

Thanks

How to repeat:
N/A

Hey there Clinton,

http://dev.mysql.com/downloads/maxdb/7.6.00.html#Linux_x86_RPM

I don't know if it was fixed for 7.6.00.16, but they're there for 7.6.00.27, the next release.

Let me know if this doesn't do it for you.

Cheers,

C.J.

This is a bug and is currently being resolved by SAP.  One work around might be to remove NULL values from the result set using something like

WHERE s_eventtaskhistorymaster.indexid IS NOT NULL AND s_eventtaskhistorydetail.indexid IS NOT NULL

Let me know if this works until the bug is resolved.

Please, check newer version, 7.6.00.27, and inform about the results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".