Thread: Error in actuate
05-05-08, 07:43 #1Registered User
- Join Date
- May 2008
Unanswered: Error in actuate
When we deploy a report in web, we are getting the following error
Plz see the attachment.
Can anyone please help on this asap.
05-05-08, 11:44 #2Registered User
- Join Date
- Jun 2006
is this a new installation and/or has it worked before
is the instance listening on the correct port
db2 get dbm cfg | grep SVC
with this entry check /etc/services
check at client the port : db2 list node directoryBest Regards, Guy Przytula
DB2 UDB LUW certified V6/7/8
05-05-08, 14:46 #3Registered User
- Join Date
- Nov 2005
Man, you got to learn to use Google. This was easy to find.
Looks like you are using SUN. Check one of the folowing
- The remote database server has not been cataloged correctly at the client. In a client-gateway-server scenario, ensure the host entries are cataloged correctly on the gateway. See the Quick Beginnings guide for assistance.
- The database manager configuration file at the server has not been configured properly with the proper communication parameters. Check that svcename has been configured properly with the TCP/IP service name or port number and that the port number is unique. If database manager configuration parameters have been updated at the server, the database manager must be stopped and re-started for the changes to take effect. There might be a mismatch between the TCP/IP service name or port number specified on the server and on the client. Ensure the service name maps to the correct port number by checking the services file. You can check this by reading the services file or checking the output of "netstat -a".
- The DB2COMM environment variable at the server does not specify the communication protocol used by the client. Check that TCPIP has been specified. Issue db2set to see what has already been set. Issue db2set DB2COMM = TCPIP to set the value.
- The database manager at the server has not been started, or has not been started successfully, or has gone down. The server should have returned SQL1063, and not SQL5043. If you set the database manager configuration parameter, diaglevel, to 4 using, db2 update dbm cfg using diaglevel 4, prior to issuing db2start, the administration notification log will provide detailed information on which protocols were started successfully. Check the administration notification log.
- The server might be too busy to handle the volume of incoming connections at this time.
- Network failure, contact your network administrator. You can try a test using the protocol tester, pctt, to verify this is not a DB2 problem.
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
DB2 v220.127.116.11 os 18.104.22.168