KB484846: Special character restrictions of username and password in ODBC connection for Diamond and Platinum gateways

Quality Engineer, Senior • MicroStrategy

This article talks about the naming restrictions for special characters in username and password when trying to use ODBC connection to connect Diamond and Platinum gateways in MicroStrategy.

Description

ODBC is the Open Database Connectivity interface to access database management system. When trying to connect to databases using ODBC in MicroStrategy, following errors may occur due to unsupported special characters used in connection strings.

Invalid connection string attribute

Or

Error parsing connect string at offset.xx

Why is this happening?

The following special characters are used in the username or password, which is not recommended by ODBC:

[]{}(),;?*=!@|
To learn more about the restriction, see this ODBC documentation.

Solution

Change the username or password to exclude the special character: []{}(),;?*=!@|
Below is a table with a detailed list of special characters that should not be used by various databases in MicroStrategy, which contain both the characters not recommended by Microsoft ODBC and not allowed by databases.

Database	Version	Characters to Avoid in ODBC Connection Strings	Database References
Microsoft SQL Server	2008	[ ] { } ( ) , : ? * = ! @ \|	Microsoft doc
	2012	[ ] { } ( ) , : ? * = ! @ \|	Microsoft doc
	2014	[ ] { } ( ) , : ? * = ! @ \|	Microsoft doc
	2016	[ ] { } ( ) , : ? * = ! @ \|	Microsoft doc
	2017	[ ] { } ( ) , : ? * = ! @ \|	Microsoft doc
	2019	[ ] { } ( ) , : ? * = ! @ \|	Microsoft doc
Microsoft Azure Synapse Analytics	Latest	[ ] { } ( ) , ; ? * = ! @ \|	Microsoft doc
Amazon Redshift	Latest	'(single quote) “(double quote) \ / @ [ ] { } ( ) , ; ? * = ! @ \|	AWS doc
IBM Db2	9.7	[ ] { } ( ) , ; ? * = ! @ \|	IBM doc
	10.1	[ ] { } ( ) , ; ? * = ! @ \|	IBM doc
	10.5	[ ] { } ( ) , ; ? * = ! @ \|	IBM doc
	11.1	[ ] { } ( ) , ; ? * = ! @ \|	IBM doc
	11.5	[ ] { } ( ) , ; ? * = ! @ \|	IBM doc
Oracle	11gR2	[ ] { } ( ) , ; ? * = ! @ \|	Oracle doc
	12c	[ ] { } ( ) , ; ? * = ! @ \|	Oracle doc
	12cR2	[ ] { } ( ) , ; ? * = ! @ \|	Oracle doc
	18c	[ ] { } ( ) , ; ? * = ! @ \|	Oracle doc
	19c	[ ] { } ( ) , ; ? * = ! @ \|	Oracle doc
Teradata		[ ] { } ( ) , ; ? * = ! @ \|	Teradata doc
Teradata Vantage		[ ] { } ( ) , ; ? * = ! @ \|	Teradata doc
MongoDB	4.x	[ ] { } ( ) , ; ? * = ! @ \|	MongoDB doc Scram attributes
Oracle MySQL	5.x	[ ] { } ( ) , ; ? * = ! @ \|
Oracle MySQL	8.x	[ ] { } ( ) , ; ? * = ! @ \|
PostgreSQL	10.x	[ ] { } ( ) , ; ? * = ! @ \|	PostgreSQL doc The connection URI needs to be encoded with percent-encoding if it includes symbols with special meaning in any of its parts.
	11.x	[ ] { } ( ) , ; ? * = ! @ \|	PostgreSQL doc The connection URI needs to be encoded with percent-encoding if it includes symbols with special meaning in any of its parts.
	12.x	[ ] { } ( ) , ; ? * = ! @ \|	PostgreSQL doc The connection URI needs to be encoded with percent-encoding if it includes symbols with special meaning in any of its parts.
	13.x	[ ] { } ( ) , ; ? * = ! @ \|	PostgreSQL doc The connection URI needs to be encoded with percent-encoding if it includes symbols with special meaning in any of its parts.
Snowflake	Latest	[ ] { } ( ) , ; ? * = ! @ \|	Snowflake doc

Comment

0 comments

Details

Knowledge Article

Published:

May 28, 2021

Last Updated:

January 31, 2024

Solution

Database	Version	Characters to Avoid in ODBC Connection Strings	Database References
Microsoft SQL Server	2008	[ ] { } ( ) , : ? * = ! @ \|	Microsoft doc
	2012	[ ] { } ( ) , : ? * = ! @ \|	Microsoft doc
	2014	[ ] { } ( ) , : ? * = ! @ \|	Microsoft doc
	2016	[ ] { } ( ) , : ? * = ! @ \|	Microsoft doc
	2017	[ ] { } ( ) , : ? * = ! @ \|	Microsoft doc
	2019	[ ] { } ( ) , : ? * = ! @ \|	Microsoft doc
Microsoft Azure Synapse Analytics	Latest	[ ] { } ( ) , ; ? * = ! @ \|	Microsoft doc
Amazon Redshift	Latest	'(single quote) “(double quote) \ / @ [ ] { } ( ) , ; ? * = ! @ \|	AWS doc
IBM Db2	9.7	[ ] { } ( ) , ; ? * = ! @ \|	IBM doc
	10.1	[ ] { } ( ) , ; ? * = ! @ \|	IBM doc
	10.5	[ ] { } ( ) , ; ? * = ! @ \|	IBM doc
	11.1	[ ] { } ( ) , ; ? * = ! @ \|	IBM doc
	11.5	[ ] { } ( ) , ; ? * = ! @ \|	IBM doc
Oracle	11gR2	[ ] { } ( ) , ; ? * = ! @ \|	Oracle doc
	12c	[ ] { } ( ) , ; ? * = ! @ \|	Oracle doc
	12cR2	[ ] { } ( ) , ; ? * = ! @ \|	Oracle doc
	18c	[ ] { } ( ) , ; ? * = ! @ \|	Oracle doc
	19c	[ ] { } ( ) , ; ? * = ! @ \|	Oracle doc
Teradata		[ ] { } ( ) , ; ? * = ! @ \|	Teradata doc
Teradata Vantage		[ ] { } ( ) , ; ? * = ! @ \|	Teradata doc
MongoDB	4.x	[ ] { } ( ) , ; ? * = ! @ \|	MongoDB doc Scram attributes
Oracle MySQL	5.x	[ ] { } ( ) , ; ? * = ! @ \|
Oracle MySQL	8.x	[ ] { } ( ) , ; ? * = ! @ \|
PostgreSQL	10.x	[ ] { } ( ) , ; ? * = ! @ \|	PostgreSQL doc The connection URI needs to be encoded with percent-encoding if it includes symbols with special meaning in any of its parts.
	11.x	[ ] { } ( ) , ; ? * = ! @ \|	PostgreSQL doc The connection URI needs to be encoded with percent-encoding if it includes symbols with special meaning in any of its parts.
	12.x	[ ] { } ( ) , ; ? * = ! @ \|	PostgreSQL doc The connection URI needs to be encoded with percent-encoding if it includes symbols with special meaning in any of its parts.
	13.x	[ ] { } ( ) , ; ? * = ! @ \|	PostgreSQL doc The connection URI needs to be encoded with percent-encoding if it includes symbols with special meaning in any of its parts.
Snowflake	Latest	[ ] { } ( ) , ; ? * = ! @ \|	Snowflake doc