If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Administration Server communication error

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-03-06, 20:08
meehange meehange is offline
Registered User
 
Join Date: Jul 2004
Posts: 256
Administration Server communication error

DB2 8.2 on Win2003

When I try to change configuration settings (from an admin client or on the server) via the GUI I get the following error:

SQL22212N A DB2 Administration Server communication error has been detected.

I can set the parameters via the CLI and the Configuration Advisor works fine just not the config params in the GUI.
I can perform a db2stop and db2start on the system and I think the Admin server is cataloged properly (how do I verify this?)

I have 3 instances on this server and about 10 DB's

Any ideas?
Reply With Quote
  #2 (permalink)  
Old 04-03-06, 20:30
Marcus_A Marcus_A is offline
Registered User
 
Join Date: May 2003
Location: USA
Posts: 5,196
Is the DB2 Administrative Server started? Check your Windows services. You can also try to start it with "db2admin start" from the command line interface.

If it is already started, stop it and restart (db2admin stop).

If that does not work, then drop the administrative instance and recreate it. See the Command Reference for details.
__________________
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390
Reply With Quote
  #3 (permalink)  
Old 04-04-06, 00:15
meehange meehange is offline
Registered User
 
Join Date: Jul 2004
Posts: 256
Quote:
Originally Posted by Marcus_A
Is the DB2 Administrative Server started? Check your Windows services. You can also try to start it with "db2admin start" from the command line interface.

If it is already started, stop it and restart (db2admin stop).

If that does not work, then drop the administrative instance and recreate it. See the Command Reference for details.
Yes sorry I meant to say that I could do a db2admin stop and start, not DB2STOP and DB2START.

I'll try dropping and recreating the instance .. is that likely to cause disruption to DB's on the server?
Reply With Quote
  #4 (permalink)  
Old 04-04-06, 00:21
Marcus_A Marcus_A is offline
Registered User
 
Join Date: May 2003
Location: USA
Posts: 5,196
Quote:
Originally Posted by meehange
I'll try dropping and recreating the instance .. is that likely to cause disruption to DB's on the server?
No, it should not cause any disruption to regular DB2 instances.
__________________
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On