If so, the RPM does not install and produces a message explaining this.
Conflicts can arise when an RPM from another vendor is already installed, such as when a vendor's conventions about which files belong with the server and which belong with the client library differ from the breakdown used for Oracle packages.
This has the effect, for example, that accounts in the grant tables are not initialized to the default set of accounts.
PDF (US Ltr) - 27.1Mb PDF (A4) - 27.2Mb PDF (RPM) - 26.0Mb HTML Download (TGZ) - 6.5Mb HTML Download (Zip) - 6.5Mb HTML Download (RPM) - 5.6Mb Man Pages (TGZ) - 170.8Kb Man Pages (Zip) - 279.3Kb Info (Gzip) - 2.6Mb Info (Zip) - 2.6Mb My SQL Backup and Recovery My SQL NDB Cluster 7.2 My SQL Globalization My SQL Information Schema My SQL Installation Guide My SQL and Linux/Unix My SQL and OS X My SQL Partitioning My SQL Performance Schema My SQL Replication My SQL Restrictions and Limitations Security in My SQL My SQL and Solaris Building My SQL from Source Starting and Stopping My SQL My SQL Tutorial My SQL and Windows The recommended way to install My SQL on RPM-based Linux distributions is by using the RPM packages.
The RPMs that we provide to the community should work on all versions of Linux that support RPM packages and use package.
If any non-"eth#" names exist, the Content Gateway installer exits and provides a link to instructions for modifying system startup files.