alibaba/nacos · error · IllegalStateException

No DatabaseDialect implementation found for selected type:

Error message

No DatabaseDialect implementation found for selected type:  + databaseType + . Please ensure the selected datasource plugin is loaded.

What it means

Thrown by DatabaseDialectManager.getDialect as IllegalStateException when SUPPORT_DIALECT_MAP contains no entry for the databaseType. This is distinct from the disabled-plugin case: the dialect plugin is enabled (or not gated) but no implementation was loaded/registered for the type.

Source

Thrown at plugin/datasource/src/main/java/com/alibaba/nacos/plugin/datasource/manager/DatabaseDialectManager.java:80

            LOGGER.warn(
                "[DatasourceDialectManager] Load DatabaseDialect fail, No DatabaseDialect implements");
        }
    }
    
    public DatabaseDialect getDialect(String databaseType) {
        // Check if plugin is enabled
        if (!PluginStateCheckerHolder.isPluginEnabled(PluginType.DATASOURCE_DIALECT.getType(),
            databaseType)) {
            LOGGER.debug("[DatabaseDialectManager] Plugin DATASOURCE_DIALECT:{} is disabled",
                databaseType);
            throw new IllegalStateException(
                "DatabaseDialect plugin is disabled: " + databaseType
                    + ". Please enable it via plugin management API.");
        }
        
        DatabaseDialect databaseDialect = SUPPORT_DIALECT_MAP.get(databaseType);
        if (databaseDialect == null) {
            throw new IllegalStateException(
                "No DatabaseDialect implementation found for selected type: " + databaseType
                    + ". Please ensure the selected datasource plugin is loaded.");
        }
        return databaseDialect;
    }
    
    /**
     * Get DatasourceDialectManager instance.
     *
     * @return DataSourceDialectProvider
     */
    public static DatabaseDialectManager getInstance() {
        return INSTANCE;
    }
    
    /**
     * Get all registered database dialects.
     *

View on GitHub (pinned to 9b989acdf1)

Solutions

1. Add the datasource dialect plugin JAR for the configured databaseType to the server classpath.
2. Check startup log for 'No DatabaseDialect implements' and resolve the load failure.
3. Align the configured nacos persistence type with an installed dialect plugin.

Example fix

// before: no dialect plugin for the type
manager.getDialect("oracle"); // -> IllegalStateException no implementation

// after
// 1. provide a DatabaseDialect SPI for oracle (or switch to a supported type)
// 2. confirm SUPPORT_DIALECT_MAP contains "oracle" at startup
manager.getDialect("mysql");

// confirm a dialect is loaded for the type
boolean loaded = DatabaseDialectManager.getInstance()
    .allDialects().containsKey(databaseType); // if such accessor exists

static boolean dialectLoaded(String type) {
    return DatabaseDialectManager.getInstance().getDialectMap().containsKey(type);
}

try {
    return manager.getDialect(type);
} catch (IllegalStateException e) {
    if (e.getMessage().contains("No DatabaseDialect implementation")) {
        // install dialect plugin JAR and restart
    } else throw e;
}

When it happens

Trigger: Calling getDialect(databaseType) for a type whose DatabaseDialect SPI implementation is absent from the classpath or failed to load into SUPPORT_DIALECT_MAP at startup.

Common situations: Configuring a database type whose dialect plugin JAR is missing; plugin SPI registration broken; startup load failure logged as a warning ('Load DatabaseDialect fail, No DatabaseDialect implements') and then a request triggers this error.

Related errors

• DatabaseDialect plugin is disabled: + databaseType + . Plea
• 103
• No AiResourceStorage for provider: + storageKey.getProvider
• RESOURCE_NOT_FOUND
• MCP server not found in registry: ${externalId}

AI-assisted analysis of alibaba/nacos@9b989acdf1 (2026-08-14). Data as JSON: /api/errors/17558859dea4ac5a. Report an issue: GitHub.