Bug #54440 Enterprise Monitor should use MySQL server - 5.1.48

• Submitted: 11 Jun 2010 17:57
• Modified: 13 Jul 2010 10:57
• Reporter: Bill Weber
• Status: Closed
• Category: MySQL Enterprise Monitor: Installing
• Severity: S2 (Serious)
• Version: 2.2.2.1723
• OS: Any
• Assigned to: BitRock Merlin
• CPU Architecture: Any

[11 Jun 2010 17:57] Bill Weber

Description:
The Merlin Service Manager stack should be updated to use MySQL 5.1.47, which has a number of bug fixes that are important to us. Please remember to use the "Advanced" version that includes partitioning.

How to repeat:
n/a

[8 Jul 2010 13:27] BitRock Merlin

Patch sent to Andy.

[8 Jul 2010 22:10] Enterprise Tools JIRA Robot

Andy Bang writes: 
In build 2.2.2.1730.

[9 Jul 2010 19:30] Enterprise Tools JIRA Robot

Andy Bang writes: 
Also in build 2.3.0.2019.

[9 Jul 2010 21:27] Enterprise Tools JIRA Robot

Marcos Palacios writes: 
Verified mysqld is 5.1.48-enterprise-commercial-advanced on both builds 2.2.2.1730 and 2.3.0.2019 on Mac OS X.

[10 Jul 2010 14:40] Enterprise Tools JIRA Robot

Carsten Segieth writes: 
re-opening 'for me' to check the 2 Solaris for inst + upd in both builds

[10 Jul 2010 14:41] Enterprise Tools JIRA Robot

Carsten Segieth writes: 
build already exists

[10 Jul 2010 14:42] Enterprise Tools JIRA Robot

Carsten Segieth writes: 
in builds 2.2.2.1730 and 2.3.0.2019

[12 Jul 2010 12:07] Enterprise Tools JIRA Robot

Carsten Segieth writes: 
checked OK for Solaris for  2.2.2.1730 fresh install and  2.3.0.2019 update installers

[12 Jul 2010 19:12] Enterprise Tools JIRA Robot

Carsten Segieth writes: 
OK for 2.2.2.1730 update installers

[12 Jul 2010 21:59] Enterprise Tools JIRA Robot

Carsten Segieth writes: 
... and also the 2.3.0.2019 fresh installs on Solaris are OK (= using 5.1.48).

[13 Jul 2010 10:57] MC Brown

No changelog entry required