DB2v9.5 how to save the database creation error reported by the Control Center?

Today, we mainly want to describe to the following information: the database creation error of the DB2v9.5 control center is reported: The system is rhel5.3, and the database is db2v9.5. When using the control center to create a database, we should proceed step by step, the final result is an error such as SQL4414 and DB2ADMIN Server is not acitve.

I have created the DB2admin server and the service is started./etc/hosts also has the Host Name and IP address, and/etc/service also has the corresponding service and port, from db2diag. log to get the following error:

 
 

  
  
010-03-08-13.09.16.532849+480 E22610G382 LEVEL: Error (OS)  
  
  
PID : 4540 TID : 106711952 PROC : java  
  
  
INSTANCE: db2inst1 NODE : 000  
  
  
FUNCTION: DB2 UDB, oper system services, sqloPdbSendBuffer, probe:20  
  
  
MESSAGE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR "Communication error"  
  
  
CALLED : OS, -, send OSERR: EPIPE (32)  
  
  
2010-03-08-13.13.37.993911+480 E22993G382 LEVEL: Error (OS)  
  
  
PID : 4540 TID : 14543760 PROC : java  
  
  
INSTANCE: db2inst1 NODE : 000  
  
  
FUNCTION: DB2 UDB, oper system services, sqloPdbSendBuffer, probe:20  
  
  
MESSAGE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR "Communication error"  
  
  
CALLED : OS, -, send OSERR: EPIPE (32) 
 
 

Delete the das, re-create the das, and then go to the control center to re-create the database, directly report the dasadmin is not active for your advice! The above content is an introduction to the error of creating a database in the DB2v9.5 Control Center. I hope you will get something.

The above content is the description of the error reported for the DB2v9.5 control center database creation. I hope it will help you in this regard.