Starting the Repository Client gets the error "Database Error: Maximum connections reached" even though no one else is connected to the database. Is this a configuration problem?

Document ID : KB000026839
Last Modified Date : 14/02/2018
Show Technical Document Details

Description

It may be that the Repository Client is trying to locate the Repository Engine in order to connect to the Repository Database, but the Repository Client makes the call to an incorrect port or server. This rejection is interpreted as a maximum connections situation though it may actually be that the Repository Engine is not listening through that port or on that server.

This has been seen when the Repository database was moved to a new Database Server, and the Repository Administrator correctly reconfigured the Repository DataSource and may have needed to reconfigure the Repository Alias, but mistakenly also reconfigured the Engine Alias. The Engine Alias always points to the Engine Server. Below is a description of how to configure the ODBC DataSource, the Repository Alias, and the Engine Alias on the computer hosting the Repository Engine and Client and a computer hosting the Repository Client tools only.

Solution

Configuration Description

Repository Engine Host Machine Client Desktop or Laptop
Configuration for CARDS on this server: Configuration for CARDS on this computer:
ODBC DSN:
Name: Any name *
Server: Oracle TNS Name defined on this computer or SQL Server's host machine name.

Then complete the DataSource configuration consistent with the driver and database server type hosting the Repository database.
ODBC DSN:
Name: Any name *
Server: Oracle TNS Name defined on this computer or SQL Server's host machine name.

Then complete the DataSource configuration consistent with the driver and database server type hosting the Repository database.
Repository Alias:
Name: Any name *
DSN: An ODBC DSN that resides in ODBC DataSources on this computer. This DSN points to the Repository Database wherever that database may reside. This Alias will be used to connect to the Repository database by the Repository Engine as well as the client tools on this server such as PCAF Loader, Procedure Generator, Metadata Scanners, etc. It is not used by the Repository Client executable.
Login: Login information for this DSN
Repository Alias:
Name: Any name *
DSN: An ODBC DSN that resides in ODBC DataSources on this computer. This DSN points to the Repository Database wherever that database may reside. This Alias will be used to connect to the Repository database by the PCAF Loader, Procedure Generator, Metadata Scanners, etc. It is not used by the Repository Client executable.
Login: Login information for this DSN
Engine Alias:
Name: Any name *
Host Name or ip-address: This is the name of the machine where the CARDS Engine will be running.
Port: This is the port through which the CARDS Engine will be listening for Client connections. It must be a free port on the Engine server machine. The default is 2861.
Engine Alias:
Name: Any name *
Host Name or ip-address: This is the name of the machine where the CARDS Engine will be running.
Port: This is the port on the Engine server through which the CARDS Engine will be listening for Client connections. It will be the same machine name and port number as was configured on the Engine server.
* The DataSource names do not need to match across computers, and Alias names do not need to be the same from computer to computer, but for setup and troubleshooting it's often convenient if they are.

Configuration Example

  • The CARDS Engine will be running on a server named CARDS-SVR.

  • The Repository Client tools are also installed on the CARDS-SVR machine.

  • A Repository Administrator has CARDS Client tools, such as the Population Center , Procedure Generator, and Repository Client installed on his or her own desktop which has a machine name of UserA-Dsktp.

  • The Repository Database resides in a database server on machine MYDB01.

  • The ODBC examples show Oracle and SQL Server hosts, but do not include DataSource configuration information not pertinent to Repository configuration. For Oracle, the user would have previously configured a TNS Name through the Oracle Net Configuration Assistant. In this example the TNS Name configured on the server is ORA102A. The TNS Name on the desktop, pointing to the same Oracle database, is called ORCL10.

  • DBA access to this database uses the login "reposprod" and password "mypwd."

  • The example intentionally uses the same name when required, and different names where possible, to reinforce which objects are and are not dependent on each other's name. Actual installations generally prefer to use the same names where possible to make it easy to remember what the name represents.
Machine name: CARDS-SVR Machine name: UserA-Dsktp
ODBC DataSource (Oracle)
Name: CARDS22PROD
Server Name: ORA102A

ODBC DataSource (SQL Server)
Name: CARDS22PROD
Server: MYDB01
ODBC DataSource (Oracle)
Name: REPOS
Server Name: ORCL10

ODBC DataSource (SQL Server)
Name: REPOS
Server: MYDB01
Repository Alias:
Name: ReposProd
DSN: CARDS22PROD
Login: reposprod
Password: mypwd
Repository Alias:
Name: CARepos
DSN: REPOS
Login: reposprod
Password: mypwd
Engine Alias:
Name: CARDS_Engine
Host Name or ip-address: CARDS-SVR
Port: 2861.
Engine Alias:
Name: ReposEngine
Host Name or ip-address: CARDS-SVR
Port: 2861.