Error message sql0443n is received when you use DB2 MQ Functions to send messages to a default queue.
We used DB2 “values db2mq.mqsend(‘test’))” DB2 MQ Functions to send messages to a default queue. We received error sql0443n, as depicted in the screen capture below.
This error may be caused for different reasons. The following is a list of a few causes for the error and a solution:
We re-installed the DB2 instance, but used a different instance owner. The database remained unchanged. However, after the owner change, the DB2 MQ Functions User Defined Function (UDF) would fail. In this case, the reason for the failure is that DB2 MQ Functions was running in fenced mode. There is a file called .fenced in the /home/udb81/sqllib/adm directory. This file determines what users can run the UDF, and necessitates that the owner of the file should be the DB2 instance owner. Therefore, we changed the file owner to be the same as the new DB2 instance owner, and then the DB2 MQ Functions UDF worked without error.
At times, after a system reboot, DB2 MQ Functions would not work properly. DB2 would go to the default location to find amt files. Also, the AMT_DATA_PATH in DB2ENVLIST was not valid, even though we had set it before. The solution was to reset AMT_DATA_PATH using the db2set command, as shown below:
At times the Default Queue Manager would not start. The solution was to start it manually. That is, just use the strmqm command to start default queue manager.
This message will also appear when too many messages are in the queue and it has reached the max depth. The solution in this case is to remove some messages, or to increase the size of the queue.
This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.