home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC89705 Status: Geschlossen

ENABLE_MQFUNCTIONS UTILITY SHOWS UNSUPPORTED PARAMETER "-Q" IN
USAGE MESSAGE

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When using enable_MQFunctions executable you may see usage 
message as below: 
 
============================================================ 
Usage: enable_MQFunctions -n dbName -u uID -p password 
                    [-q queuemanager] [-v 0pc|1pc|all] 
                    [-novalidate] [-echo] [-force] 
                    [-c clobSize] 
============================================================ 
 
But actually Federation Server does NOT support parameter [-q 
queuemanager] on v95 or later versions. You can not specify 
queue manager name to enable your MQ UDF.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* 68660,000,858                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Federation Server v10.1fp3 or later.              * 
****************************************************************
Local-Fix:
To enable MQ UDF using your own queue manager instead of the 
default one: 
 
1. Create your own queue manager, create at least a receive 
queue in it, active it. 
 
2. Run enable_MQFunctions(without -q option) to enable MQ UDF 
using the default queue manager. 
 
3. Run below SQLs to update the config table to use your own 
queue manager: 
 1) UPDATE  DB2MQ."MQSERVICE" SET 
QUEUENAME='<QUEUE_NAME>',QUEUEMGRNAME='<QUEUE_MGR_NAME>' WHERE 
SERVICENAME='DB2.DEFAULT.SERVICE' 
 2) UPDATE   DB2MQ."MQHOST" SET QUEUEMGRNAME='<QUEUE_MGR_NAME>' 
 3) ALTER SERVER MQ OPTIONS(SET AMI_QUEUE_MGR_LIST 
'<QUEUE_MGR_NAME>') 
 
NOTE: Where <QUEUE_MGR_NAME> is the queue manager name, 
<QUEUE_NAME> is name of the queue managered by <QUEUE_MGR_NAME>
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
The problem was firstly fixed in Federation Server v10.1fp3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.01.2013
03.10.2013
03.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList