Oracle 5.0, Reference Manual

Page: 382 / 3232

mysqlmanager
— The MySQL Instance Manager
362
After you set up a password file for the MySQL Instance Manager and Instance Manager is running,
you can connect to it. The MySQL client/server protocol is used to communicate with the Instance
Manager. For example, you can connect to it using the standard
mysql
client program:
shell> mysql --port=2273 --host=im.example.org --user=mysql --password
Instance Manager supports the version of the MySQL client/server protocol used by the client tools and
libraries distributed with MySQL 4.1 or later, so other programs that use the MySQL C API also can
connect to it.
4.6.10.7. MySQL Instance Manager Commands
Important
MySQL Instance Manager is been deprecated in MySQL 5.1 and is removed in
MySQL 5.5.
After you connect to MySQL Instance Manager, you can issue commands. The following general
principles apply to Instance Manager command execution:
• Commands that take an instance name fail if the name is not a valid instance name.
• Commands that take an instance name fail if the instance does not exist.
• Instance Manager maintains information about instance configuration in an internal (in-memory)
cache. Initially, this information comes from the configuration file if it exists, but some commands
change the configuration of an instance. Commands that modify the configuration file fail if the file
does not exist or is not accessible to Instance Manager.
• On Windows, the standard file is
my.ini
in the directory where Instance Manager is installed. On
Unix, the standard configuration file is
/etc/my.cnf
. To specify a different configuration file, start
Instance Manager with the
--defaults-file
[356] option.
• If a
[mysqld]
instance section exists in the configuration file, it must not contain any Instance
Manager-specific options (see Section 4.6.10.2, “MySQL Instance Manager Configuration Files” ).
Therefore, you must not add any of these options if you change the configuration for an instance
named
mysqld
.
The following list describes the commands that Instance Manager accepts, with examples.
•
START INSTANCE instance_name
This command attempts to start an offline instance. The command is asynchronous; it does not wait
for the instance to start.
mysql> START INSTANCE mysqld4;
Query OK, 0 rows affected (0,00 sec)
•
STOP INSTANCE instance_name
This command attempts to stop an instance. The command is synchronous; it waits for the instance
to stop.
mysql> STOP INSTANCE mysqld4;
Query OK, 0 rows affected (0,00 sec)
•
SHOW INSTANCES
Shows the names and status of all loaded instances.
mysql> SHOW INSTANCES;
+---------------+---------+
| instance_name | status |
+---------------+---------+