Legal Notice

Abstract

Chapter 1. Red Hat Software Collections 1.0

Chapter 2. Installation and Usage

Important

1. Display a list of all channels that are available to you and determine the exact name of the Red Hat Software Collections channel. To do so, type the following at a shell prompt asroot:

   rhn-channel --available-channels

   The name of the channel depends on the specific version of Red Hat Enterprise Linux you are using and is in therhel-x86_64-variant-6-rhscl-1 format, wherevariant is the Red Hat Enterprise Linux system variant (server orworkstation).
2. Subscribe the system to the Red Hat Software Collections channel by running the following command asroot:

   rhn-channel --add --channel=channel_name

   Replacechannel_name with the name you determined in the previous step.
3. Verify the list of channels you are subscribed to. Asroot, type:

   rhn-channel --list

1. Display a list of all subscriptions that are available for your system and determine the pool ID of a subscription that provides Red Hat Software Collections. To do so, type the following at a shell prompt asroot:

   subscription-manager list --available

   For each available subscription, this command displays its name, unique identifier, expiration date, and other details related to it. The pool ID is listed on a line beginning withPool Id.
2. Attach the appropriate subscription to your system by running the following command asroot:

   subscription-manager subscribe --pool=pool_id

   Replacepool_id with the pool ID you determined in the previous step. To verify the list of subscriptions your system has currently attached, run asroot:

   subscription-manager list --consumed

3. Display the list of available Yum list repositories to retrieve repository metadata and determine the exact name of the Red Hat Software Collections repositories. Asroot, type:

   yum repolist all

   The repository names depend on the specific version of Red Hat Enterprise Linux you are using and are in the following format:

   rhel-variant-rhscl-6-rpmsrhel-variant-rhscl-6-debug-rpmsrhel-variant-rhscl-6-source-rpms

   Replacevariant with the Red Hat Enterprise Linux system variant, that is,server orworkstation. Note that Red Hat Software Collections is not supported on theClient variant.
4. Enable the appropriate repository by running the following command asroot:

   yum-config-manager --enablerepository

Important

• Starting with MySQL 5.5, the InnoDB storage engine (formerly known as InnoDB Plugin) is the default storing engine.
• InnoDB and some other plug-ins (for example, archive, blackhole and federated) were installable plug-ins in MySQL 5.1. Starting with MySQL 5.5, these plug-ins became compiled-in storage engines, that is, they do not have to be installed nor uninstalled.
• If you used InnoDB Plugin and it was loaded using theplugin-load=innodb=ha_innodb_plugin.so configuration option, you need to remove this configuration option as it does not work in MySQL 5.5.
• In MySQL 5.1, InnoDB Plugin included a configuration variableinnodb_file_io_threads. However, this variable does not exist in MySQL 5.5; new variables,innodb_read_io_threads andinnodb_write_io_threads, are used instead. To ensure proper functionality, either remove the former variable from the configuration file or replace it with the current variables.
• When upgrading from MySQL 5.1 to MySQL 5.5 using the in-place upgrading method, themysql.proxies_priv table will not exist. To create the missing table, themysql_upgrade utility has to be run as soon as the new daemon is started.
• MySQL 5.5 uses latin1 for thestopword file if thecharacter_set_server variable is ucs2, utf16 or utf32. Thus, if the table uses FULLTEXT indexes in these cases, users should repair the table using theREPAIR TABLEtable_name QUICK.
• MySQL 5.1 used thelanguage variable for specifying the directory which included the error message file. This option is now deprecated and has been replaced by thelc_messages_dir andlc_messages options. This also applies for configuration options. Also, error messages no longer contain mixed set of character sets and error messages are returned in the set following thecharacter_set_results system variable instead. That is, some error messages can be different in MySQL 5.5.

• In the first scenario, the whole dump of all databases from one database is generated,mysql is run with the dump file as an input, usingmysqlimport or theLOAD DATA INFILE SQL command whithin the other database. At the same time, the appropriate daemons have to be running during both dumping and restoring. You can use the--all-databases option in the mysqldump call to include all databases in the dump. The--routines,--triggers and--events options can also be used if needed.
• During the in-place upgrade, the data files are copied from one database directory to another database directory. The daemons should not be running at the time of copying. Set the appropriate permissions and SELinux context for copied files.

Example 2.1. Dump and Restore Upgrade

~]#service mysqld startStarting mysqld:                                           [  OK  ]~]#mysqldump --all-databases --routines --events > dump.sql~]#service mysqld stopStopping mysqld:                                           [  OK  ]~]#service mysql55-mysqld startStarting mysql55-mysqld:                                   [  OK  ]~]#scl enable mysql55 'mysql' < dump.sql~]#scl enable mysql55 'mysql_upgrade'Looking for 'mysql' as: mysqlLooking for 'mysqlcheck' as: mysqlcheckRunning 'mysqlcheck with default connection argumentsRunning 'mysqlcheck with default connection argumentsa.t1                                               OKmysql.columns_priv                                 OK<skipped tables list>mysql.user                                         OKRunning 'mysql_fix_privilege_tables'...OK

Example 2.2. In-place Upgrade

~]#service mysqld stopStopping mysqld:                                           [  OK  ]~]#service mysql55-mysqld stopStopping mysql55-mysqld:                                   [  OK  ]~]#rm -rf /opt/rh/mysql55/root/var/lib/mysql/~]#cp -r /var/lib/mysql/ /opt/rh/mysql55/root/var/lib/mysql/~]#chown -R mysql:mysql /opt/rh/mysql55/root/var/lib/mysql/~]#restorecon -R /opt/rh/mysql55/root/var/lib/mysql/~]#service mysql55-mysqld startStarting mysql55-mysqld:                                   [  OK  ]~]#scl enable mysql55 'mysql_upgrade'Looking for 'mysql' as: mysqlLooking for 'mysqlcheck' as: mysqlcheckRunning 'mysqlcheck with default connection argumentsRunning 'mysqlcheck with default connection argumentsa.t1                                               OKmysql.columns_priv                                 OK<skipped tables list>mysql.user                                         OKRunning 'mysql_fix_privilege_tables'...OK

• The following server configuration parameters have been removed and are no longer supported:add_missing_from,regex_flavor,silent_mode,wal_sender_delay, andcustom_variable_classes. Do not use any of these parameters in the new configuration file.
• Theunix_socket_directory parameter has been renamed tounix_socket_directories and can now be used to specify more than one UNIX socket to listen on. To do so, provide a list of comma-separated directories as the value of this option. The default value remains unchanged and is/tmp.
• New configuration parametersssl_ca_file,ssl_cert_file,ssl_crl_file, andssl_key_file have been added. These configuration parameters can be used to specify the locations of server-side SSL files that were previously hard-coded as relative paths to theroot.crt,server.crt,root.crl, andserver.key files in the data directory.
  Note that the PostgreSQL server no longer reads theroot.crt androot.crl files by default. To load these files, change the corresponding parameters to non-default values.
• The=> operator has been removed and users are now advised to use thehstore(text, ,text) function.
• The default value of thestandard_conforming_strings configuration parameter is nowon. This configuration parameter controls if ordinary string literals (strings enclosed in single quotes) treat backslashes literally as specified in the SQL standard.
• A new configuration parameter,backslash_quote, has been added. This configuration parameter can be used to control whether a single quotation mark can be represented by\' in string literals. The default value issafe_encoding, which permits the use of\' only when the client encoding does not allow ASCII backslashes in multi-byte characters. As a consequence,\' can now be interpreted differently only in specific cases and only in string literals that do not conform to standards, including escape string syntax,E'value'.
• PostgreSQL 9.0 introduced access privileges for large objects. Consequently, a new configuration parameter,lo_compat_privileges, has been added to allow you to disable security checks related to the large objects affected by this change. To disable these security checks, change the value of this configuration parameter toon. The default value isoff.

Procedure 2.1. Performing In-place Upgrade

1. Stop the old PostgreSQL server to ensure that the data is not in an inconsistent state. To do so, type the following at a shell prompt asroot:

   service postgresql stop

   To verify that the server is not running, type:

   service postgresql status

2. Verify that the new data directory located in/opt/rh/postgresql92/root/var/lib/pgsql/data/ does not exist:

   file /opt/rh/postgresql92/root/var/lib/pgsql/data/

   If you are running a fresh installation of PostgreSQL 9.2, this directory should not be present in your system. If it is, back it up by running the following command asroot:

   mv /opt/rh/postgresql92/root/var/lib/pgsql/data{,-scl-backup}

3. Copy the old database data to the new location by typing the following at a shell prompt asroot:

   cp -ra /var/lib/pgsql/data/ /opt/rh/postgresql92/root/var/lib/pgsql/

4. Open the/opt/rh/postgresql92/root/var/lib/pgsql/data/pg_hba.conf configuration file and verify that thepostgres user is allowed to connect to the PostgreSQL server fromlocalhost without a password. If not, you can edit this file and temporarily set the authentication method for thepostgres user totrust orident. For a detailed description of thepg_hba.conf file and a complete list of available configuration options, see theofficial documentation.
5. Upgrade the database data for the new server by running the following command asroot:

   service postgresql92-postgresql upgrade

   It is recommended that you read the resulting/opt/rh/postgresql92/root/var/lib/pgsql/pgupgrade.log log file to see if there were any problems with the upgrade.
6. Start the new server asroot:

   service postgresql92-postgresql start

   It is also advised that you run theanalyze_new_cluster.sh script as follows:

   su - postgres -c 'scl enable postgresql92 ~/analyze_new_cluster.sh'

7. Optionally, you can configure the PostgreSQL 9.2 server to start automatically at boot time. To disable the old PostgreSQL 8.4 server, run the following command asroot:

   chkconfig postgresql off

   To enable the PostgreSQL 9.2 server, type asroot:

   chkconfig postgresql92-postgresql on

Procedure 2.2. Performing a Dump and Restore Upgrade

1. Ensure that the old PostgreSQL server is running by typing the following at a shell prompt asroot:

   service postgresql start

2. Dump all data in the PostgreSQL database into an SQL file. Asroot, type:

   su - postgres -c 'pg_dumpall > ~/pgdump_file.sql'

3. Stop the old server by running the following command asroot:

   service postgresql stop

4. Initialize the data directory for the new server asroot:

   service postgresql92-postgresql initdb

5. Start the new server asroot:

   service postgresql92-postgresql start

6. Import data from the previously created SQL file:

   su - postgres -c 'scl enable postgresql92 "psql -f ~/pgdump_file.sql postgres"'

7. Optionally, you can configure the PostgreSQL 9.2 server to start automatically at boot time. To disable the old PostgreSQL 8.4 server, run the following command asroot:

   chkconfig postgresql off

   To enable the PostgreSQL 9.2 server, type asroot:

   chkconfig postgresql92-postgresql on

Chapter 3. Additional Resources

Revision History