Did this article resolve your question/issue?



Unable to access Auxiliary Database tables from a Multi-database SQL connection

« Go Back


TitleUnable to access Auxiliary Database tables from a Multi-database SQL connection
URL NameUnable-to-access-Auxiliary-Database-tables-from-a-Multi-database-SQL-connection
Article Number000179363
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: All supported platforms
Other: [-mdbq:<catalog-name>]
Question/Problem Description
Unable to access Auxiliary Database tables from a Multi-database SQL connection

<database> is created as detailed in article Quick Guide to setting up Multi Database ODBC / JDBC connectivity

SQL client connects with [-mdbq:<catalog-name>] parameter.

SQL clients fails to access Auxiliary tables

sqlexp errors with (13693) when attempting to access and auxiliary database with the catalog name.

Primary database logs errors with "Auxiliary databases not connected"

Steps to Reproduce
Clarifying Information
Error MessagePrimary Database log:

SQLSRV<n> <n>: (-----) User <usernum> Connection warning: Auxiliary
databases not connected

sqlexp errors with:

Catalog name <catalog-name> is an unknown catalog. (13693)
Defect/Enhancement Number
The <primary database> is missing a CRLF character after the last line in the file. For example, if the properties file is viewed through an editor that can show all characters it looks like:

1. Add a CRLF character (ENTER) to the last line in the properties file:


2. Connect with the [-mdbq] parameter from the sqlexp tool and issue the command 'show catalogs all;' This should show that both the primary and auxiliary database is connected:

SQLExplorer>show catalogs all;
------------------      ---------            ----------
SP2G1                 primary            default
config                   auxiliary           notdefault

3. SQL queries referencing the catalog name should now work.
Last Modified Date6/16/2015 3:19 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.