Error
Error Code:
72
MySQL Error 72: Option Requires Argument
Description
This error occurs when a MySQL command-line utility is invoked with a short option (e.g., `-u`, `-p`, `-h`) that expects a value, but no argument is provided. The utility cannot proceed because the specified option lacks its mandatory parameter.
Error Message
option '-%c' requires an argument.
Known Causes
3 known causesMissing Argument Value
You have used a short option (like `-u` for user or `-h` for host) without providing the necessary value immediately after it.
Incorrect Spacing or Syntax
An argument might have been provided, but incorrect spacing or syntax (e.g., adding a space where none is expected, or vice versa) caused the utility to not recognize it as the option's value.
Misunderstanding Option Requirements
The user might not be aware that certain short options, such as `-u` (user), `-h` (host), or `-P` (port), always mandate an accompanying argument.
Solutions
3 solutions available1. Correcting Incorrect Command-Line Syntax easy
Identify and fix typos or missing arguments in MySQL client commands.
1
Review the command you are using to interact with MySQL. The error 'option '-%c' requires an argument' indicates that a command-line option (like `--host`, `--user`, `--password`, `--port`, etc.) was provided without its corresponding value.
2
For example, if you intended to connect to a specific host, ensure you provide the host name after the `--host` option. Similarly, check for other options like `-u` (user), `-p` (password), `-P` (port), etc.
mysql --host --user myuser -p --port3
Correct the command by adding the missing arguments. For instance, to connect to host 'localhost' with user 'myuser' and prompt for a password:
mysql --host localhost --user myuser -p4
If you are using a tool that generates MySQL commands (e.g., a script or application), check its configuration or output to ensure it's constructing valid commands.
2. Verifying MySQL Client Configuration Files medium
Inspect and correct settings in MySQL configuration files that might be causing syntax issues.
1
MySQL client tools often read configuration from files like `~/.my.cnf` (on Linux/macOS) or `my.ini` (on Windows). These files can contain default options that are passed to the client.
2
Locate your MySQL configuration file. Common locations include:
On Linux/macOS: `~/.my.cnf` or `/etc/my.cnf`
On Windows: `C:\ProgramData\MySQL\MySQL Server X.X\my.ini` or `%APPDATA%\MySQL\my.ini`3
Open the configuration file in a text editor and look for sections related to the client (e.g., `[client]`). Examine the options defined within these sections for any missing arguments.
[client]
host =
user = myuser
port = 33064
Correct any options that are missing their required values. For example, if `host =` is present without a hostname, provide one or remove the line if it's not needed.
[client]
host = localhost
user = myuser
port = 33065
Save the configuration file and try running your MySQL command again. The corrected settings should now be applied.
3. Resolving Issues with Environment Variables medium
Check and fix any environment variables that might be incorrectly defining MySQL client options.
1
Some applications or scripts might use environment variables to pass arguments to the MySQL client. An incorrectly set environment variable can lead to this error.
2
Check for environment variables that might be influencing MySQL client behavior. Common variables related to MySQL include `MYSQL_HOST`, `MYSQL_USER`, `MYSQL_PORT`, etc. The exact variable names can vary depending on the application.
On Linux/macOS:
echo $MYSQL_HOST
On Windows (Command Prompt):
echo %MYSQL_HOST%3
If you find an environment variable that is set but missing its value, correct it or unset it if it's not intended to be used.
On Linux/macOS (to unset):
unset MYSQL_HOST
On Windows (Command Prompt, to unset):
set MYSQL_HOST=4
After correcting or unsetting relevant environment variables, restart your terminal or application and try running the MySQL command again.