Errors SQL22212N or DBA1177N with DB2 Control Center

The DBA1177N message will appear under one of the following conditions:

1. The Tools Catalog Database has not been created.
2. The DAS configuration parameters have not been updated.
3. The connection failed (SQL22212N) to the Tools Catalog Database.

Resolving this issue can be as easy as restarting the DAS. If that doesn’t work then check the DAS configuration and if needed, create the Tools Database.

1. RESTART THE DAS:
The most common solution is to simply restart the DB2 Administration Server (DAS) 
Log in as the DAS owner and perform these commands to stop and start the DAS:

db2admin stop 
db2admin start

2. CHECK DAS CONFIGURATION: 
If the errors persist, check the following DB2 Administration Server configuration settings: 

TOOLSCAT_DB 

 

TOOLSCAT_INST 

 

TOOLSCAT_SCHEMA

These settings can be viewed with the command: GET ADMIN CONFIGURATION 

For example: 
log on as an instance owner (db2inst1) and use this command: 
db2 get admin cfg

 

 

 

OUTPUT:

 

Tools Catalog Database (TOOLSCAT_DB) = 
Tools Catalog Database Instance (TOOLSCAT_INST) = 
Tools Catalog Database Schema (TOOLSCAT_SCHEMA) =

3. CREATE TOOLSDB: 
If the output from the ‘get admin cfg’ command is empty as listed above, then you will need to create the Tools Catalog Database. 

For Example: 
log on as an instance owner (db2inst1) and use these commands: 
db2 create tools catalog SYSTOOLS create new database TOOLSDB

 

db2 get admin cfg

 

OUTPUT:

 

Tools Catalog Database (TOOLSCAT_DB) = TOOLSDB

 

Tools Catalog Database Instance (TOOLSCAT_INST) = DB2INST1

 

Tools Catalog Database Schema (TOOLSCAT_SCHEMA) = SYSTOOLS

 

Note: The DB2 Administration Server configuration keywords are initially set when the TOOLSDB database is created as listed above. The settings are removed if the DAS instance is dropped. Thus if you drop the DB2 Administration Server and already have a tools database created, remember to update the admin config settings with the name of the tools database using the ‘db2 update admin config’ command.