Documentation

InfluxDB Clustered

influxctl database rename

  • influxctl 2.10.2+

The influxctl database rename command renames a database in an InfluxDB cluster. This command does not change the database ID, database properties, or the data stored in the database.

Renaming a database requires new tokens

Database tokens are associated to databases by name. After renaming a database, tokens referencing the old name no longer function. You must generate tokens for the new database name.

Usage

influxctl database rename [flags] <CURRENT_DB_NAME> <NEW_DB_NAME>

Arguments

ArgumentDescription
CURRENT_DB_NAMECurrent name of the database
NEW_DB_NAMENew name for the database

Flags

FlagDescription
-h--helpOutput command help

Also see influxctl global flags.

Was this page helpful?

Thank you for your feedback!

© 2025 InfluxData, Inc.

What is your InfluxDB cluster URL?

Enter your InfluxDB cluster URL and we’ll update code examples for you.

Enter cluster URL

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2