Technical article 126471

How do I install and start to use MYSQL Pro Certified Server v5.0.17c or v4.1.16?

OpenServer 6.0.0UnixWare 7.1.4

Written · Last revised

Problem

How do I download and use MySQL Pro Certified Server 5.0.17c or 4.1.16 for OpenServer6?

Solution

You must purchase an appropriate MySQL Network Subscription Offering in order for you to be entitled to download and use MySQL Pro Certified Server.

Please note that the product is only supported on OpenServer6.

v5.0.17c is used as an example, later versions of MySQL should install in the same way.

It is assumed that no other MySQL has been installed.  If it has then
please stop it before upgrading the version.

Later versions such as 5.0.82 are also available.

For OpenServer6:
---------------
a.  Login and Download the software from the "Certified Software"
    section of:
https://network.mysql.com/
into /local/mysql.

For OpenServer6/UnixWare7 v5.0.17 and v4.1.16, it is recommended to download the appropriate "pkg".

You may need to run "mkdir -p /local/mysql".

b.  Un-gzip and un-tar the file downloaded.
mysql-pro-gpl-cert-5[1].0.17c-sco-osr6-i686.pkg.gz
or:
mysql-pro-gpl-cert-4[1].1.16-sco-osr6-i686.pkg.gz
c.  If you have installed using the OpenServer6 media prior to March
    2006, then MySQL is likely to have been installed at installation
    time.  If this is the case then run "custom" and from SCO
    OpenServer6 select Database Services and remove the 4.x version
    of MySQL currently installed.

It is assumed that the "gzip" package is installed.

d.  # cd /local/mysql
# gunzip mysql-pro-gpl-cert-5[1].0.17c-sco-osr6-i686.pkg.gz
or:
# gunzip mysql-pro-gpl-cert-4[1].1.16-sco-osr6-i686.pkg.gz
e.  Note the following changes to the default MySQL file locations:
Path to mysqlshow command     /opt/mysql/bin/mysqlshow
Path to mysqladmin command    /opt/mysql/bin/mysqladmin
Path to mysql command         /usr/bin/mysql
Path to mysqldump command     /opt/mysql/bin/mysqldump
Path to mysqlimport command   /opt/mysql/bin/mysqlimport
Command to start MySQL server /etc/rc2.d/S99mysql start
Command to stop MySQL server  /etc/rc0.d/K01mysql stop
Path to MySQL shared libraries directory  /usr/lib
Path to MySQL databases directory         /var/lib/mysql
UnixWare7:
---------
Follow the same steps for UnixWare7, however, UnixWare7 is currently not a supported platform for this version from MySQL or SCO.
To Install:
----------
1.  Create the MySQL user and groups with:
# groupadd mysql
# useradd -g mysql mysql
2.  Run the following commands:
For OpenServer6 and UnixWare7 you can use the "pkgadd" command:
--------------------------------------------------------------
# pkgadd -d /local/mysql/mysql-pro-gpl-cert-5[1].0.17c-sco-osr6-i686.pkg
or:
# pkgadd -d /local/mysql/mysql-pro-gpl-cert-4[1].1.16-sco-osr6-i686.pkg

If you did not create the "mysql" user and group first then you will get the following error:

This install requires that the user 'mysql' and group 'mysql' exists UX:pkginstall: ERROR: request script did not complete successfully

A successful install will report:
## Executing postinstall script.
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/opt/mysql/mysql/bin/mysqladmin -u root password 'new-password'
/opt/mysql/mysql/bin/mysqladmin -u root -h
tiger7.uk.sco.com password 'new-password'
See the manual for more instructions.
NOTE:  If you are upgrading from a MySQL <= 3.22.10 you should
       run the /opt/mysql/mysql/bin/mysql_fix_privilege_tables.
       Otherwise you will not be able to use the new GRANT
       command!
Please report any problems with the ./bin/mysqlbug script!

The latest information about MySQL is available on the web at http://www.mysql.com

Support MySQL by buying support/licenses at
https://order.mysql.com

Installation of MySQL Pro Certified Server (GPL) (mysql) was successful.

The MySQL root password is set automatically as part of the post installation, see above.

3.  Now ensure the server starts and stops at each boot time:
# cd /etc/init.d
# ln /etc/init.d/mysql /etc/rc2.d/S99mysql
# ln /etc/init.d/mysql /etc/rc0.d/K01mysql
4.  Start MySQL with:
# /etc/init.d/mysql start
5.  Check MySQL has started ok with:
# ps -ef | grep mysql
You should see:
     root  3220     1   TS  70  0 12:40:49 pts/1 0:00
/opt/mysql/mysql/bin/mysqld_safe --datadir=/var/lib/mysql --pid-file=/var/lib/m
6.  To run MySQL, run:
# mysql --version (or mysql -V)
mysql  Ver 14.12 Distrib 5.0.17c, for unknown-sysv5SCO_SV6.0.0 (i686)
using readline 5.0
or:
mysql  Ver 14.7 Distrib 4.1.16, for unknown-sysv5SCO_SV6.0.0 (i686) using
readline 4.3
7.  Run:
# mysql (/bin/mysql):
Welcome to the MySQL monitor.  Commands end with ; or \g.

Your MySQL connection id is 2 to server version: 5.0.17c-pro-gpl-cert or: Your MySQL connection id is 2 to server version: 4.1.16-pro-gpl-cert

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql>
Enter:
mysql> STATUS;
mysql> quit;
8.  Download the world.sql example database from:
http://dev.mysql.com/get/Downloads/Manual/world.sql.gz/from/pick
9.  At the mysql prompt enter:
mysql> CREATE DATABASE world;

10. There are two ways to import the MySQL Source SQL file:

Either from the shell run with:
mysql> quit<RETURN>   - ie. with or without the ;
or:
mysql> exit<RETURN>
# mysql world < world.sql

OR from within the MySQL client run:

mysql> USE world;
mysql> SOURCE world.sql;

NOTE: The opposite command to output or backup a database would be to use the "mysqldump" client program as:

mysql> mysqldump world > world.backup.sql

world.sql and world.backup.sql contain the same data but were produced from different MySQL databases with different mysqldump client programs so the file size and content is different.

NOTE: To import data into a table from a Comma Separated Value file,  for
      example, use the commands "LOAD DATA INFILE" or "mysqlimport" client
      program.
11.  Once loaded, within the MySQL client run "mysql":

mysql> USE world; mysql> SHOW tables; mysql> SELECT * from Country;

to see your first SELECT statement.

Press the UP and DOWN arrows to browse and change your most recent commands.

NOTE: the default line terminator is ";" which is the same as \g.

You can also use \G to change the format of the output.

TROUBLESHOOTING:
1.   For OpenServer6, to keep a link to the MySQL default locations:
# ln -s /opt/mysql/mysql /usr/local/mysql
2.   my.cnf

For new starters to MySQL is recommended to run MySQL with the safe updates option as "mysql --safe-updates".

This can be included in a $HOME or global /etc/my.cnf file as:

[client]
compress
[mysql]
safe-updates

Alternatively, use the my.cnf location defined in:

  mysql  3249  3220   TS  80  0 12:40:49 pts/1 0:00
/opt/mysql/mysql/bin/mysqld --defaults-extra-file=/opt/mysql/mysql/data/my.cnf
above.

Any changes made to the my.cnf file require you to stop and start MySQL;

# /etc/init.d/mysql restart

NOTE: The compress is an example to show that any clients connecting from other than localhost would use the session to send traffic over the network between clients/server for slower networks on port 3306.

3.    Syntax Error:
mysql> This is an invalid statement;

Will display the most common error message: ERROR 1064: You have an error in your SQL syntax.

4.    Checking a Database:

Use "mysqlcheck" and "myisamchk" to check the integrity of your database, for example:

# mysqlcheck world;
world.City                            OK
world.Country                         OK
world.CountryLanguage                 OK
# cd /usr/local/mysql/data/world
# myisamchk City
Checking MyISAM file: City
Data records:    4079   Deleted blocks:       0
        - check file-size
        - check record delete-chain
        - check key delete-chain
        - check index reference
        - check data record references index: 1
NOTE: that "mysqlcheck" is a client program (See CHECK & REPAIR TABLE) and so
      can be run when the database is running, whereas myisamchk is not a
      client program and performs operations on tables by accessing the table
      files directly.
5.    Disk Space
Your databases are created in /var/lib/mysql

It is recommended to store this on a separate filesystem, other than root to ensure the root filesystem does not become congested.

See: /etc/init.d/mysql.in to show an example of where the data directory is changed.

6.    MySQL comes with its own test suite.
/opt/mysql/mysql/mysql-test/README

It is suggested to run the tests as the "mysql" user.

./mysql-test-run --force

NOTE: Should the "rpl_rotate_logs" test fail then this is a known issue and is caused by running the tests as "root".

It can be resolved by removing the "var" directory in:

/opt/mysql/mysql/mysql-tests/var

and running the tests as the "mysql" user.

It is recommended to change the default "mysql" user in "scoadmin account" and change the default shell to /usr/bin/bash and then running:

# mkdir /home/mysql
# chown mysql:mysql /home/mysql
NOTE: MySQL may also offer a VOLS package format for OpenServer6.  Follow the
      instructions below to install if a package type is available:
mysql-pro-gpl-cert-5[1].0.17c-sco-osr6-i686.VOLS.gz
For OpenServer6 only (VOLS) package:
-----------------------------------
Run the commands listed in:
https://network.mysql.com/docs/README-SCO.txt as:
-----
The files:
mysql-pro-cert-5.0.17a-sco-osr6-i686.VOLS.tar
and:
mysql-pro-gpl-cert-5.0.17a-sco-osr6-i686.VOLS.tar

are tar archives of media images suitable for installation with the SCO Software Manager (/etc/custom) on SCO OpenServer 6.

The first, mysql-pro-cert-5.0.17a-sco-osr6-i686.VOLS.tar, is the Commercially licensed MySQL Pro Certified server.

The latter,mysql-pro-gpl-cert-5.0.17a-sco-osr6-i686.VOLS.tar, is the MySQL Pro Certified server licensed under the terms of the General Public License (GPL).

Select which of these you wish to install and, after download, extract the
tar archive into an empty directory.
For example:
# mkdir /tmp/mysql-pro
# cd /tmp/mysql-pro
# tar xf /tmp/mysql-pro-cert-5.0.17a-sco-osr6-i686.VOLS.tar

Prior to installation back up your data following the procedures outlined at:

http://dev.mysql.com/doc/refman/5.0/en/upgrade.html

Remove any previously installed pkgadd version of MySQL:

# pkginfo mysql 2>&1 > /dev/null && pkgrm mysql

Install MySQL Pro from media images using the SCO Software Manager:

# /etc/custom -p SCO:MySQL -i -z /tmp/mysql-pro

Alternatively, the SCO Software Manager can be displayed graphically by clicking on the "Software Manager" icon on the desktop, selecting "Software -> Install New", selecting the host, selecting "Media Images" for the Media Device, and entering /tmp/mysql-pro as the Image Directory.

After installation, run "mkdev mysql" as the root user to configure your newly installed MySQL Pro Certified server.

If you wish to configure your MySQL Pro server to interface with the Apache web server via PHP, download and install the PHP update from SCO at:

https://ftp.scoexpert.com/updates/OpenServer/SCOSA-2006.17/
------

See also

Support for MySQL

To obtain full support for MySQL version 4.1 and 5.0 from SCO on OpenServer6 visit MySQL Network at:

http://www.mysql.com/network/
http://www.sco.com/products/openserver6/mysql.html
FAQ:      Q. How many editions of MySQL are available?

A. Community Version and Pro Certified Software (Commercial) and the OEM Version.

http://www.mysql.com/products/database/mysql/which-edition.html

Q. Are there any differences in the commercial version shipped?

A. Classic and Pro

Q. What is the difference between MySQL Classic and MySQL Pro?

A. MySQL Classic includes support for the MyISAM storage engine. MySQL Pro includes support for the MyISAM and the InnoDB storage engine.

Both Classic and Pro licenses are shipped under a commercial license.

A commercial license allows the redistribution of the MySQL Database as part of your solution without having to opensource your solution.

Pro will be the version downloadable via MySQL Network.

Q. When I log in to MySQL Network I can see later Pro Server versions, different from the Certified ones, can I download and use these?

A. Yes, but these versions have not been certified yet but are supported.

Q. Are OEM, MySQL Cluster and MaxDB versions supported?

A. Contact SCO Sales in your region to discuss availability.

For information on MySQL's Support policies and products visit:

http://www.mysql.com/company/legal/supportpolicies/

Q. Are later, 5.1, 5.4 and 6.0 versions supported?

A. Visit MySQL's Enterprise Supported matrix website at:

http://www.mysql.com/support/supportedplatforms/enterprise.html

From the Xinuos technical article database, record 126471. Reproduced with permission. The original is at www.sco.com/ta/126471, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.