SQL2044N reason code 7

Shivraj Kumar Sarsambi

unread,

May 9, 2018, 11:58:41 PM5/9/18

to

SQL2044N An error occurred while accessing a message queue. Reason
code: "<reason-code>"
Explanation: An unexpected error or bad message was received on one of
the message queues during the processing of a database utility. The
following is a list of reason codes:
1
Unable to create a message queue. The number of message queues allowed
may have been exceeded.
2
An error was encountered while reading from a message queue.
3
An error was encountered while writing to a message queue.
4
An invalid message was received from a message queue.
5
An error was encountered while opening a message queue.
6
An error was encountered while closing a message queue.
7
An error was encountered while querying a message queue.
8
An error was encountered while deleting a message queue.

While taking a backup through EMC networker for a database, we get SQL2044N reason code 7 . Please note that local backup of db is successful and there is enough storage as well.

Please help!

Thanks,
Shivraj

Shivraj Kumar Sarsambi

unread,

May 9, 2018, 11:59:23 PM5/9/18

to

> While taking a backup through EMC networker for a database, we get SQL2044N reason code 7 . Please note that local backup of db is successful and there is enough storage as well. DB2 LUW Version - 11.1.1.1.
>
> Please help!
>
> Thanks,
> Shivraj

Mladen Gogala

unread,

May 12, 2018, 5:36:37 PM5/12/18

to

On Wed, 09 May 2018 20:58:39 -0700, Shivraj Kumar Sarsambi wrote:

> While taking a backup through EMC networker for a database, we get
> SQL2044N reason code 7 . Please note that local backup of db is
> successful and there is enough storage as well.
>
> Please help!

EMC Networker? You can find all the help for EMC Networker for DB2 here:
https://www.commvault.com
No error messages there. EMC Networker is an old and neglected product,
the artist formerly known as Legato Networker. Even EMC advises using
Avamar or DD Boost instead of the Networker.

Disclosure:
I am an employee of Commvault Systems, a competing backup suite.

--
Mladen Gogala
Database Consultant
http://mgogala.byethost5.com

Shivraj Kumar Sarsambi

unread,

May 13, 2018, 11:12:00 PM5/13/18

to

Thanks Mladen for the heads up.

I encountered this in db2diag.log.

2018-05-13-23.17.53.012195+480 I249095494E808 LEVEL: Error
PID : 24962 TID : 140284205721344 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : XMETA
APPHDL : 0-27870 APPID: *LOCAL.db2inst1.180513151608
AUTHID : BKADMIN HOSTNAME: DCDCA0000047
EDUID : 150 EDUNAME: db2agent (XMETA) 0
FUNCTION: DB2 UDB, oper system services, sqloReadNamedPipe, probe:1273
MESSAGE : ZRC=0x870F00B3=-2029059917=SQLO_NPIPE_TIMEOUT
"Operation on named pipe timed out."
DATA #1 : String, 55 bytes
Timeout error occurred with the following timeout value
DATA #2 : String, 18 bytes
timeout (seconds):
DATA #3 : signed integer, 8 bytes
0
DATA #4 : String, 23 bytes
timeout (microseconds):
DATA #5 : signed integer, 8 bytes
0

2018-05-13-23.17.57.261506+480 E249096303E472 LEVEL: Severe
PID : 24962 TID : 140284205721344 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : XMETA
APPHDL : 0-27870 APPID: *LOCAL.db2inst1.180513151608
AUTHID : BKADMIN HOSTNAME: DCDCA0000047
EDUID : 150 EDUNAME: db2agent (XMETA) 0
FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:1081
MESSAGE : Backup terminated.

Based on the technote - http://www-01.ibm.com/support/docview.wss?uid=swg1IC85508, though the diag messages are not similar.

Eventual justification for the cause of the backup failure is similar.

==============
This error is more likely to happen using the DEDUP_DEVICE
option on the backup and in certain circumstances due to not
having any data to backup in the tablespace.
===============

I have few temp tablespaces which are of only 1 page size and empty. So, I can assume that the issue is due to empty tablespaces.

If there is any other point I missed or overlooked, feel free to share here.

Thanks,
Shivraj