sdkp1-release-notes-slesRecommended update for release-notes-slesRecommended update for release-notes-slesLTC Owner is: jon.thomas@us.ibm.com LTC Originator is:
mjwolf@us.ibm.com
---Problem Description--- customer upgraded from sles9 to
sles10, in doing that the customer also upgraded MySQL
from 4.x to 5.x. However, the customer did not migrate
the database they expected it to just work. When they ran
the database they would get segfaults approximately every
5 secs.
The fix was to migrate the data
Contact Information = mjwolf@us.ibm.com
Machine Type = pseries
---Steps to Reproduce--- load sles 9 on a platform setup
and populate a mysql database upgrade system to sles 10
stress the database by running queries
---Documentation Component Data--- Userspace tool common
name: mysql
Documentation version: unknown
The userspace tool has the following bit modes: 32 bit
Userspace rpm: mysql-4.0.18-32.20.ppc.rpm
Did you/they already check the documentation for these
issues? What version of sles9 did they upgrade from?
I am trying to find out. I have sent some emails but no
responses on what the customer used for documentation
during the upgrade
sent Denis Roy at eclipse.org another email asking for the
version or pdf of the upgrade documentation used
the response from Denis Roy at eclipse.org
"Actually, the documentation I was referring to was the
'readme', or release notes, that you see in the final step
of the SLES 10 upgrade (in YaST). That readme/release
notes talks about upgrade issues from PHP4 to 5, but does
not talk about upgrade issues from MySQL 4 to 5. I
honestly don't believe this is a Power-specific issue."
Mike - sorry, this is stale. They still looking for
something? What I see seems to imply a MySQL migration,
but the SLES pdfs don't specifically address.
The site that reported the problem is fine. The bug is
really about documentation and is it clear that the mysql
data needs to be migrated when updating versions of sles.
On the latest version of mysql in maintweb
(mysql-5.0.18-20.8.i586.rpm), the mysql README file
indicates that one should read the upgrade section within
the online docs. However, the README.SuSE file does not
mention the need to migrate the database.
..also, documentation indicating the need to migrate mysql
databases is not within:
release-notes-sles-10-43.30.i586.rpm
LTC Owner is: jon.thomas@us.ibm.com LTC Originator is:
mjwolf@us.ibm.com
---Problem Description--- customer upgraded from sles9 to
sles10, in doing that the customer also upgraded MySQL
from 4.x to 5.x. However, the customer did not migrate
the database they expected it to just work. When they ran
the database they would get segfaults approximately every
5 secs.
The fix was to migrate the data
Contact Information = mjwolf@us.ibm.com
Machine Type = pseries
---Steps to Reproduce--- load sles 9 on a platform setup
and populate a mysql database upgrade system to sles 10
stress the database by running queries
---Documentation Component Data--- Userspace tool common
name: mysql
Documentation version: unknown
The userspace tool has the following bit modes: 32 bit
Userspace rpm: mysql-4.0.18-32.20.ppc.rpm
Did you/they already check the documentation for these
issues? What version of sles9 did they upgrade from?
I am trying to find out. I have sent some emails but no
responses on what the customer used for documentation
during the upgrade
sent Denis Roy at eclipse.org another email asking for the
version or pdf of the upgrade documentation used
the response from Denis Roy at eclipse.org
"Actually, the documentation I was referring to was the
'readme', or release notes, that you see in the final step
of the SLES 10 upgrade (in YaST). That readme/release
notes talks about upgrade issues from PHP4 to 5, but does
not talk about upgrade issues from MySQL 4 to 5. I
honestly don't believe this is a Power-specific issue."
Mike - sorry, this is stale. They still looking for
something? What I see seems to imply a MySQL migration,
but the SLES pdfs don't specifically address.
The site that reported the problem is fine. The bug is
really about documentation and is it clear that the mysql
data needs to be migrated when updating versions of sles.
On the latest version of mysql in maintweb
(mysql-5.0.18-20.8.i586.rpm), the mysql README file
indicates that one should read the upgrade section within
the online docs. However, the README.SuSE file does not
mention the need to migrate the database.
..also, documentation indicating the need to migrate mysql
databases is not within:
release-notes-sles-10-43.30.i586.rpm
recommendedrelease-notes-slesx86_6422ac510b640e43312ca3f8dc1f39e481977e805a